AFOS Console

The value of AFOS_ASSISTANT_TOKEN in /srv/afos/orchestrator.env. Stored in this browser only.

AFAFOS Agent Factory
connecting…
Dashboard Projects System

Connect your first repository

AFOS verifies the token, the working branch, its protection and the test command. Once every check passes, agents can work on it.

Projects

Connect a repository

AFOS checks the token, the branch, its protection and the test command before any agent is allowed near it.
Before you paste a token. Builder commits, so this token is mounted into the session container and an agent holding it can do anything its scope permits. The scope is the whole safety boundary: Contents: write on this one repository, nothing org-wide, no administration, no merge rights. AFOS confirms the token has write here — it cannot confirm the token is limited to this repository, and will say so rather than imply otherwise.

Project

Verification

Start a job

Intake goes first by default: it turns what you wrote into acceptance criteria, so you can see what the work will be held to before any of it is done.

Advanced

The stub executor never contacts the API. It exists for testing AFOS itself, not for real work.

Work on this project

Settings

Ceiling and description are yours: they are written to Airtable first, so a change made here does not quietly revert on the next sync.

Spending and context

Working branch

The branch agents work from and open pull requests into. A new branch is checked first — that it exists, is not the default branch, is protected, and can be cloned — and the project switches only if every check passes. If one fails, it stays on the current branch.

GitHub credential

Contents: write on this one repository, nothing else. Replacing it re-runs verification immediately.

Dashboard

What AFOS is doing now, what it did today, and what it needs from you.
How AFOS works

You describe a job. AFOS splits it into steps, and each step is done by one role — an agent with one thing to do and nothing else. A step hands its work to the next one, so a job reads as a sequence you can follow.

    Nothing reaches your branch on its own: work arrives as a pull request, and anything judged comes to you for a verdict until AFOS has learned what you accept.

    Today

    System details

    Recent work, across every project

    Projects

    All projects

    Step

    The job, step by step

    Handoffs, by run id

    Brief

    Acceptance criteria

    Result

    What the agent did

    Artifacts

    System

    The orchestrator, the worker, and spend across everything.

    Pause

    Pausing stops new runs being claimed. Runs already in progress finish. The switch is written to Airtable first, so it stays set.