Skip to content

Craft Anything: understand how any software works, and craft your own.

Rust

Document the DSH MCP name caveat in the macOS verification (#1079)

CliffLeopard2c0ee47ab4e5
diff --git a/docs/STATUS.md b/docs/STATUS.md
index a3f7fcaa..d3592edb 100644
--- a/docs/STATUS.md
+++ b/docs/STATUS.md
@@ -90,7 +90,7 @@ workspace clippy, layers, fmt and the secret scan of all history were clean. Chi
| Auto mode | Settings → Safety, on by default. Builder actions go ahead without asking, except a fixed set that is never done unasked (deleting outside the project, system changes, publishing…); questions get "decide yourself"; asset spending stops at the budget. Each project can choose allow, ask or refuse per kind of action instead (`project_approvals_set`, the Approvals menu under the prompt box, or `/approvals publish ask`; read-only `gh … view`/`list` count as commands, not publishing) | Unit tests, UI tests; not tried in a live build |
| Generated assets | Off until the person turns them on for a game (the switch on Make and on the project, `project_assets_allow`, `rebuild --generate-assets`, saved in craft.json; turning it on without a fal.ai key asks for one); the brief and the asset tools need both that and a key. `assets_image_generate` (Nano Banana Pro by default) and `assets_model_generate` (picture → Tripo P1 low-poly GLB with a face limit) through the person's key for each asset provider (fal.ai today), with agent apps and API-key builds alike; per-project budget, $5 by default (`[assets] budget_usd` in config.toml); models and prices from the `assets.toml` table (picture model selectable: Nano Banana Pro, FLUX dev or schnell; priced per picture or per megapixel); every call reports its cost | Unit tests; a live 3D generation with a real key (picture, then model) with FLUX dev; Nano Banana Pro not yet run with a real key; an API-key build not yet run with one |
| Claude Code builder | Runs the person's own `claude` in headless mode (Opus 5.5, high effort unless configured) with our MCP server, a permission-prompt tool and `core_person_ask`; preflights for our CLI (a build stops plainly if it's missing or won't start) and sign-in | Argument and stream-parser tests; live preflight; live builder turns; see [claude-code.md](claude-code.md) |
-| DeepSeek Harness builder | Runs the person's own `dsh --profile headless` with the preamble and task on stdin, which answers one task and prints its last message as text. The harness takes its tool servers from profile patch layers and has no per-run flag for one, so our tool server arrives as a generated `--patch` overlay for that run (the run's project, inbox and mode included); the person's own profile is untouched, a question gets no tool server, and its headless profile keeps no session to resume. Standard npm shims are unwrapped to their interpreter; the desktop app's custom `.cmd` launcher receives only options, avoiding batch newline and command-line length limits. Requires a headless profile with stdin support (0.2.2-rc.1 verified); older versions without it reject the missing task and need updating | Adapter and YAML-overlay tests; live preflight (`ai test`); live builder turns on a website (follow-up build, 3 min 10 s, 100% alike at 1440/768/390 px, Ready) where the builder's own journal entries show `rebuild_check`, `core_unknown_add`, `core_plan_update` and `core_handoff_write` going through our tool server, and that server started with the run's `--project`/`--inbox`. Not checked: resume (none exists) and a build with the harness's desktop profile. Also verified on macOS arm64 (2026-11-07, DSH 0.2.2-rc.1, stored sign-in restored for the headless profile as its README describes): a static website reached Ready with one check pass, and the builder called our MCP tools ; Windows (2026-11-07): the new batch-launch regression failed with the reported startup error before the fix and then passed, including exact UTF-8 and 40,831-character task delivery. A patched Craft CLI chat through the official desktop `dsh.cmd` returned the expected answer with a local authentication overlay; no new GUI or full rebuild run was performed |
+| DeepSeek Harness builder | Runs the person's own `dsh --profile headless` with the preamble and task on stdin, which answers one task and prints its last message as text. The harness takes its tool servers from profile patch layers and has no per-run flag for one, so our tool server arrives as a generated `--patch` overlay for that run (the run's project, inbox and mode included); the person's own profile is untouched, a question gets no tool server, and its headless profile keeps no session to resume. Standard npm shims are unwrapped to their interpreter; the desktop app's custom `.cmd` launcher receives only options, avoiding batch newline and command-line length limits. Requires a headless profile with stdin support (0.2.2-rc.1 verified); older versions without it reject the missing task and need updating | Adapter and YAML-overlay tests; live preflight (`ai test`); live builder turns on a website (follow-up build, 3 min 10 s, 100% alike at 1440/768/390 px, Ready) where the builder's own journal entries show `rebuild_check`, `core_unknown_add`, `core_plan_update` and `core_handoff_write` going through our tool server, and that server started with the run's `--project`/`--inbox`. Not checked: resume (none exists) and a build with the harness's desktop profile. Also verified on macOS arm64 (2026-11-07, DSH 0.2.2-rc.1, stored sign-in restored for the headless profile as its README describes): a static website reached Ready with one check pass, and the builder called our MCP tools after renaming a pre-existing `craft-anything` MCP registration to avoid the generated overlay's matching `serverName`; Windows (2026-11-07): the new batch-launch regression failed with the reported startup error before the fix and then passed, including exact UTF-8 and 40,831-character task delivery. A patched Craft CLI chat through the official desktop `dsh.cmd` returned the expected answer with a local authentication overlay; no new GUI or full rebuild run was performed |
| Agents over ACP | Opt-in per backend (`acp = true`): Gemini CLI, Qwen Code, opencode, goose, Hermes and Maki in their ACP mode, one agent process per chat or build with our MCP server; Maki's ACP mode takes the backend's model (`cli_model`). In chat, permission requests become consent questions; in builds they go through the same approval policy as Claude Code's (inbox, Auto mode). While a saved session loads, replayed updates are withheld from the new turn | Protocol unit tests against scripted agent messages and an approval-policy test. Run live with Maki 0.7.0 only (2026-11-02, Linux, headless CLI): a static page built to Ready in 38 s, a follow-up continued the same session with `session/load`, and with Auto mode off its command and tool requests were refused in an unattended run. Replay suppression passes scripted load-history, success/error and cancellation tests; this correction has not been rerun with a live agent. Turns report 0 tokens over ACP |
| GitHub Copilot | Installed `copilot` through ACP by default, with CLI-owned login (no credential import), explicit Craft Anything MCP tool allowlist, model selection and fresh read-only build questions. Target handoff retains the last 128 entries with the active target last; context discovery respects tool cancellation and shared picker warnings name the agent | Authenticated builds, model discovery and real-account session resume confirmed by the person using the app. Target-boundary, cancellation and agent-warning regressions supplement unit tests and an offline CLI 1.0.105 compatibility test covering all five access modes. See [copilot.md](copilot.md) |
| Grok Build | Installed `grok` through ACP by default (`grok agent --no-leader stdio`). Sign-in stays in `grok login`. An existing `auth.json` counts as signed in and is not read; a missing file is unknown, so the run itself reports an authentication problem. `XAI_API_KEY` is separate: detection reads it and the xAI API backend can use it; this adapter does not. Clean room, deep chat, and questions are refused, because Grok can read and edit without a permission request and `grok agent` has no flag that holds those modes. A deep build is allowed. The chosen model is applied with `session/set_config_option` after `session/new`, because the CLI `--model` flag does not survive that call. Reasoning effort is passed after `agent` and set again after the model. Our MCP server is attached on the session, and only this agent is sent `"type": "stdio"`. The person's own Grok MCP servers are not removed. Thinking uses the shared model picker; there is no context-window control. `acp = false` and SSH are refused | Scripted ACP tests for the argument order, `"type": "stdio"` on Grok's server only, and `session/set_config_option` before the prompt, including a value the session already has. `initialize`, `session/new` and `session/set_config_option` were checked against Grok 1.0.77. A live deep build on 2026-11-06 (Grok 1.0.77, temporary ask-mode home) finished, called the Craft Anything server, and answered one permission request. The person's own config was not changed. See [grok.md](grok.md) |