Catcrafts/Crafter.Debug
Watch
2
0
Fork
You've already forked Crafter.Debug
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: which app the client picks when other projects' apps run too

Browse source 
The consumer notes tell agents that commands pick their project's app
and how to reach another with -i, the README's discovery row says the
same, and the agent notes describe CRAFTER_DEBUG_PROJECT and how an app
is matched to its project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Jorijn van der Graaf 2026-11-01 18:33:59 +01:00
commit 98e92c1976
Signed by: jorijnvdgraaf
GPG key ID: 2937E59CDCC1BCFB
3 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
tooling/AGENTS.consumer.md
View file

@ -19,6 +19,7 @@ This app can be driven while it runs: call its commands, read and set its state,
- Requests run when the app calls `Debug::Pump()`, once per frame; `status` shows when it last did.
- Stopping the background `-r` task can leave the app running. Stop it with `quit`, or `quit --force` if its loop is stuck.
- Run long `wait`s in the background, and chain short steps with `&&`.
- Other projects' debug apps may be running too. Commands pick this project's app and leave the others alone, and `ls` marks this project's. `-i <name|id>` picks another project's app, or one of two copies of this one.
- `debugger` prints how to attach lldb or gdb for breakpoints and memory.
### Coding with it