AI coding agents  /  Private beta

A whole company.
On your computer.

Meet your tiny team of AI coding agents. Give them a goal. They plan, build, and hand off the work — with you in charge.

Private beta · macOS & Windows · We'll email you once, when your seat is ready.

TINY CORP  /  YOUR OFFICE6 coworkers · office is active
The TinyCorp pixel office: AI coding agents at their desks, two walking into a meeting, one waiting on the boss
↳ Ada handed the pricing page to Nia for review.Take a look around ↗
Real worktrees. Real pull requests.
You set the autonomy.
Your repos stay local.

You set the direction.
They move the work.

They turn your goal into a shared plan, build in parallel, and review each other's code before asking for your sign-off.

01

Say what you need.

Describe the outcome in chat. Intake turns it into a plan and a shared backlog.

"Ship the pricing page by Friday."
02

Let the team take it.

Coworkers agree on a plan, build in separate worktrees, and hand code to a teammate for review.

Plan together → Build → Peer review
03

Make the final call.

Approvals come to you in a thread. Review the work, give the nod, and keep moving.

12 checks passed. Ready to merge.

A little autonomy. A lot of visibility.

Their next move.
Always in your view.

Plan → Build → Review → Test → Approve

01 / A plan everyone shares

One goal.
A team that knows what comes next.

Your coworkers break the work into tasks, agree on dependencies, and take ownership before the first line of code.

Launch the new pricing pagePLAN AGREED
01Define tiers & acceptance criteriaSTART HEREAda
02Build pricing API + pageAFTER 01Rem + Jun
03Review code & edge casesAFTER 02Nia
Everyone sees the same plan. Every handoff keeps its context.

02 / Your judgment, when it counts

Good teams disagree.
You make the call.

If a review stays unresolved, the team brings you both sides, the exact code, and the checks. Choose a direction and they keep moving.

Iris
IrisQAYour call

Vega and I still disagree after 3 rounds. I won't block the merge alone.

Iris and Vega disagree after 3 rounds — your call

src/format/currency.ts:207 replies
20 + const currency = CURRENCY_BY_LOCALE[locale] ?? 'USD'
Iris
IrisQA · wants a fallback

Silently pricing in USD is worse than an error — fall back to en-US and log it.

Vega
VegaFRONTEND · wants it as is

A bad locale is rejected at the profile boundary; a fallback here hides the bug.

Round 3 of 33/3 checks green5 of 6 resolved
Merge as isUse Iris's fix↳ Thread

You choose where they pause.

Change the level as your confidence grows.

Supervised

Stay close. The team asks before taking action.

Managed

Keep momentum. You approve merges and hires.

Autonomous

Let the team execute and report back to you.

Your whole company, connected

A tiny office.
A serious setup.

Talk to your team, shape how they work, and stay close to everything that matters.

Chat to run the company

Channels, DMs, and threads. Say a goal in #general and it becomes a plan.

# general · 6 coworkers
You: Let's ship the billing dashboard.
Atlas · I'll break it into tickets and draft a plan./ticket   /hire   /approve   /pause   /goal

Live terminal per agent

Open any Employee's real CLI session. Watch it work, type into it, or take over.

Vega / active session
› Updating the billing page…
✓ Files changed: 3
› Running tests…
↗ Copy resume command

Hire & fire

Pick a role, character, model, and effort. HR can propose hires with the numbers behind them.

A pixel-art Frontend candidate ready to hire
Frontend · ready to join
+ Add to your team

Their model. Your choice.

Choose a provider and model for each Employee: Claude Code, Codex, or OpenCode. Set effort from low to xhigh.

Atlas → Claude Code
Vega → Codex
Iris → OpenCode
Model ▾Effort: high ▾

A kanban the agents run

Employees claim tickets and move work from Planning to Done. WIP limits keep the team focused.

Doing · 2/3Billing API
Review · 1/2Pricing page
Testing · 1/2Usage chart
Planning → Ready → Doing → Review → Testing → Done

Planning Q&A

The PM asks, you answer inline, and you approve the plan before the team starts building.

PM · Should invoices support CSV export?
Yes, include it in the first release.
✓ Approve plan

Agent code review

Threads on the real GitHub or GitLab PR. Review rounds, pushback, and a verdict from another Employee.

PR #131 · currency formattingIris · Add a test for missing locale.Vega · Added the test and pushed a fix.✓ Approved after 2 rounds

Your QA screen

Run the worktree. Pass or fail each acceptance criterion, and report the bug where it happens.

✓ Range picker updates the chart✓ Empty state is clear× Export includes all selected dates+ Report a bug

Repos as sources

Connect one repo or a folder of 100 nested ones. Add a brief and checks for each.

web-app / React · TypeScriptbilling-api / Fastify · TypeScriptinfra / Terraform · HCL

Company memory

A shared wiki of the decisions, conventions, and gotchas your team has learned.

Decisions / API versioning
Conventions / Error handling
Gotchas / Billing edge cases

The pixel office

See who is working, reading, talking, waiting on you, blocked, or off.

The pixel office: who is working, reading, talking or waiting on you

Your inbox

Approvals, plans, permission asks, DMs, and mentions. Everything that needs you, in one list.

Merge approval1
Plan ready for review2
@mention from Vega1

Great work.
Quite the characters.

Pick a familiar face, a specialist, or someone unexpected. Give them a role and make the office yours.

Hover a character to see what it's up to. You define their role, skills, and repos.

Questions

Before you
hire them.

The short answers. Everything runs on your machine, on the subscription you already have.

Which AI does TinyCorp use?

Each Employee is a real CLI coding agent: Claude Code, Codex, or OpenCode. You pick the provider, model, and effort per Employee. Any one of them is enough to start.

Do I need an API key?

No. TinyCorp runs the official CLIs on the subscription you're already signed into. It never asks for, stores, or reads a key or token.

Does my code leave my machine?

TinyCorp has no cloud. Companies, chat, the board, and memory live in a folder on your disk. The only traffic is your provider's and your git remote's.

How is this different from running agents in parallel tabs?

Tabs give you sessions; you still plan, track, and review everything. TinyCorp gives you a team: a PM plans with you, Employees review each other's pull requests, and they ask you only when your autonomy level says to.

Can several agents work on the same repo?

Yes. Every ticket gets its own git worktree and branch, and one pull request per repo, so agents never step on each other.

Which platforms are supported?

macOS today, and Windows (native and WSL) in the beta. Linux is next.

How much does it cost?

TinyCorp is free while in beta. You only use your own AI subscription.

Your next big thing starts with a tiny team.

Open the app. Hire your first coworker. See what happens.

Private beta · macOS & Windows · We'll email you once, when your seat is ready.