Skip to content

feat: add dispatching-coding-agents bundled skill#1166

Open
sarahwooders wants to merge 8 commits intomainfrom
sarah/add-dispatching-coding-agents-skill
Open

feat: add dispatching-coding-agents bundled skill#1166
sarahwooders wants to merge 8 commits intomainfrom
sarah/add-dispatching-coding-agents-skill

Conversation

@sarahwooders
Copy link
Contributor

@sarahwooders sarahwooders commented Feb 26, 2026

Summary

  • Adds a new bundled skill dispatching-coding-agents that teaches agents how to shell out to Claude Code (claude) and Codex (codex) CLIs as stateless sub-agents
  • Covers non-interactive execution (claude -p, codex exec), model selection, session resumption, the history-analyzer subagent for mining past sessions, and dispatch patterns (parallel research, cross-agent review, etc.)
  • Includes the core philosophy: Letta Code agents are the experienced manager with persistent memory, while Claude Code/Codex are high-intellect but stateless workers that need context and guidance

Test plan

  • Verify skill is discovered after build (node build.js copies from src/skills/builtin/ to skills/)
  • Load skill via /skill dispatching-coding-agents and confirm SKILL.md renders correctly
  • Test claude -p and codex exec invocations from within a Letta Code session

🐾 Generated with Letta Code

sarahwooders and others added 5 commits February 26, 2026 12:24
Teaches agents how to shell out to Claude Code and Codex CLIs as
stateless sub-agents, including non-interactive execution, model
selection, session resumption, and the history-analyzer subagent.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
…g skill

Explains how to capture session IDs from Claude Code (--output-format json)
and Codex (grep session id from output), where session files live on disk,
and how to use the history-analyzer subagent to deep-dive into full session
data and persist insights to memory.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
…ing skill

Show end-to-end flows for both Claude Code and Codex: capture session ID
from output, construct the session file path, and pass the concrete path
to the history-analyzer subagent.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
Killed/timed-out claude -p sessions leave stale approval state that
causes "stale approval from interrupted session" errors on subsequent
runs. Using --no-session-persistence avoids this entirely since we're
using Claude Code as a disposable sub-agent.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
…stence

We want sessions persisted so history-analyzer can read them later.
The stale approval issue is solved by skipping permissions entirely
(safe in trusted repos for automated dispatch).

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
@sarahwooders sarahwooders requested a review from cpacker February 26, 2026 21:32
sarahwooders and others added 3 commits February 26, 2026 13:36
Based on testing: Codex handles large repos more reliably than Claude
Code and codex-5.3 is the preferred frontier model for dispatch tasks.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
The history-analyzer was using `MEMORY_DIR=[provided in assignment]`
which resolved to its own agent's memory directory. Changed to use
`$LETTA_PARENT_AGENT_ID` (same pattern as the reflection subagent)
so memory files are written to the parent agent's repo.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
…r-dispatch

Single-session analysis produces overly detailed memory that's better
represented by the code. Reflection already captures conversation
insights. Reserve history-analyzer for bulk migration during /init.

🐾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta <noreply@letta.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant