Comparison
Shelbi vs Sketch.dev
Shelbi coordinates agents across your machines through a native macOS app or TUI. Sketch.dev is discontinued; its archived client shows a different approach to isolation and browser review.
As checked on November 5, 2026, Sketch.dev redirects to a discontinuation notice. Its repository is archived and no longer maintained. The developers introduced Shelley as its successor in January 2026. Shelley is a separate product; its current features and exe.dev plans should not be read as Sketch features or pricing.
Shelbi has continued shipping. The comparison below covers Shelbi through v0.13.3 and the archived Sketch client, with historical Sketch strengths described in that context.
At a glance
| Shelbi | Sketch.dev | |
|---|---|---|
| Architecture | Orchestrator coordinating a pool of workspaces | Coding agent with separate sessions |
| Isolation | Persistent git worktree per workspace | Docker container by default locally; gVisor was used for hosted sessions |
| Where work runs | Your local and SSH-connected machines | Local Docker; the hosted service is discontinued |
| Model / runner | Claude Code, Codex, and configurable CLI runners | Built-in model selection, including Claude and OpenAI models |
| Interface | Native macOS desktop app and terminal TUI | Archived terminal client and browser UI |
| Delivery | Task branches, workflow handoffs, review and PR actions | Commits pushed back to host-repository sketch/* branches |
| Task tracking | GitHub Issues or a local Markdown board | Session chat and diffs |
| Dependencies | Shelbi CLI, git and your chosen agent CLI; SSH for remotes | Local client normally needs Docker and model API access |
| License | MIT, open source | Apache-2.0, archived source |
| Cost | Free software; agent and machine costs are separate | No current hosted Sketch plan to buy |
Where Shelbi excels
Persistent workspaces across your machines. Each workspace keeps a stable git worktree and switches branches between assignments. It can reuse that checkout and build output across tasks. This does not promise that one agent conversation lasts forever. Sketch's developers identified tying the container's lifetime to the conversation as a limitation when explaining the move to Shelley.
A native desktop workflow, including remote projects. Shelbi's macOS app and TUI share application models and the command registry. The app brings the Issues board, Orchestrator, workspaces, Review and Settings into a native window. Remote workspaces attach from the sidebar, with a user shell, diff and editor access. A whole remote project can also open in the native window over one SSH relay per host, without port forwarding. This requires matching Shelbi versions; a mismatch opens the remote TUI in a terminal view with a notice.
Choose the agent harness. Shelbi has dedicated Claude Code and Codex
integrations and a generic CLI runner path. Other CLIs can be configured,
including aider, but integration depth varies. New orchestrator onboarding
lets you choose its harness and default model, then edit its instructions.
Sketch was not Claude-only: its archived CLI
has -model, -list-models and provider-key configuration. The distinction is
coordinating external agent CLIs versus choosing models inside Sketch.
A board and an explicit delivery workflow. Shelbi supports GitHub Issues and a local file system board, with configurable workflow statuses and agent handoffs. The New task dialog includes Title, Workflow, Status, Priority and Description, plus Let Orchestrator write this up. The per-project Changelog records shipped work. With Zen Mode off, review stays human-driven; opt-in Zen Mode lets the orchestrator triage eligible backlog and attempt merges under the project's merge policy, with checks tied to the reviewed commit. It is not a promise that every ready task merges automatically.
Use your existing development environment. Shelbi does not require Docker. Project configuration and agent instructions are editable files. A local board uses Markdown; a GitHub-backed board stores its issues on GitHub. Workspaces use the tools installed on their machines, which saves container setup but also makes those machines' environment and permissions part of the trust boundary.
Where Sketch.dev excels
These are strengths of the archived design, rather than reasons to expect ongoing service or maintenance.
Container isolation by default. Local Sketch normally put the agent in
Docker; the former hosted service used gVisor. This provided a containment
boundary beyond a git worktree. It was not an unconditional guarantee about
host secrets: the CLI also allowed host mounts and an -unsafe mode without
Docker. Shelbi's worktrees separate checkouts, not operating-system access;
any further sandboxing depends on the runner and environment you choose.
Editable browser diffs and inline feedback. Sketch's diff view let you edit the right-hand side directly and send line comments back to the agent through chat. Shelbi's diff view sends line comments back to the agent too, but it doesn't edit in place: Edit in <editor> does that, beside Reviewer, Approve and Reject. Sketch's integrated browser interaction remains a useful distinction.
Built-in browser and screenshot tools. Sketch could browse a page, capture it and inspect the image. Shelbi delegates browser automation and image understanding to its agent harness and tools. Those capabilities depend on your runner setup.
Choose Shelbi if…
You want an actively developed orchestrator with a native Mac app or TUI, persistent workspaces across machines you control, a task board, and a choice of agent harnesses. You want to choose between manual review and policy-driven automation without running a required container stack.
Choose Sketch.dev if…
You already maintain a Sketch installation or want to study and adapt its Apache-2.0 code, particularly its browser review and container workflow. For a new deployment, account for its discontinued service and unmaintained client. If you meant the team's current offering, evaluate Shelley and exe.dev separately, including their current pricing.