Shell-native dispatch in v0.4.0 · gradually gains a TUI skin · shell mode stays forever
v0.4.0 — Shell-Native Dispatch
✨ Second Magic Moment
$ synlynk dispatch claude --story 14
▶ [job:1] claude → story#14 (feat/auth-fix)
worktree: .synlynk/worktrees/feat/auth-fix
context: .synlynk/context-claude.md injected
running in background — PID 48291
$ synlynk dispatch gemini --story 15
▶ [job:2] gemini → story#15 (feat/tests)
$ synlynk jobs
job:1 claude story#14 running 4m12s
job:2 gemini story#15 running 1m03s
$ synlynk logs --job 1
← tails captured stdout in real time
$ synlynk shell --story 14
← jump into worktree to unblock agent
How it works: nohup + PTY-less exec (claude --print / gemini --quiet).
PID tracked in .synlynk/jobs.json. stdout captured via tee → telemetry.
No daemon required. Works with existing exec infrastructure.
v0.4.0 — The Two Magic Moments
✨ Magic 1 — Hybrid Workgroup Discovered
synlynk init detects:
✓ Claude Code — capability: Architect, Builder
✓ Gemini CLI — capability: Builder, Verifier
✓ Codex — capability: Builder
→ "You have a 3-agent Hybrid Workgroup.
Quota problems solved. Let's assign roles."
✨ Magic 2 — Parallel Dispatch from Shell
synlynk run --trio
▶ Architect (claude) → generating task-packet.md
▶ Builder (gemini) → implementing feat/auth-fix
▶ Verifier (codex) → running tests on story#13
← three agents running in parallel, right now,
from your shell, no extra tooling needed
SHELL MODE — permanent parallel track (never removed)
For developers who live in their shell and don't want to switch UX layers:
synlynk dispatch,
synlynk jobs,
synlynk logs,
synlynk shell
all remain first-class CLI commands forever.
The TUI is an opt-in surface, not a replacement.
Power users get the full workgroup in their existing terminal. No layers, no context switching.