AGENT CONTROL CENTER BETA

Run your organisation
with AI.

For individuals and teams.

Coordinate goals, people and AI agents in one workspace. Keep the work, decisions and results connected—without carrying every handoff yourself.

Free ACC access for accepted beta users. Your AI and hosting costs are separate.

AGENT CONTROL CENTER / HarborIllustrative digital workflow
THE DIRECTION

Launch a booking site

You · direction & decisions
Design Implementation Release
Brief + decisions linked
Manager agentPlan → coordinate → report

Design

Reviewed

Build

Change ready

Review

Your decision
Plan Decisions Repository Evidence
THE RESULT TO REVIEW
harbor Booking preview

Make room for your team.

IndividualTeam booking
Team size4 people
Review booking
Keep the work moving. Keep the important calls.You review the result and choose what happens next.

Start with digital product and service delivery. Bring ongoing work or a new goal.

THE WORK BETWEEN THE WORK

One change. Several places to reconnect.

The request changes in a conversation. The old brief reaches an agent. Review finds the wrong outcome. ACC gives you a shared place to resolve what changes next.

ONE CHANGE · RELATED WORKIllustrative sequence
Client request“Customers need to book as a team, too.”
BRIEF · OLD VERSION

Individual bookings

Requirement needs updating
IMPLEMENTATION TASK

Build a solo booking flow

Build agentWorking from the old scope
HUMAN REVIEW

Which version are we accepting?

Owner · clarification needed

A conversation changed. The brief and task still need to catch up.

ONE CONTINUOUS WORK LOOP

Same goal. Connected work. A result to review.

Follow one booking-site example from its initial plan through a changed requirement and back to review.

People direct and accept the work.
Agents help plan and execute.

Harbor / Booking siteIllustrative workflow
GOAL / INITIAL SCOPE

Launch individual bookings

Owner · defines acceptance

Design

Design lead

Build

Build agent

Review

Owner
Design reviewed → implementation can proceed
Explore features and their limits

INDIVIDUALS AND TEAMS

More hands on the work. More room to think.

The same workspace supports one person or a team. Human responsibility stays clear as agents join the work.

ONE PERSON · SEVERAL AGENT ROLES

Working on your own

One person directs several roles and agents.

You · goal, decisions & review
Manager agentShared plan · connected records
Design supportImplementationReview support

Keep ongoing work moving without rebuilding its context every time.

SHARED WORK · DISTINCT RESPONSIBILITIES

Working as a small team

People share responsibility; agents execute assigned work.

Human responsibilitiesLeadDesignerReviewer
Manager agentShared plan · connected records
Design supportImplementationReview support

Membership and permissions define who can see, change or approve work.

Workspaces and teammates

THE ORGANISATIONAL SYSTEM

Different relationships. One connected workspace.

Scope, readiness and authority mean different things. ACC keeps them related without treating them as the same.

Booking site
DesignBuildRelease

Where work belongs

Hierarchy groups the goal and its parts. Boards show status and the next action.

Board guide
Design reviewed Build ready
Owner · approvalPermitted action

When work can move

Dependencies define prerequisites. Permissions define who may act or approve.

Supervision
Task
Decision
Report + change
Linked, reviewable records

What happened

Decisions, reports and delivery records preserve the trail for review.

Work records
Parallel software changes: merge lanes

A merge lane groups related changes on an integration branch. It is different from a board column or task dependency.

Configuration-dependent: routing and merge-train execution are separate, default-off controls. Required checks, approvals, conflicts and deployment verification still matter.

See prerequisites and limitations

A COORDINATION LAYER

Your tools. Your machines. Connected work.

ACC coordinates the work. Agents execute through supported engines and can use tools installed on a connected computer or VPS through its terminal. The tools shown here are starting points, not the full extent of your setup.

Agent Control Center

Goals · people · agents
Boards · decisions · reports

Available to evaluate in beta

Supported engines & repository connections

Claude Code

Supported for tasks and chat. Provider sign-in required.

Codex

Chat supported. Task execution is opt-in.

Gemini CLI

Task execution when enabled. Gemini chat is currently unavailable.

GitHub & repositories

Local or GitHub repositories. PR delivery needs a push remote.

