Add jcode coding agent to CLI - #121
Conversation
|
Warning Review limit reached
Next review available in: 48 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 (14)
📝 WalkthroughWalkthroughAdds the ChangesJcode integration
Estimated code review effort: 2 (Simple) | ~15 minutes Sequence Diagram(s)sequenceDiagram
participant CLI
participant AgentRegistry
participant Runtime
participant JcodeContainer
CLI->>AgentRegistry: resolve "j" to "jcode"
AgentRegistry->>Runtime: load jcode specification and image
Runtime->>JcodeContainer: start jcode with config and skill mounts
Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 2📝 Generate docstrings 💡
🛠️ Fix failing CI checks 💡
🧪 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 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9e32ad3c35
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # $HOME and its provider env files via XDG config (~/.config/jcode), | ||
| # so pointing HOME at the persisted /config mount covers both. | ||
| {"HOME": "/config", "JCODE_NO_AUTO_UPDATE": "1"}, | ||
| headless_prefix=["run"], |
There was a problem hiding this comment.
When vp task create jcode ... is used with installed project or user skills, task.create builds extra_volumes only from agent_extra_volumes and never invokes the skills-mount logic added for Jcode in run.py. Consequently, the new task-mode path launches successfully but lacks /config/.agents/skills/<id>, so Jcode cannot discover those skills despite the documented support; task creation should add the same resolved skill mounts as vp run.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/vibepod/core/agents.py`:
- Line 172: Update the Jcode command construction in the agent execution flow to
pass the supported global `--no-update` flag before `run`, replacing the
ineffective `JCODE_NO_AUTO_UPDATE` environment entry; preserve the existing
command behavior otherwise.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 81146956-60ad-42b4-9f80-0d2d1139d3f6
📒 Files selected for processing (14)
README.mddocs/agents/index.mddocs/configuration.mddocs/index.mddocs/quickstart.mdsrc/vibepod/commands/run.pysrc/vibepod/constants.pysrc/vibepod/core/agents.pysrc/vibepod/core/config.pytests/test_agents.pytests/test_cli.pytests/test_constants.pytests/test_run.pytests/test_task_cmd.py
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Adds support for the Jcode agent to VibePod. Jcode is now recognized as a first-class agent throughout the CLI, configuration, documentation, and tests. The changes ensure Jcode can be run, configured, and managed just like other agents, with appropriate documentation and test coverage.
Jcode Agent Integration
vp j) and default image (vibepod/jcode:latest).AgentSpec, including environment variables, config mount path, command, and headless mode support.Documentation Updates
Summary by CodeRabbit
New Features
vp jshortcut for launching Jcode.VP_IMAGE_JCODE.Documentation
Tests