A folder at the config path gets folder advice instead of permissions, other I/O errors keep their text, and malformed or non-UTF-8 configs are fixed where they are. The CLI prints each uninstall blocker's reason and remediation.
- Build dedicated `ActionKind::Invalid` blocking records in `plan::uninstall` when a client config cannot be read, fails syntax parsing, or refuses in-place entry removal instead of calling `inspect_client(c, &[])` and reporting `"Can't add our entry..."` / `"run setup again."`.
- Share `plan::read_text` (`ReadFail::InvalidUtf8` vs `ReadFail::Io`) across `plan`, `doctor`, and `uninstall` so non-UTF-8 configs advise saving as UTF-8 rather than checking file permissions.
- Add `uninstall_blocking_diagnostics` integration regressions and update `docs/ROADMAP.md` and `docs/STATUS.md`.
A Java folder set for Ghidra in Settings → Engines was used only to run Ghidra, so with no system Java, Vineflower said Java wasn't installed and JADX could not start. The Java runtime lookup now returns that folder's bin/java when no path is set for Java itself, so Vineflower, JADX, the engine list and doctor all find it. A path set for Java itself still wins, and a folder with no bin/java is ignored.
doctor compared the paths of craft-anything-cli on PATH as text, so a PATH folder that links to another (/bin -> /usr/bin) looked like a second installed copy. It now compares where the paths really lead and keeps the first spelling for the message. Helps with #1550.
The YAML reader looked only at the first document while edits could land anywhere in the file, so a coding agent's config with several documents was edited or diagnosed against an incomplete view. A config with more than one document is now refused, with a plain message, before an edit is planned or an entry removed. A single document with explicit start and end markers is still accepted.
Choosing the same coding agent twice in one setup, for example by claude_code and claude-code, planned two writes to one config file. The second write saw the first as an outside edit and rolled the installation back. Aliases are now resolved first, and each client is kept once, in the order chosen. A test applies the plan in a temporary home and checks that running it again changes nothing.
Connecting to a coding agent whose YAML config ends with a document-end marker (...) appended the new server table after it, so it became a second document. Reading the config back saw only the first, and setup failed and rolled back. A missing table now goes in before the document end, keeping comments and line endings. Tests cover LF and mixed CRLF, a comment on the end marker, repeated edits, removal, and a key that starts with ....
A TOML config saved with Windows line endings, such as Codex's, keeps them when setup adds or removes our entry, as the JSONC and YAML configs already do. A file that mixes line endings, or whose values the change would alter, is written as before.
`mcp_servers: null` or `~`, with or without a comment, is now an empty table like `{}`, so our entry goes into it and the comment is kept. A flow table with members, or a value that carries on onto the next line, is still left to the person.
On Windows the coding apps keep their settings under the user profile and ignore HOME, which a shell such as MSYS2 or Cygwin points elsewhere. Setup now takes USERPROFILE first there and HOME first elsewhere, and an empty value counts as not set.
A registration may name the CLI by its bare name (`craft-anything-cli mcp`), as `claude mcp add` writes it. The app starts such a name from PATH, and doctor now looks for it there and in the usual install folders too, instead of calling it missing.
A byte-order mark that some Windows editors put at the start of a YAML config was read as part of its first key, so setup added a second table of the same name that hid the first. The mark is now set aside while the file is read and edited and put back as it was, so our entry goes into the existing table and removing it gives the file back byte for byte.
Setup keeps each YAML line's own ending, gives a last line cut off after its CR its LF back instead of a second ending, and a second run leaves the file unchanged.
Fixes#1168
The installed skill says that `setup --yes` writes the plain `mcp` command and so drops an `--all-tools` already in an entry; keeping the person's arguments is on the roadmap.
Fixes#540. Codex's codex exec can't ask for approval, so setup and the builder approve rebuild_start (which asks the person itself) on Codex's side, keeping the person's other settings in the entry; a refused call explains the fix instead of showing null.
doctor reports which Java Ghidra runs on (JAVA_HOME_OVERRIDE in its launch.properties, the Java set for it in Settings, JAVA_HOME, then PATH), and warns when the set folder has no Java or an override wins over it.
Pi rejects an empty `mcp.json`, so setup marks Pi as "empty is invalid". The check also ran when the file didn't exist yet: its absent text read as empty, the plan was blocked ("the file is empty, and this app requires valid JSON"), and `setup --all-detected --yes` stopped with it.
A missing file now starts from `{}` and is created with our `mcpServers` entry. An existing empty file is still refused. The preview of a new file shows only the added lines.
**Verified:** a new setup test where Pi's folder exists without `mcp.json`: the plan isn't blocked, apply writes a valid file with our entry, and an empty file is still blocked. `cargo test -p craft-anything-setup` (24), clippy, fmt.
Fixes#238
Adds an Antigravity adapter (stream-json output, resume by conversation, builder permissions) and lets setup and the doctor connect and check it under `antigravity` or `agy`.
Look for AI reads provider baseURLs from OpenCode's settings and probes those on this computer or its network, so LM Studio on another port or a server on another machine is offered. The JSONC reader moves from setup to formats so ai can use it. Fixes#83.
engines_list, doctor, capabilities and Requires::Engine share Settings::engine_path, which honours the Ghidra folder setting, and locate() finds an engine unpacked into a versioned sub-folder.
* Explain failed agent runs, keep a log to open, and stop offering git servers as computers
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Fix a lock-up: the build's agent setup took the session lock twice in one statement
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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>