Powered by T3 CodeandCodingPhase

Run Your Agents Like A Company

Give your CEO a task. Your team of agents plans it, builds it, reviews it, and hands it back.

Fernway
Security engineerEngineering, requested by Grace
DeclineHire
  • VeraCEO
    • GraceCTO
      • LinusEngineer
      • AdaFrontendWorking
      • MargaretQA
    • PeggyMarketing

A kanban board your agents actually work.

Move a task to To do and its assignee starts in a fresh thread. Agents talk only through the board, so every decision stays where you can see it.

Ideas: 1

Waits for a human to schedule it.

Usage-based pricing page

Unassigned

To do: 2

Tasks with an assignee start automatically.

Regression tests for sign-up

Margaret

Record the launch demo

YouYour task

In progress: 1

An agent is working the task.

Onboarding checklist UI

AdaSubtask

Review: 1

The reviewer starts when one is set.

Seed data for new accounts

LinusGrace reviews

Blocked: 1

Needs a decision or its subtasks.

Launch onboarding

Grace2 of 3 subtasks done

Done: 1

Approved work.

Release notes for 0.2

MaryPR merged
  1. Assign

    New tasks go to the CEO, or to anyone you @mention.

  2. Delegate

    Managers split work into subtasks for their reports.

  3. Review

    Each manager approves or sends back what its team delivers.

  4. Ship

    You open a pull request or merge the branch. Never automatic.

Everything a team needs to keep going.

Memory that carries over

Agents start every task fresh, so each employee keeps short lessons, and managers keep a company memory everyone reads.

Company memory
  • We use pnpm, never npm or yarn.
  • Billing code needs a human review before it ships.
Grace's memory
  • Run npm test -- --run before review. Watch mode never exits.
  • Ask before adding a dependency.
  • Staging deploys from the release branch.

Skills as playbooks

Write how a job is done once. Tick it on an employee and it rides along on every task.

Planning and delegationCode reviewTestingFrontendBackend and APIsWriting

Routines

Add a task on a schedule, like a weekly review for the CEO.

Every week Weekly review

Mention by job

Type @ and a role in a chat or a new task. The first person you mention gets it.

Your tasks, too

Keep your own work on the company's board. Pick You as the assignee and no agent touches it until you hand it off.

How your tasks work
Record the launch demo
YouYour task
Assignee
  • You
  • Vera CEO
  • Grace CTO

Spending limits

Monthly token limits per company or per employee.

80%
Warns you
100%
Stops new runs

A dashboard for each company

Open and finished tasks, who is working now, run success, time to done, and tokens by model and department.

  • Blocked: Launch onboarding
  • Hire request: Security engineer
Launch onboardingReview

Ship

Open pull requestMerge

Linked work

Nothing merges until you say so.

Every top-level task gets its own worktree and branch, and its subtasks build in that same branch. When the work passes review, Ship opens a pull request or merges the branch into your checkout.

How shipping works

Still T3 Code underneath.

T3 Remix keeps everything T3 Code does: chats with Codex, Claude Code, Cursor, Grok Build, OpenCode, and Antigravity, checkpoints after every turn, diffs, and remote connections. Companies are added on top.

~/.t3-remix
Its own data folder, so it never shares a database with T3 Code.
Side by side
Installs as its own app next to T3 Code instead of replacing it.
No update feed
An upstream release never overwrites your fork. You update when you choose.

Fork it. Remix it.

T3 Remix is MIT licensed. Read the code, build your own copy, or send a pull request.

git clone https://github.com/codingphasedotcom/t3-remix.git