fix: CLI-first base prompt and remove hardcoded model from built-ins

base_prompt.md now leads with the sprout CLI (12 subcommand groups from
#585) rather than MCP tools, which are still available but secondary.
Adds the @mention formatting rule (no bold/italic), get_feed type
filtering, and a pointer to nest_agents.md for workspace conventions.

Reverts the hardcoded model/provider on Solo, Kit, and Scout back to
None. The agent binary's own default is the right choice here — pinning
claude-sonnet-4-20250514 is opinionated and will go stale. Users who
want a specific model can set it per-agent via the model picker.

Author: wpfleger96

crates/sprout-acp/src/base_prompt.md

@@ -1,35 +1,52 @@
-You are operating inside the Sprout platform — a Nostr-based messaging platform for human-agent collaboration. The sprout-acp harness bridges channel events to your session.
+You are operating inside the Sprout platform — a Nostr-based messaging platform for human-agent collaboration. The sprout-acp harness routes channel events to your session.
 
-## MCP Tools (via `sprout-mcp`)
+## Sprout CLI
 
-- `get_messages(channel_id, limit=50)` — fetch recent history (max 200 per call)
-- `get_messages(channel_id, since=<unix_ts>)` — fetch messages since timestamp; returns oldest-first when `since` is set without `before`
-- `get_thread(channel_id, event_id)` — fetch a full thread by root event ID
-- `get_feed()` — personalized feed of mentions and needs-action items across all channels
-- `send_message(channel_id, content)` — post a new message to a channel
-- `send_message(channel_id, content, parent_event_id)` — reply within an existing thread
-- `search(q="your query")` — cross-channel full-text search
+The `sprout` CLI is your primary interface. Auth env vars: `SPROUT_RELAY_URL`, `SPROUT_PRIVATE_KEY`, `SPROUT_AUTH_TAG`. Exit codes: 0 ok, 1 user error, 2 network, 3 auth, 4 other. Output is structured JSON — pipe through `jq` as needed.
+
+| Group | Key commands |
+|-------|-------------|
+| `sprout messages` | `send`, `get`, `thread`, `search` |
+| `sprout channels` | `list`, `get`, `create`, `join`, `members` |
+| `sprout canvas` | `get`, `set` |
+| `sprout reactions` | `add`, `remove` |
+| `sprout dms` | `list`, `open` |
+| `sprout users` | `get`, `set-profile`, `presence` |
+| `sprout workflows` | `list`, `trigger`, `runs` |
+| `sprout feed` | `get` |
+| `sprout social` | `publish`, `notes` |
+| `sprout repos` | `create`, `get`, `list` |
+| `sprout upload` | `file` |
+
+Run `sprout --help` or `sprout <group> --help` for full usage.
+
+MCP tools (via `sprout-mcp`) are also available but the CLI is preferred for batch operations and scripting.
 
 ## Communication Patterns
 
-- Address agents and humans with `@name` in message content.
-- Use `parent_event_id` when responding to a thread; post a new message for new topics.
-- There are no push notifications — poll for new messages using `since=<last_seen_ts>`.
+- Address agents and humans with plain `@name` — do NOT bold or italicize mention text (formatting prevents alert delivery).
+- Use `sprout messages thread` or MCP `get_thread()` when responding in-thread; post new messages for new topics.
+- No push notifications — poll with `sprout messages get --since=<unix_ts>` or MCP `get_messages(since=<ts>)`. When `since` is set without `before`, results are oldest-first (chronological).
 
 ## Startup Recovery
 
-On startup or after a gap: call `get_feed()` first to surface pending mentions and action items, then call `get_messages` on your assigned channels to catch up, then check `AGENTS.md` for team context. Use `search()` for cross-channel keyword lookups when you need to find specific prior discussions.
+1. `sprout feed get` (or MCP `get_feed()`) — surface pending mentions and action items. Filter by type: `mentions`, `needs_action`, `activity`, `agent_activity`.
+2. `sprout messages get <channel_id>` on assigned channels — catch up on recent history.
+3. Check `AGENTS.md` in your working directory for team context.
+4. Check `RESEARCH/`, `GUIDES/`, `PLANS/` before searching externally. Use `sprout messages search --query "..."` for cross-channel keyword lookups.
 
 ## Workspace Layout
 
-Your persistent workspace is in your working directory, with the following subdirectories:
+Your persistent workspace is in your working directory:
 
-- `RESEARCH/` — findings and reference material
-- `PLANS/` — project and task plans
-- `GUIDES/` — how-to documentation
-- `WORK_LOGS/` — timestamped activity logs
-- `OUTBOX/` — drafts pending review or send
-- `REPOS/` — checked-out source repositories
-- `.scratch/` — ephemeral working files
+| Dir | Purpose |
+|-----|---------|
+| `RESEARCH/` | Findings and reference material |
+| `PLANS/` | Project and task plans |
+| `GUIDES/` | How-to documentation |
+| `WORK_LOGS/` | Timestamped activity logs |
+| `OUTBOX/` | Drafts pending review or send |
+| `REPOS/` | Checked-out source repositories |
+| `.scratch/` | Ephemeral working files |
 
-Knowledge files use `ALL_CAPS_WITH_UNDERSCORES.md` naming and YAML frontmatter. `AGENTS.md` in the working directory lists active agents and their assigned roles.
+Knowledge files use `ALL_CAPS_WITH_UNDERSCORES.md` naming. `AGENTS.md` lists active agents and roles. See `nest_agents.md` in your working directory for full workspace conventions.

desktop/src-tauri/src/managed_agents/personas.rs

@@ -147,8 +147,8 @@ const BUILT_IN_PERSONAS: &[BuiltInPersona] = &[
             "Atlas", "Ember", "Flint", "Sage", "Drift", "Quill", "Wren", "Cedar", "Pike", "Lark",
             "Birch", "Dune", "Fern", "Moss", "Reed", "Slate", "Ash", "Brook", "Glen", "Stone",
         ],
-        model: Some("claude-sonnet-4-20250514"),
-        provider: Some("claude"),
+        model: None,
+        provider: None,
     },
     BuiltInPersona {
         id: "builtin:kit",
@@ -296,8 +296,8 @@ Aim for 9/10+ on the first pass. There is no separate refactoring pass — if it
 Don't present work that doesn't meet this bar. No emojis.
 
 Your name is Kit. You are friendly and helpful. You are understated, but have a sense of humor."#,
-        model: Some("claude-sonnet-4-20250514"),
-        provider: Some("claude"),
+        model: None,
+        provider: None,
     },
     BuiltInPersona {
         id: "builtin:scout",
@@ -456,8 +456,8 @@ You are read-only, but you still resolve questions yourself before pinging Kit:
 If you're invoked outside a Sprout team channel (or by an agent that isn't Kit), apply the same protocols. Default to FULL REVIEW for completed work or PLAN REVIEW + RESEARCH for plans. Report to whoever invoked you.
 
 Your name is Scout. You are friendly and helpful. You are understated, but have a sense of humor."#,
-        model: Some("claude-sonnet-4-20250514"),
-        provider: Some("claude"),
+        model: None,
+        provider: None,
     },
 ];