dev-3.0vsTessera
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
dev-3.0
h0x91b · Agent harness
OSS
Panel
6.30 spec wins
- Reliability
- 6.0
- Usefulness
- 6.5
- Cost
- 7.7
- Longevity
- 5.2
“Your coding agents are now cards on a Kanban board, which means they will be moved to Done by someone who has not read them.”
Tessera
Horang Labs · Agent harness
OSS
Panel
6.31 spec wins
- Reliability
- 5.8
- Usefulness
- 6.5
- Cost
- 6.8
- Longevity
- 5.8
“A paired phone continues the same sessions, so the agent can now wait for your approval while you are asleep.”
Spec by spec
| Spec | dev-3.0 | Tessera |
|---|---|---|
| Architecture | ||
| Category | Agent harness | Agent harness |
| Runs | local | local |
| Platforms | macos, linux, windows | macos, linux, windows, web |
| Context window | not documented | not documented |
| Protocols | ||
| MCP client | No | No |
| MCP server | No | No |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | YesFiles are changed by the agent running in each card's worktree, not by dev-3.0 itself. | YesFiles are changed by the Claude Code, Codex or OpenCode session Tessera runs in each worktree; Tessera adds its own file and diff editor on top. |
| Git operations | YesEvery card is a real git worktree and branch; the agent opens the pull request and enables auto-merge, and the card then shows the PR number and CI state. | Yes |
| Browser control | No | No |
| Sandboxed execution | No | No |
| Multi-agent orchestration | Yes | YesA lead agent can create worktrees and launch, read and prompt parallel worker sessions through the /tessera-cli command. |
| Headless / CI mode | No | No |
| Models | ||
| Backbone | Claude Code, Codex, Gemini, Cursor Agent, opencode | Claude Code, Codex, OpenCode |
| Bring your own model | Yes | Yes |
| Local models | No | No |
| Cost | ||
| Pricing model | byok | byok |
| Starts at | $0/mo | $0/mo |
| Free tier | Yes | Yes |
| Bring your own key | Yes | Yes |
| Openness | ||
| Open source | Yes | Yes |
| License | Apache-2.0 | AGPL-3.0 |
| GitHub stars | 301 | 311 |
Which one would each critic pick
| Critic | dev-3.0 | Tessera | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 6.5 | 6.8 | Tessera — Pick Tessera if you want agent work to move through visible stages; pick a single session if a board with five columns would only be a board you stopped updating. |
| El Crítico | 5.8 | 5.3 | dev-3.0 — Every card cuts a fresh worktree from the same base branch, so five agents working at once produce five branches that were each written as though the others did not exist. |
| El Profesor | 6.8 | 6.5 | dev-3.0 — Review is structured as a feedback channel rather than a report: inline comments on a whole-branch diff are pushed back into the producing agent, and separate read-only hunters comb the same diff. |
| La Inversora | 5.8 | 5.8 | no preference |
| La Jefa | 6.0 | 5.8 | dev-3.0 — Nothing to buy across sixty desks, and the one thing that reaches my existing process is a card that shows its pull-request number and live continuous-integration state. |
| El Hacker | 7.3 | 7.5 | Tessera — Strong copyleft, which is the licence I want on something I depend on, and each backend takes a custom model identifier so I decide what is actually behind each session. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.