shep
“The failure was traced to override state remaining undefined rather than defaulting to the displayed interactive agent, and was fixed so the selected interactive agent (Claude Code) is actually used at bootstrap instead of falling through to a 'dev' agent type that cannot run interactive sessions.”
team — shep-ai
Why they built it
The team built shep as an AI software-development agent to automate repetitive feature implementation, code generation, and repository-management tasks so developers spend less time on manual coding, with the agent orchestrated through a LangGraph state machine and shipped as installable CLI tooling.
What worked
- ✓The agent ships as a daemon-backed CLI with a Next.js control surface, and the team maintains a disciplined LESSONS.md postmortem compendium where every shipped regression is captured with the exact user-visible symptom, root cause, and the fix that landed.
What broke or was painful
- ✗The agent default fallback chain broke on bootstrap: users got stuck with the error 'Agent type dev does not support interactive sessions' even though the picker displayed 'Claude Code · Sonnet 4.6', because the override state stayed undefined when the user never clicked to confirm, so the system silently used the non-interactive 'dev' agent instead of the displayed one.
The result
The failure was traced to override state remaining undefined rather than defaulting to the displayed interactive agent, and was fixed so the selected interactive agent (Claude Code) is actually used at bootstrap instead of falling through to a 'dev' agent type that cannot run interactive sessions.
What they'd do differently
Stopped treating an unconfirmed picker selection as undefined and instead resolved the displayed agent as the effective default, preventing a silent fallback to an incompatible agent type.