Repository navigation
fix: label agent-worker config fields for editable console forms - #381
Conversation
The console builds the worker-config form from each worker's published config schema; fields with no description render as unlabeled/empty inputs. Documented every config field across the agent workers that lacked it, so each renders as a labeled, editable field: - codex (Rust): /// doc comments on Defaults + Config (schemars -> description). - claude-code / pi / opencode (TS): .describe() on each Zod config field (z.toJSONSchema -> description). hermes already documents its config schema; grok is fixed on its own branch. No behavior change. Verified the generated schema now carries per-field descriptions (top-level + nested). codex 32 tests, claude-code 75, pi 69, opencode 64 — all pass; fmt/clippy/biome clean.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
skill-check — worker0 verified, 29 skipped (no docs/).
Four for four. Nicely done. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis PR adds descriptive metadata to configuration schemas across four packages (claude-code, codex, opencode, pi). Zod ChangesConfig schema documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
The console builds each worker's config form from its published config schema. Fields with no
descriptionrender as unlabeled / empty grey inputs, so the agent workers' configs looked non-editable. Documented every config field that lacked a description across the agent workers so each renders as a labeled, editable field.Changes
codex(Rust)///doc comments onDefaults+Config→ schemars emitsdescriptionclaude-code(TS).describe()on each Zod config field →z.toJSONSchemaemitsdescriptionpi(TS)opencode(TS)hermesalready documents its config schema;grokis fixed on its own branch (#378).Verified
Dumped each worker's generated schema and confirmed descriptions now land at the top level and on nested
defaults.*fields. No behavior change (comments / schema metadata only).-D warningsclean, 32 testsDoc/metadata-only, so no version bumps.
Summary by CodeRabbit