Working on your own
One person directs several roles and agents.
Keep ongoing work moving without rebuilding its context every time.
AGENT CONTROL CENTER BETA
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.
Start with digital product and service delivery. Bring ongoing work or a new goal.
THE WORK BETWEEN THE WORK
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.
A conversation changed. The brief and task still need to catch up.
The person clarifies the scope. Related records and work are then revised; this illustration does not imply automatic propagation.
ONE CONTINUOUS WORK LOOP
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.
INDIVIDUALS AND TEAMS
The same workspace supports one person or a team. Human responsibility stays clear as agents join the work.
One person directs several roles and agents.
Keep ongoing work moving without rebuilding its context every time.
People share responsibility; agents execute assigned work.
Membership and permissions define who can see, change or approve work.
THE ORGANISATIONAL SYSTEM
Scope, readiness and authority mean different things. ACC keeps them related without treating them as the same.
Hierarchy groups the goal and its parts. Boards show status and the next action.
Board guideDependencies define prerequisites. Permissions define who may act or approve.
SupervisionDecisions, reports and delivery records preserve the trail for review.
Work recordsA 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 limitationsA COORDINATION LAYER
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.
Goals · people · agents
Boards · decisions · reports
Supported engines & repository connections
Supported for tasks and chat. Provider sign-in required.
Chat supported. Task execution is opt-in.
Task execution when enabled. Gemini chat is currently unavailable.
Local or GitHub repositories. PR delivery needs a push remote.
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.
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.
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.
BUILT WITH ACC
ACC is used internally to improve ACC. This historical example connects a requested change to its clarified scope, report and merge record.
Board polish + operator-handbook work.
Report maps requested paths to changed files.
Linked PR #1013 retains the change and review context.
Task history records merge reconciliation.
Selected historical internal records, not a productivity or external-adoption benchmark. The separate programme closeout is explained in the evidence guide.
FROM ACC TO GETSET
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 visionACC · people, agents and supported tools
Provider commitments and agreed milestones
GetSet · composed capabilities and outcomes
BETA ACCESS
Bring an ongoing project, a team workflow or a new goal. Apply without an account. We’ll reply by email within 3–4 days.
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.
Yes. Bring ongoing work, a local repository or a GitHub repository. Discuss the goal, responsibilities and next reviewable outcome rather than starting again.
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.
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.
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.
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.
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.
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.
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.
Your answers are still in the form. Please try again. If this continues, contact support@getset.live.