Repository navigation
Prepare v1.1.1 and the ACP registry resubmission - #2
Conversation
The listing still pointed at kelvin-soen/OndeCode v1.0.0, while the v1.1.0 release and the npm provenance live on ondeinference/onde-code. - Replace the repository URLs in Cargo.toml, the release skill, the winget workflow and packaging/registry. Issue links stay on kelvin-soen, where the audit and tracking issues are. - agent.json: v1.1.0 archives and hashes, a new description, Onde Inference as author, a website, and an npx entry for @ondeinference/onde-code with --acp. - update-agent.sh also sets the npx package version. - New assets/icon.svg: the ONDE block as a 16x16 currentColor square with the letters knocked out. - Rewrite packaging/registry/README.md around the new registry PR. - Add keywords, categories and a readme to the crate manifests. Co-Authored-By: Onde Code v1.1.0-acp <noreply@ondeinference.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The README now opens like onde-cli (logo, subtitle, badges, SDK row) and stays short. The long reference content moves into focused pages under docs/, with an index: install, editors, ACP behavior, terminal, models, providers and development. docs/models.md covers model work through `onde --mcp`. The MCP server lists, registers and assigns models; fine-tuning runs through the onde CLI, and the page says so. Built-in tools stay tracked in kelvin-soen#27. Also add the onde-code-agent crate README, and use the new subtitle and intro in the npm package READMEs. Co-Authored-By: Onde Code v1.1.0-acp <noreply@ondeinference.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The crate, npm and winget manifests still described Onde Code as an ACP-compatible agent for fine-tuning and deployment. Use the registry wording, and replace the winget long description, which still said inference runs on-device from GGUF models. Co-Authored-By: Onde Code v1.1.0-acp <noreply@ondeinference.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Onde Code v1.1.0-acp <noreply@ondeinference.com> Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
![sigit-code-review[bot]](https://avatars.githubusercontent.com/in/3492899?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR prepares the renamed repo for a fresh ACP registry submission: it points agent.json at v1.1.0 archives on ondeinference/onde-code, adds the npx distribution, updates npm/winget descriptions, splits the README into docs/, adds a crate README for onde-code-agent, and bumps workspace versions to 1.1.1. The registry entry itself is intentionally left at 1.1.0 to be bumped post-release; the one issue I found is that the registry README's submission walkthrough still uses 1.1.0 tags even though Cargo.toml is now 1.1.1.
Automated review by siGit Code Review · commit b329bb3 · see the review dashboard
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
This re-review covers the documentation updates that add Android Studio/JetBrains, Xcode and marimo setup instructions to docs/editors.md, and update the editor lists in README.md and docs/README.md. The earlier warning about the registry README still tagging v1.1.0 is unchanged and remains open; no new issues were introduced in this diff.
Automated review by siGit Code Review · commit 01b400e · changes since b329bb3 · see the review dashboard
The steps tagged v1.1.0 while Cargo.toml is 1.1.1, and the release workflow refuses a tag that does not match. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The repo now lives at ondeinference/onde-code, so the old registry submission (agentclientprotocol/registry#652) points at the wrong place. I'll close it and send a fresh one once v1.1.1 is released. This PR gets main ready for that.
Changes
packaging/registry/agent.jsonis set to v1.1.0 with npx distribution added, the new description, authors and website.update-agent.sh v1.1.1bumps it after the release.docs/. Theonde-code-agentcrate gets its own README.Cargo.toml,crates/agent/Cargo.tomlandCargo.lock, so main can be taggedv1.1.1right after this merges.onde --mcphas no fine-tuning tool, sodocs/models.mdsays fine-tuning goes through the CLI.Validation
cargo fmt --check,cargo clippy --all-targets --locked -- -D warningsandcargo test --lockedpass.cargo package --listchecked for the agent crate, and the doc links resolve.--auth-checkpass for both the binary and npx distributions, run natively rather than in Docker.Refs kelvin-soen#27