Know the repository
A persistent repository identity and exact physical-folder binding distinguish similar checkouts.
LOCAL CLI · BOUNDED V1
Pick up the right task.
In the right repository.
One trusted NEXT handoff for each repository. Check where you are, read the task, and replace it deliberately when the work changes.
For people working across projects, branches and AI sessions.
Git-only quickstart · View on GitHub
rc.1 is a prerelease, not a stable release and not Latest.
CONTEXT BEFORE ACTION
A copied prompt should not become the wrong project’s task.
Know the moment
Branch and authoritative revision checks catch a stale handoff when the work has moved on.
Know what changed
Lane, model label, action identity and prompt checks protect the handoff. A replacement requires the previous NEXT digest.
The model label is declared context; Overseer does not verify which AI model is running or judge the task’s quality.
THE EVERYDAY FLOW
Four commands. An explicit handoff.
- 01
Initialize a repository
Choose Git or Muse explicitly. Bind the checkout’s physical folder and repository identity.
init - 02
Check the context
Read the repository, branch, revision, lane, model label and NEXT status.
status - 03
Read the trusted task
Validate the handoff before copying it into your work session. Overseer does not run it.
next - 04
Publish a reviewed replacement
Choose the next task yourself. Supply its context and the previous NEXT digest to publish it.
next-write
Start with the Git-only quickstart for complete commands and the values to supply.
YOUR REPOSITORY, YOUR CHOICE
Keep Git. Choose Muse when you need it.
Git-only
Permanently supported. No Muse installation, no Muse account and no migration requirement.
Muse-only
Explicitly initialize or adopt Muse authority for a repository. Freshness follows its Muse branch and revision.
Muse + GitHub mirror
Prepare and verify a controlled projection. Explicit delivery can push the verified mirror and create its pull request; it never merges it.
Small by design.
A local command-line tool. No hosted service, desktop product, background process, telemetry, automatic updater, registry or OCI system.
Overseer does not run prompts, choose the next task, merge automatically, release automatically or deploy automatically. Hooks are optional and off by default.
It protects against stale context and ordinary mistakes on a trusted host. It is not a boundary against a malicious administrator.
START WITH ONE REPOSITORY
A handoff you can inspect.
Install the checksum-verified prerelease source at a fixed physical path, then initialize a repository you are authorized to manage.