Agent orchestrator · Orchestrator (Desktop / Web)
Up.computer
Up.computer is an Orchestrator (Desktop / Web) in the 2026 agents.dancingteeth catalog. Developers who want to talk ideas through with one orchestrator chat and have it queue tasks for background worker agents (Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, ACP agents) on their existing subscriptions, with worktrees, diff review, PRs, and computer use — free and local.
Last updated
Verified
Best for
Developers who want to talk ideas through with one orchestrator chat and have it queue tasks for background worker agents (Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, ACP agents) on their existing subscriptions, with worktrees, diff review, PRs, and computer use — free and local.
Skip if
You want a mature, multi-maintainer product (T3 Code upstream or Conductor), a published mobile app, cloud sandboxes or VMs (Backgrounder), or an orchestrator that bundles its own models.
Who it fits
- Developers who want to talk ideas through with one orchestrator chat and have it queue tasks for background worker agents (Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, ACP agents) on their existing subscriptions, with worktrees, diff review, PRs, and computer use — free and local.
- People who prefer a dedicated desktop coding surface
- Builders who start in the browser without a local IDE setup
Pros
Free MIT desktop app where an orchestrator chat turns your ideas into queued tasks that saved worker agents pick up in the background — on Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, or any ACP Registry agent, each on your own subscription with no resale or markup; per-thread git worktrees, diff review, and commit/push/PR from the app; tasks by status/tag plus scheduled tasks; cross-agent review hand-offs; managed browser and desktop computer use for every agent; built-in MCP server so outside agents (terminal Claude Code/Codex, ChatGPT) can start and steer threads; all chats in one local database; signed macOS (Apple Silicon + Intel), Windows, and Linux builds that self-update.
Cons
Fork of T3 Code (pingdotgg/t3code) — same runtime with a task/orchestrator layer on top, internals still say T3; very early (v0.0.x, mostly a single maintainer, ~90 stars); orchestration only — install and log in to at least one agent CLI first; new threads default to Full access permissions; product usage data goes to PostHog by default (opt out via T3CODE_TELEMETRY_ENABLED=false); unsigned Windows installer; mobile app not published yet; catalog has not hands-on verified.
Facts
- Locality:
- Hybrid (local + cloud)
- Surfaces:
- Desktop, Web
- Maturity:
- Experimental
- Open source:
- Source available
- Free tier:
- Free option available
- MCP:
- Model Context Protocol support
- Verified:
- Oct 2026
Agent standards & memory
Compare one neighbor first
Vendor pages sell hard. Read one alternative on this site, then leave for the official link if the fit still holds.
Official links
Alternatives
Related tools
Frequently asked questions
What is Up.computer?
- Up.computer is an Orchestrator (Desktop / Web) covered in the agents.dancingteeth 2026 catalog. Free MIT desktop app where an orchestrator chat turns your ideas into queued tasks that saved worker agents pick up in the background — on Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, or any ACP Registry agent, each on your own subscription with no resale or markup; per-thread git worktrees, diff review, and commit/push/PR from the app; tasks by status/tag plus scheduled tasks; cross-agent review hand-offs; managed browser and desktop computer use for every agent; built-in MCP server so outside agents (terminal Claude Code/Codex, ChatGPT) can start and steer threads; all chats in one local database; signed macOS (Apple Silicon + Intel), Windows, and Linux builds that self-update.
Who is Up.computer best for?
- Developers who want to talk ideas through with one orchestrator chat and have it queue tasks for background worker agents (Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, ACP agents) on their existing subscriptions, with worktrees, diff review, PRs, and computer use — free and local.
When should I skip Up.computer?
- You want a mature, multi-maintainer product (T3 Code upstream or Conductor), a published mobile app, cloud sandboxes or VMs (Backgrounder), or an orchestrator that bundles its own models.
What are the main trade-offs of Up.computer?
- Pros: Free MIT desktop app where an orchestrator chat turns your ideas into queued tasks that saved worker agents pick up in the background — on Claude Code, Codex, Cursor, Grok Build, OpenCode, Pi, or any ACP Registry agent, each on your own subscription with no resale or markup; per-thread git worktrees, diff review, and commit/push/PR from the app; tasks by status/tag plus scheduled tasks; cross-agent review hand-offs; managed browser and desktop computer use for every agent; built-in MCP server so outside agents (terminal Claude Code/Codex, ChatGPT) can start and steer threads; all chats in one local database; signed macOS (Apple Silicon + Intel), Windows, and Linux builds that self-update. Cons: Fork of T3 Code (pingdotgg/t3code) — same runtime with a task/orchestrator layer on top, internals still say T3; very early (v0.
Does Up.computer support AGENTS.md, SKILL.md, or MCP?
- This card lists AGENTS.md as Delegates to agents, SKILL.md as Delegates to agents, and rules/memory as Local database of every thread across agents; task queue and status/tag routing; per-thread worktree/branch state; wraps underlying agent harness memory and skills.. Free options: 100% Free (Open-source, MIT; BYO agent subscriptions, no markup)..
Someone asks you about vibe-coding software? Share this site with them — we are adding more useful data regularly. agents.dancingteeth.net