Add Markdown custom agent selection - #170
Conversation
|
Warning Review limit reached
Next review available in: 6 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (55)
✨ Finishing Touches🧪 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 |
- Remove conditional primary-color highlight from effort/agent picker triggers and agent list items; use uniform foreground color - Only show agent-changed system notice when a conversation is active (timeline non-empty) to avoid replacing the welcome hero
What changed
*.agent.mdfiles under~/.jcode/agents/and<project>/.jcode/agents/nameanddescriptionfrontmatter plus a non-empty Markdown instruction body; support an optional role modeljcode --agent, a conditional Web/Desktop Agent picker, active-agent display, localized switch notices, and session persistence/replayWhy
Custom agents already existed as an unused JSON-only delegated-role mechanism, but there was no top-level selection or visible current-agent state. The new Markdown format matches the repository's instruction-oriented workflows and follows the useful Codex/Grok semantics: role instructions are reusable, an optional role model can override selection, and runtime permissions remain inherited from the caller.
User/developer impact
When valid custom agents exist, Web/Desktop shows
Defaultplus every effective role. CLI users can select one withjcode --agent <name>. Agent changes survive resume and appear in the timeline. Custom Markdown cannot add tools, bypass approval, or broaden the active mode/sandbox.This intentionally removes inline/legacy JSON agent definitions; the feature was not yet in use.
Validation
go test ./...go test -race ./internal/config ./internal/session ./internal/web ./internal/commandmake lintmake buildpnpm --dir packages/jcode-ui testpnpm --dir web testpnpm --dir site build