01 / START WHERE YOU ARE
An idea. Or your next chapter.
Start fresh, connect a local or GitHub repository, or bring one as reference.
AGENT CONTROL CENTER BETA
Build your product with
an AI team you direct.
Bring an idea or an existing project. Coordinate planning, design and development—with your project’s files and decisions keeping the work connected.
Free ACC access for accepted beta users. Future pricing is undecided.
YOUR PROJECT, MOVING FORWARDIllustrative workflow
Add a guided onboarding flow.
ManagerPlan → coordinate → review Context linked
Design Ready
Build Ready
Review Your turn
Plan Decisions
Repository
Repository harbor01 / 03
Make yourself
at home.
A simpler start for your customers.
A plan becomes something you can review.You choose what happens next.
KEEP THE BIGGER PICTURE
New conversation.
Same project.
A new agent shouldn’t mean another round of explaining everything.
ACC connects work to your project files and recorded decisions, helping the next task pick up the relevant background.
See how context carries forward PROJECT RECORD Connected
A decision worth keepingKeep onboarding
to three steps.
to three steps.
Brief Files
FilesThe conversation changes. The decision stays connected.
YOUR DIRECTION. COORDINATED WORK.
More hands on the work.
More room to think.
Plan it with a manager agent. Let your agents handle the tasks. Review the results and decide what comes next.
YouDirection & decisions
Manager agentKeeps the work connected
Design
Build
Review
Bring human teammates into the project, too.
02 / SHAPE THE PLAN
Think it through together.
Discuss the work with a manager agent and review the plan before implementation.
03 / CHOOSE YOUR OVERSIGHT
Stay involved on your terms.
Choose what can run automatically. Review results, answer decisions and request changes.
BUILT WITH ACC
Our first proof?
ACC itself.
We built ACC to get back to building GetSet. Today, we use it to plan, coordinate, review and improve ACC itself.
The work includes corrections and human decisions. Each improvement makes the system we rely on more useful.
Read the building storyAgent Control CenterBuilt with ACC. Improved with ACC.
Plan
Build
Review
Improve
FROM THE DEVELOPMENT RECORD
Make decisions easier to act on.
Review holds were connected to a visible decision queue, with corrections to how approval releases work.
ROOM TO BUILD YOUR WAY
Your ambition.
Your way of working.
Choose the team and the level of oversight that fit your project. Stay involved where your judgement matters.
Design
Gemini
GeminiBuild
Claude Code
Claude CodeReview
Codex
CodexOne project. Connected records.
Choose the team for the task.
Give agents different roles and AI tools. Bring in human collaborators when you need another perspective.
Explore tools and setupYour decision
Ready for a closer look.
Review resultRequest changes
Decision alerts, including configured Slack notifications.
Keep the important calls.
Let configured work proceed, ask for reports and step in to change direction. You decide what needs your approval.
See how supervision worksYour computer
orYour VPS
Connected to ACC
Your browserDesktop, tablet or mobile
The execution machine must stay online.
KEEP YOUR WORK WITHIN REACH
Step away from the desk.
Stay close to the decisions.
Open ACC in your web browser—on a laptop, tablet or phone. Run supported work on your computer or a connected VPS, then check progress and respond from another device.
A laptop that sleeps can’t keep running tasks. Use an available dedicated machine when you want work to continue.
Check what you needA PROJECT YOU CAN KEEP
Your project stays yours.
Your project files and the document-context records that accompany them stay with you, so you can continue working outside ACC.
Some coordination data is stored by ACC. Personal exports, organization-owned work and account deletion have different coverage. Read the data guide before choosing what to keep or remove.
Understand what is stored whereProject files
Document-context records
Local or GitHub repository
ACC also holds coordination data.
INTEGRATION IN PROGRESS
Meet FlowGraph.
A separate GetSet tool for exploring and editing project memory as a connected graph.
Help shape what comes next.
Need a capability? Request it. Your feedback helps us understand what would make ACC more useful for your work.
Beta access
What would you like
to move forward?
Bring the idea you keep coming back to, or the product you’re already building. Apply for the free ACC beta. Setup support is available.
Thanks — your application has been sent.
Check your inbox for a confirmation email. We’ll review your request and get back to you within 3–4 days.
Applying does not create an account or grant beta access.
We couldn't send your application.
Your answers are still in the form. Please try again. If this continues, contact support@getset.live.
A few things to know
Is this for me if I’m building alone?
Yes. ACC is designed for solo founders and small teams. Start on your own and invite human collaborators as your project develops.
How much technical knowledge do I need?
Technical familiarity helps with setup and reviewing work. You can discuss the plan with a manager agent, and beta setup support is available. Onboarding is still being improved.
Can I bring an existing product?
Yes. Connect a local or GitHub repository to build on it, or use one as reference. Explain which parts can change and which decisions must stay in place.
What does the free beta include?
ACC access is free for accepted applicants. You supply your own supported AI subscriptions or API credits and pay for any VPS or other hosting you use. Future ACC pricing is undecided.
Will I still need to review the work?
Yes. Agents can make mistakes. ACC helps coordinate records, tasks and decisions; your judgement and review remain part of the process.
Back to overview
The tour
One project, five stages.
Harbor is an example product — a B2B onboarding tool. Its founder, Priya, wants a customer-onboarding flow: invites by email, a three-step setup wizard and a checklist. Here is how that request moves through ACC. Scenes are simplified representations of ACC, with illustrative project data. This example uses GitHub; you can also start with a local repository.
STAGE 01
Describe your idea
A normal chat message in the Workspace — no template, no ticket.
- You do
- Tell ACC what you want to build: “Invite teammates by email, a three-step setup wizard, a checklist on the dashboard. Ship it behind a feature flag.”
- ACC does
- Brings the project record and earlier decisions to the conversation — here, DEC-014 (new features ship behind the flag() helper) — so the manager agent plans with relevant context instead of asking you to explain the product again.
- You get
- A conversation that starts from what Harbor already is, and a plan proposal to review.
HarborWorkspace
Illustrative
WorkspaceManager-agent chat · context items
Priya09:14
Build a customer-onboarding flow: invite teammates by email, a three-step setup wizard, and an onboarding checklist on the dashboard. Ship it behind a feature flag.
Manager agent09:15
I'll draft a plan. Using the project record and DEC-014 (new features ship behind the flag() helper). Expect five tasks in three waves — you can revise before anything runs.
context usedproject recordDEC-014 · flags2 operational notes
What's happening. Because the project record and earlier decisions live in ACC, the agent can respond with relevant context. The chips show exactly what it was given.
STAGE 02
Shape the plan
Tasks, responsibilities and the order of work — readable before anything runs.
- You do
- Read the plan and ask for changes in conversation — here, “split the wizard into design and build.” Approve when it's right.
- ACC does
- Checks that each task has an owner and a place in the order of work, keeps each revision, and holds the work until you approve. Approving places the tasks on the Work board.
- You get
- Five tasks in three waves. T1 and T2 can start together; T3 waits for both; T5 tests the result.
HarborWork
Illustrative
Onboarding flowPrograms · revision 2 · 5 tasks · 3 waves
BoardTableProgramsHierarchy
Wave 1runs together
T1P2
Invite tokens + schema
Dev agent
T2P2
Wizard screens
Design agent
Wave 2after wave 1
T3P1
Wizard build
Dev agent← T1 · T2
T4P2
Invite emails
Dev agent← T1
Wave 3after wave 2
T5P2
End-to-end tests
Test agent← T3 · T4
r2 — split the wizard into design and build; email templates moved to wave 2.
ReviseApprove plan
What's happening. Waves are the order of work: tasks in the same wave can run together; a wave starts when the one before it has landed. Change your mind later and an approved plan can be pulled back.
STAGE 03
Put agents to work
Specialists take their tasks. Independent work runs together; dependent work waits.
- You do
- Nothing yet. Your runner is signed in — on your laptop, a Mac mini or a VPS — and picks up tasks from the board.
- ACC does
- Starts T1 and T2 at the same time on different machines. T3 and T4 wait until the schema in T1 has landed. Each task works on its own branch; each step goes to the activity record, within the cycle's budget.
- You get
- Parallel progress without agents stepping on each other, and a board that shows what's running, what's waiting, and why.
HarborWork
Illustrative
WorkBoard · 5 tasks · 2 running · 2 waiting
BoardTableProgramsHierarchy
Queued2
T3P1
Wizard build
waits on T1 · T2
T4P2
Invite emails
waits on T1
Running2
T1running
Invite tokens + schema
Dev agentvps-01
T2running
Wizard screens
Design agentmacbook
Needs review0
Nothing to review yet
Done0
—
09:32 T1 claimed · branch acc/T1-invite-tokens09:33 T2 claimed · three wizard variants postedbudget within cycle cap
What's happening. Two agents work at once on tasks that don't depend on each other, each on its own runner. The “waits on” chips say exactly what T3 and T4 are waiting for.
Design agent finishes T2Wizard screens · the chosen variant is attached to T3
Dev agent picks up T3Wizard build · claimed · with T2's result on the record
The design is ready, so the developer can pick up the next task — without anyone pasting anything between tools.
STAGE 04
Review the results
What needs you lands in one Inbox: approvals, questions and review asks.
- You do
- Approve the T3 merge from the review summary and answer T4's question — invite links: 7 days or 30?
- ACC does
- The review agent reads the pull request and summarises what it found. Where a task hits an ambiguity, the agent stops and asks instead of guessing; your answer resumes the same task. Merges and other elevated actions wait for you by default.
- You get
- Decisions made in one place, each with the record of what happened and why. Your answer becomes DEC-021.
HarborInbox
Approvals · 1Illustrative
Inbox3 items need you
Approve merge · T3 Wizard build
Review agent: checks green · wizard state survives refresh · flag gate respected
T4 asks: invite links — 7 days or 30?
needs clarification · task paused until you answer
Preview ready · harbor-preview
Delivery · T2 Wizard screens · opens the example product
T3 · P1
Wizard build
needs reviewWizard build
createdclaimedcommitreviewmerged
- agent
- Dev agent · vps-01
- PR
- #118 · 2 checks passed
- depends
- T1 ✓ · T2 ✓
Reviewer note: invite expiry is hard-coded to 7 days — confirm the intended policy.
PauseSteerReassign
What's happening. Reviews come back as summaries you can act on. The drawer shows where T3 is in its lifecycle and what it depended on. Pause, steer or reassign a running task without losing its work.
STAGE 05
Build on what you learned
Two weeks later, a new task touches invites. The record is already there.
- You do
- Ask for the next thing — “add invite reminder emails” — without re-explaining the invite policy.
- ACC does
- Keeps the outcome, the decision and the agents' operational notes with the project. For the new task it offers the relevant ones — DEC-021 and the note about lib/mail — as context, not instruction, within a fixed budget. Near-duplicates are dropped.
- You get
- A reply that already respects the 7-day expiry. The next request starts from the record rather than a blank chat.
HarborWorkspaceSession · T7
Illustrativerunning
T7 · Invite reminder emailstwo weeks later · Dev agent
Knowledge · DEC-021 · Priya14 days ago
Invite links expire after 7 days; admins can extend to 30.
context for this task2 of 5 slots · within budget
DEC-021 · invite links expire after 7 daysmatches: invite · expiry
note · transactional email goes through lib/mailpinned
Dev agentnow
Scheduling the reminder for day 5 — two days before the 7-day expiry in DEC-021 — and sending it through lib/mail so the unsubscribe footer is added.
Offered as context, not instructions. The agent still decides how to do the work.
What's happening. Relevant items are selected for the task at hand, ranked, de-duplicated and kept within a fixed budget. This is project memory — not training of the underlying AI models.
That's one project. Yours is next.
Apply for the beta, or check what you need to get set up.
Back to overviewBuilt to get back
THE GETSET BUILDING STORY
Built to get back
to building.
ACC began as an internal tool to help a founder keep an ambitious product moving. It became a product of its own.
The work behind the work
GetSet started with a vision for a service coordination platform. Across teams, tools and iterations, too much of the founder’s time went into explaining decisions, reconnecting context and coordinating implementation.
AI agents brought new possibilities, and new friction: scattered conversations, repeated mistakes, connection failures and work spread across machines. ACC grew out of the effort to make that work easier to direct.
Built with the system it improves
Today, the founder uses ACC to plan and coordinate ACC’s own development, with agents implementing work and people reviewing decisions and corrections. The same approach supported FlowGraph, built by an intern under the founder’s close supervision.
The founder now uses ACC to continue building GetSet, including automated work on a VPS that returns decisions for human input.
WHAT THE RECORD SHOWS
Progress includes
review and correction.
Selected merged changes from ACC’s September 2026 development history.
Check before opening a PR.
A pre-PR conformance gate added checks for mechanical issues before work reached the pull-request stage.
Refine the merge workflow.
Request-budget and merge-workflow changes went through revisions around scope, review constraints and tests.
Bring holds into view.
Review holds were connected to a visible decision queue, with corrections to how approval releases work.
Based on a review of the private repository on 7 September 2026. These examples show recorded implementation and rework, not guaranteed outcomes or fully autonomous development.
Explore how ACC works