@debugbundle/cli 1.10.0 → 1.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -0
- package/dist/main.cjs +1753 -729
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -41,6 +41,24 @@ debugbundle incidents
|
|
|
41
41
|
debugbundle explain <incident-id> --source cloud
|
|
42
42
|
```
|
|
43
43
|
|
|
44
|
+
## Agent-aware setup
|
|
45
|
+
|
|
46
|
+
```sh
|
|
47
|
+
debugbundle setup --agent codex --agent claude-code --agent gemini-cli --agent muse-code --non-interactive
|
|
48
|
+
debugbundle doctor --json
|
|
49
|
+
debugbundle validate --fix --json
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Interactive setup offers detected agents as defaults. Repeat `--agent` to select integrations explicitly; JSON/non-interactive runs never prompt or infer new agents. Saved selections are reused. Codex, Gemini CLI, and Muse Code discover `.agents/skills/debugbundle/` directly. Claude Code receives a relative link under `.claude/skills/debugbundle/`, with an owned copy fallback when links are unavailable. Only selected native instruction files are managed; existing references/imports are preserved.
|
|
53
|
+
|
|
54
|
+
Keep `.debugbundle/agent-setup.json` with the canonical skill. It stores ownership hashes and selection, without credentials. Doctor and validate report canonical health separately from native discovery. Repair refreshes unchanged generated artifacts and preserves user edits for manual review. Repeated setup preserves the reviewed profile and cloud connection. Unknown legacy files are retained; exact known 1.10.0 templates can upgrade safely.
|
|
55
|
+
|
|
56
|
+
`debugbundle setup --agent none --non-interactive` removes only unchanged owned native integrations while retaining the canonical skill and configuration. Edited conflicts remain and require review. A stale `.debugbundle/agent-setup.lock` may be removed only after confirming no setup/repair is running.
|
|
57
|
+
|
|
58
|
+
Muse Code uses `--agent muse-code` (the agent executable is `muse`). It respects Muse's existing instruction precedence, creates `AGENTS.md` only when no supported instruction file exists, and shares owned blocks safely with other agents. Detection uses `.muse` project evidence; `AGENTS.md` alone does not select Muse. Trust the repository in Muse before expecting project skills to load, then check with `muse skills list --source project --json`.
|
|
59
|
+
|
|
60
|
+
Portable plugin skills complement the project's profile and workflows. Setup does not install plugins, configure MCP, or change authentication. Project plugin settings are hints; doctor does not prove a running agent loaded the skill. Restart/reload the agent after setup. See [the full contract and rollback guidance](https://github.com/debugbundle/debugbundle/blob/main/spec/agent-aware-cli-setup.md).
|
|
61
|
+
|
|
44
62
|
## Configuration
|
|
45
63
|
|
|
46
64
|
The CLI reads local project configuration from `.debugbundle/` and can use member-token authentication for connected cloud operations. Use `debugbundle connect` to configure cloud access, or pass `--auth-file` to commands that support explicit auth state.
|