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."AI coding agents / Private beta
Meet your tiny team of AI coding agents. Give them a goal. They plan, build, and hand off the work — with you in charge.
They turn your goal into a shared plan, build in parallel, and review each other's code before asking for your sign-off.
Describe the outcome in chat. Intake turns it into a plan and a shared backlog.
"Ship the pricing page by Friday."Coworkers agree on a plan, build in separate worktrees, and hand code to a teammate for review.
Plan together → Build → Peer reviewApprovals 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.
01 / A plan everyone shares
Your coworkers break the work into tasks, agree on dependencies, and take ownership before the first line of code.
02 / Your judgment, when it counts
If a review stays unresolved, the team brings you both sides, the exact code, and the checks. Choose a direction and they keep moving.
Vega and I still disagree after 3 rounds. I won't block the merge alone.
Silently pricing in USD is worse than an error — fall back to en-US and log it.
A bad locale is rejected at the profile boundary; a fallback here hides the bug.
Change the level as your confidence grows.
Stay close. The team asks before taking action.
Keep momentum. You approve merges and hires.
Let the team execute and report back to you.
Your whole company, connected
Talk to your team, shape how they work, and stay close to everything that matters.
Channels, DMs, and threads. Say a goal in #general and it becomes a plan.
# general · 6 coworkersOpen any Employee's real CLI session. Watch it work, type into it, or take over.
Pick a role, character, model, and effort. HR can propose hires with the numbers behind them.
Choose a provider and model for each Employee: Claude Code, Codex, or OpenCode. Set effort from low to xhigh.
Employees claim tickets and move work from Planning to Done. WIP limits keep the team focused.
The PM asks, you answer inline, and you approve the plan before the team starts building.
PM · Should invoices support CSV export?Threads on the real GitHub or GitLab PR. Review rounds, pushback, and a verdict from another Employee.
Run the worktree. Pass or fail each acceptance criterion, and report the bug where it happens.
Connect one repo or a folder of 100 nested ones. Add a brief and checks for each.
A shared wiki of the decisions, conventions, and gotchas your team has learned.
See who is working, reading, talking, waiting on you, blocked, or off.
Approvals, plans, permission asks, DMs, and mentions. Everything that needs you, in one list.
Pick a familiar face, a specialist, or someone unexpected. Give them a role and make the office yours.
Questions
The short answers. Everything runs on your machine, on the subscription you already have.
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.
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.
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.
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.
Yes. Every ticket gets its own git worktree and branch, and one pull request per repo, so agents never step on each other.
macOS today, and Windows (native and WSL) in the beta. Linux is next.
TinyCorp is free while in beta. You only use your own AI subscription.
Open the app. Hire your first coworker. See what happens.