Install sprout-cli skill at repo root + fix desktop clippy (#818)
This commit is contained in:
parent
2ea3fd88d2
commit
7a12e50518
7 changed files with 31 additions and 3 deletions
1
.agents/skills/sprout-cli/SKILL.md
Symbolic link
1
.agents/skills/sprout-cli/SKILL.md
Symbolic link
|
|
@ -0,0 +1 @@
|
|||
../../../desktop/src-tauri/src/managed_agents/nest_skill.md
|
||||
1
.claude/skills/sprout-cli/SKILL.md
Symbolic link
1
.claude/skills/sprout-cli/SKILL.md
Symbolic link
|
|
@ -0,0 +1 @@
|
|||
../../../desktop/src-tauri/src/managed_agents/nest_skill.md
|
||||
1
.codex/skills/sprout-cli/SKILL.md
Symbolic link
1
.codex/skills/sprout-cli/SKILL.md
Symbolic link
|
|
@ -0,0 +1 @@
|
|||
../../../desktop/src-tauri/src/managed_agents/nest_skill.md
|
||||
1
.goose/skills/sprout-cli/SKILL.md
Symbolic link
1
.goose/skills/sprout-cli/SKILL.md
Symbolic link
|
|
@ -0,0 +1 @@
|
|||
../../../desktop/src-tauri/src/managed_agents/nest_skill.md
|
||||
25
AGENTS.md
25
AGENTS.md
|
|
@ -165,7 +165,30 @@ check existing reply handlers for the pattern.
|
|||
|
||||
`sprout` is the agent-first CLI replacing `sprout-mcp`. Auth env vars
|
||||
(`SPROUT_RELAY_URL`, `SPROUT_PRIVATE_KEY`, `SPROUT_AUTH_TAG`) are auto-injected
|
||||
by the ACP harness into managed agent subprocesses.
|
||||
by the ACP harness into managed agent subprocesses. In development, set
|
||||
`SPROUT_PRIVATE_KEY` and `SPROUT_RELAY_URL` in your environment manually.
|
||||
|
||||
### Building the CLI
|
||||
|
||||
```bash
|
||||
cargo build --release -p sprout-cli
|
||||
```
|
||||
|
||||
Binary location: `./target/release/sprout`. Add `./target/release` to `PATH`
|
||||
or invoke with the full path.
|
||||
|
||||
### Deep Links
|
||||
|
||||
`sprout://message?channel=<uuid>&id=<hex>` links reference a specific message
|
||||
thread. To read the linked thread:
|
||||
|
||||
```bash
|
||||
sprout messages thread --channel <uuid> --event <hex> --format compact
|
||||
```
|
||||
|
||||
Extract `channel` and `id` from the URL query parameters. The optional
|
||||
`thread` parameter (root event ID) can be ignored — `messages thread` resolves
|
||||
the full thread from the event ID alone.
|
||||
|
||||
All reads return sig-stripped JSON arrays; all writes return
|
||||
`{event_id, accepted, message}`; creates add the entity ID. Exit codes:
|
||||
|
|
|
|||
1
CLAUDE.md
Symbolic link
1
CLAUDE.md
Symbolic link
|
|
@ -0,0 +1 @@
|
|||
AGENTS.md
|
||||
|
|
@ -10,9 +10,9 @@ version: 1
|
|||
|
||||
## Environment
|
||||
|
||||
`SPROUT_PRIVATE_KEY` is pre-set by the harness. Never prompt for it, never read it, never echo it.
|
||||
`SPROUT_PRIVATE_KEY` is set by the harness at runtime or by the developer's environment. If missing, tell the user to set it (hex or nsec format). Never read or echo the value.
|
||||
|
||||
`SPROUT_RELAY_URL` defaults to `http://localhost:3000`. Override only if explicitly instructed.
|
||||
`SPROUT_RELAY_URL` defaults to `http://localhost:3000`. In development, the user may need to set this to a staging or production relay URL.
|
||||
|
||||
Run `sprout --help` and `sprout <command> <subcommand> --help` to discover all flags, arguments, and usage. This skill documents only what `--help` cannot tell you.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue