An API backend's `tools` setting (auto, lean or full) could only be changed by editing config.toml. Settings → AI now has a "Builder's tools" choice per API backend, with a caption saying what Auto works out to for that AI, and `ai tools <name> [auto|lean|full]` shows or sets it from the CLI. Auto is saved as no setting; agent apps are refused, as they choose their own tools.
* Let Claude Code use the model its own settings name by default
Claude Code runs are no longer passed a hardcoded --model: with no choice
saved, the agent uses whatever its own settings name (a custom model, an
alias, opusplan…), and `ai model --default` clears a saved override back
to that. The Settings → AI picker lists "Default (its own settings)" first
for Claude Code (saved as `claude-code` or `claude`), choosing it clears
the saved model, and the typed "Another model" field is gone since the
list carries the choice. effort_levels detects Claude Code by adapter id
so the `claude` agent id gets every effort level too.
* Translate "Default (its own settings)" in the remaining eight catalogs
The i18n gate requires every catalog to carry the same key set; the
first commit only added the new picker label to six of them.
An API backend's requests per minute could only be set by editing config.toml. Settings → AI now has a field for it on each API backend, and the CLI has ai request-rate <name> [n]; zero removes the limit. Agent apps send their own requests, so they have no such setting. The save runs on a worker through the hub's usual save path.
Since #987, picking a folder that already holds a project attaches to it, but the create path then overwrote its saved builder, asset budget, generated-assets choice and stack, replaced its conversation, and dropped the typed request. An attached project now keeps everything the person set and its saved conversation, and the request is added as its follow-up, in the app and the CLI; the CLI refuses --build-with, --generate-assets and --existing for such a folder with a fix to use instead.
A key saved in the app silently wins over the one in the environment, so a rotated key stayed hidden behind the old one unless the backend was removed or the keychain edited by hand. Settings → AI now shows for every API backend whether a key is saved; a saved one can be forgotten, so the environment's is used again, and a new one saved in its place, without removing the backend. The CLI does the same with ai key <name> (--key-env, --key-stdin or --forget), and never prints the key. A new key is read back after saving, and a forget that a locked or failing keychain can't confirm says so instead of reporting success.
Refs #1358
`rebuild --continue-in`, `rebuild_start` on a project and `rebuild_question_ask` now say which AI works when the saved one is off or gone, as the app does.
A project can allow, ask about or refuse each kind of builder action (web, commands, outside files, publishing, deletes outside the project, system changes, other tools); a kind it hasn't chosen follows Auto mode as before. `project_approvals_set` sets them, and an agent can only make a kind stricter, including through our CLI from its own shell. "Always" on a push, delete or system card allows that whole kind, and pushes are read word by word in every shell form.
`mcp --restricted` leaves out tools that act on the machine or reach the network, going by what each declares; `--allow-web` and `--allow-capture` turn on their own groups. Closes#855. Closes #856.\n\nCo-authored-by: Dev Maktuporia <devmaktuporia@gmail.com>
`rebuild --backend <name>` uses a configured backend of that name as it is, and registers an installed agent whose name matches when it is not added yet; an unknown name adds nothing. Follow-up to #819 (R5.5).
`rebuild` looks for and saves a coding agent only when no enabled AI can build, so a run with an API backend no longer adds Claude Code to the settings; a refused command changes nothing (R5.5).
GitHub Copilot CLI can be a coding agent over ACP, with its models chosen through the shared agent model catalogue; options that could bypass the app's tool restrictions are refused, and agents share investigation findings safely.
`craft-anything-cli capabilities` lists each tool with `available`, `needs_target` and `reason`. To show target tools as usable before anything is open, it marked every target tool available and dropped its reason. That also covered tools Clean room refuses, so in Clean room `native_function_pseudocode` read as available with no reason, though the engine refuses it.
Only the "nothing is open yet" refusal is waived now. A target tool the mode refuses keeps `available: false` and its Clean room reason, with `needs_target: true` as before. In Deep mode nothing changes.
**Verified:** a new CLI test runs `capabilities` in Clean room (the tool is unavailable with a reason) and with `--deep` (available, no reason). `cargo test -p craft-anything-cli` and clippy pass.
Fixes#249
A native, pure-Rust app that shows anyone how a piece of software works, with
evidence-backed answers, then helps them rebuild it. It ships a desktop app, a
CLI and an MCP server, all driven by one engine.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>