Marcode

Marcode is a maintained fork of T3 Code, an agent harness control surface for controlling coding agents from the web, mobile, and desktop.

Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, and OpenCode. If they're set up on your computer, Marcode can control them.

Installation

Warning

Marcode currently supports Codex, Claude, Cursor, Grok Build and OpenCode. Install and authenticate at least one provider before use:

• Codex: install Codex CLI and run codex login
• Claude: install Claude Code and run claude auth login
• Cursor: install Cursor CLI and run agent login
• Grok Build: install Grok Build CLI and run grok login
• OpenCode: install OpenCode and run opencode auth login

Try it out (install-free)

The easiest way to test Marcode is to run the server in your terminal (requires Node.js 22.16+, 23.11+, or 24.10+).

The CLI keeps the upstream-compatible t3 package name:

npx t3@latest

This launches the backend and local web app to control your agents.

Tip: Use npx t3@latest --help for the full CLI reference.

Run from source

Install Vite+ and the project dependencies:

vp i
vp run dev

For the desktop development surface:

vp run dev:desktop

Published desktop builds will appear in Marcode Releases.

Status

Marcode is early and under active development. Expect bugs and incomplete surfaces.

Documentation

Full docs live in docs/. There's no docs site yet.

• Install and first run
• Permission modes
• Keyboard shortcuts
• Remote access from a phone or another machine
• Keeping app and server in sync
• Source control integrations
• Unified workspace sidebar
• Multiple accounts: Codex · Claude
• Linux: run Marcode as a background service

Building from source? Start at docs/internals/overview.md.

Upstream synchronization

Marcode tracks the official T3 Code repository as upstream.

The scheduled Upstream Sync workflow detects upstream changes and prepares reviewable integration work. It never resolves conflicts automatically or pushes to main. Conflicted syncs create a GitHub Issue for manual follow-up; clean syncs create a draft pull request.

See the upstream sync runbook for the integration policy and recovery steps.

Contributing

Read CONTRIBUTING.md before opening an issue or pull request. The repository's Issues are enabled for bug reports and follow-up work.

Need support? Join the Discord.