Your computer or VPSInstalled CLI tools

Work with the setup you already use.

Agents can use command-line tools available on the connected machine—for example, build, test or deployment commands. Tools need to be installed, authenticated and permitted; what can run depends on the engine and environment. The machine must stay online.

BuildTestDeployYour CLI workflow
PLANNED · PHASE 2

More tools connected directly in ACC. Broader direct integrations are planned for phase 2. Using a tool through your terminal today is different from having a dedicated integration in the ACC interface.

Infrastructure, planned connections and limitations

ACC’s own infrastructure: Vercel hosts the application and Supabase supports its backend. These are not a promise of universal user-tool connectivity.

In development: FlowGraph integration. Planned for phase 2: broader direct tool integrations. No delivery date is promised. Availability varies by engine, credentials, permissions and beta configuration.

Check the current product status

BUILT WITH ACC

A clarification becomes part of the work.

ACC is used internally to improve ACC. This historical example connects a requested change to its clarified scope, report and merge record.

INTERNAL WORK RECORDT-5077 · July 2026
REQUEST

Improve board statuses

Board polish + operator-handbook work.

CLARIFICATION

Resolve the scope

Report maps requested paths to changed files.

CHANGE

Review and merge

Linked PR #1013 retains the change and review context.

RECORD

Keep the result linked

Task history records merge reconciliation.

Task T-5077Change #1013Scope reportMerge record

Selected historical internal records, not a productivity or external-adoption benchmark. The separate programme closeout is explained in the evidence guide.

ACCInternal digital-delivery use
FlowGraphSeparate memory tool · integration in progress
Read the internal evidence and its limits

FROM ACC TO GETSET

Coordinate an organisation.
Then connect capabilities.

ACC is the first digital phase of GetSet. The wider vision is to compose services across independent providers and domains, with explicit commitments and acceptance.

Explore the GetSet vision
  1. CURRENT BETA

    Within an organisation

    ACC · people, agents and supported tools

  2. FUTURE VISION

    Between organisations

    Provider commitments and agreed milestones

  3. FUTURE VISION

    Across service domains

    GetSet · composed capabilities and outcomes

BETA ACCESS

What work would you like to move forward?

Bring an ongoing project, a team workflow or a new goal. Apply without an account. We’ll reply by email within 3–4 days.

A few things to know

Is ACC only for building software?

ACC is an organisation-management and coordination workspace. Digital product and service delivery is its first use case. Start with work that fits the supported tools; the wider GetSet service network remains future vision.

Can I bring work that is already underway?

Yes. Bring ongoing work, a local repository or a GitHub repository. Discuss the goal, responsibilities and next reviewable outcome rather than starting again.

What does the free beta include?

Accepted applicants receive free ACC access. You supply your own supported AI subscriptions or API credits and pay any VPS or hosting costs. Future ACC pricing is undecided.

Can my team join?

Yes. Workspace access and the number of people allowed are set per accepted application. Approved founders can invite teammates within that capacity; roles and permissions still apply.

How much technical knowledge do I need?

A little technical knowledge helps with repositories, runners and provider sign-in. Setup support is available. A manager agent can help discuss the plan; you remain responsible for direction and review.

Will agents run everything automatically?

You choose oversight and approvals for configured work. Work can pause for a decision, failed check, missing permission or unavailable machine. ACC does not remove the need to inspect results.

Where is my data stored?

Project files and related document-context records stay with your project. ACC also stores coordination data. Personal exports, organisation-owned work and account deletion have different coverage. Read the data and export guides before deciding what to keep or remove.

Can I use ACC from my phone?

The web workspace can be accessed on a laptop, tablet or phone. Execution still runs on a connected computer or VPS, which must remain online.

Get started and understand setupYour data and project ownership
ApplyReview · 3–4 daysSetup if accepted

Apply for beta access

Tell us about the work. No sign-in needed—we’ll reply by email within 3–4 days.

Free ACC access for accepted applicants. AI and hosting costs are separate; future ACC pricing is undecided.

We’ll acknowledge your request and reply here.

An ongoing project, team workflow or goal. A sentence or two is enough.

Checking this browser before sending.

Your answers go to our support inbox so we can review your application and reply by email. How we use your details

No account needed to apply.