docs: competitive teardown — Symphony vs TaskYou#602
Open
bborn wants to merge 1 commit into
Open
Conversation
Compares anantjain-xyz/symphony-rust against ty across product posture, GUI architecture, and feature gaps. Key findings: - GUI stacks are near-identical (both Tauri 2 + React + TS); no rearchitecture needed. Our TUI-first / fully-scriptable posture is the real differentiator. - Highest-value borrowables are unattended-run robustness features: automatic exponential-backoff retry with error context, AI-provider rate-limit/token awareness, and editable prompt templates. - Documents our moats (TUI-first, scriptable CLI/MCP, worktrees, 6 executors, SSH, project-context caching, extensions) to avoid regressing them. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Comparison of Symphony (
anantjain-xyz/symphony-rust) against TaskYou, per task #4360. Addsdocs/comparisons/symphony.md.The brief asked two things: what should we copy/borrow, and is their GUI built better than ours.
Key findings
On the GUI question — no, their stack is essentially identical to ours. Both are Tauri 2 + React + TypeScript (+ Tailwind/shadcn-style + SSE). We are not behind on GUI technology. The real difference is posture: Symphony's GUI is the only interface, while ours is one of three faces of the same engine. Our TUI-first + 100%-scriptable-CLI + MCP story is a genuine differentiator we should not dilute. Re-platforming the desktop GUI is explicitly not recommended.
What's worth borrowing (all engine-level features that benefit TUI/CLI/GUI at once):
internal/ui/retry.go), which undercuts our unattended-execution story. Biggest gap.Our moats (documented so we don't regress): TUI-first, scriptable CLI/MCP, local-first (no SaaS coupling), 6 executors vs 2, worktrees vs full clones, SSH + browser access, project-context caching, extensions ecosystem.
Files
docs/comparisons/symphony.md(new)Follow-ups
The doc ends with a ranked, standalone-task list (auto-retry → rate-limit tracking → prompt templates → retry-queue view → keychain). These are recommendations, not implemented here — this PR is the analysis only.
🤖 Generated with Claude Code