The delivery system where humans and AI agents plan, execute, review, and ship in the same workspace.
Oversight is for teams that are tired of splitting intent across docs, execution across tickets, discussion across chat, and automation across ad hoc agent scripts.
It gives you one operating model where:
- documents hold plans, requirements, SOPs, runbooks, ADRs, and test intent
- issues hold execution state, ownership, and delivery progress
- issue-bound threads hold human-agent discussion and run context
- workflows and approvals decide when automation is allowed to move work forward
Best for:
- software teams doing AI-assisted delivery, review, and ops work
- teams that start from requirements, plans, SOPs, or ADRs instead of blank tickets
- organizations that want automation without losing approval gates, auditability, or traceability
Not ideal for:
- a lightweight personal todo app
- teams that only want a chatbot attached to an issue tracker
- projects with no need for document-to-issue traceability or workflow-driven automation
| If your work is split across... | Oversight brings it back together by... |
|---|---|
| planning docs | turning source documents into linked execution issues |
| issue trackers | keeping state, assignees, dependencies, and subissues in one delivery graph |
| chat tools | binding human/agent conversations to the issue instead of letting them float away |
| agent wrappers and scripts | putting automation behind workflow rules, approval gates, and durable history |
- Write or collect the document that should drive the work.
- Create the linked execution issue.
- Decompose, assign, and discuss the work with humans and agents on the issue.
- Let workflow rules dispatch agents where appropriate.
- Keep approvals, outputs, and traceability attached to the same record of work.
That makes Oversight especially good for flows like:
- requirement → implementation → review → verification
- bug report → evidence → fix → approval-gated validation
- SOP / rollout plan → deployment issue → release evidence
- ADR / engineering standard → linked implementation issues and long-term traceability
git clone https://github.com/aspect-build/oversight.git
cd oversight
make setup
cargo build --workspace --release
pnpm --dir web build
export OVERSIGHT_MASTER_KEY=$(./target/release/oversight-server genkey)
./target/release/oversight-serverThen open http://127.0.0.1:7878.
Next step: read Tutorial: Getting Started for the guided setup flow.
- Backend: Rust workspace with Axum-based server, worker runtime, shared models, and multiple storage backends
- Frontend: React + TypeScript + Vite + Playwright
- Execution modes: local CLI, embedded worker, remote/distributed workers, ACP stdio embedding
- Storage: SQLite by default, with PostgreSQL and filesystem backends under active development
- Docs: Astro Starlight docs site with tutorials, how-to guides, operations docs, and ADRs
Common commands:
make help
make check
make test
make web-test
make docs-buildoversight/
├── crates/ # Rust workspace crates
├── web/ # React frontend + Playwright tests
├── docs/ # Tutorials, reference docs, architecture notes, internal archive
│ ├── tutorials/
│ ├── concepts/
│ ├── how-to/
│ ├── operations/
│ ├── reference/
│ ├── use-cases/
│ ├── architecture/
│ └── internal/
├── migrations/ # SQL migrations
└── scripts/ # Developer utilities
Oversight is under active development. Expect rough edges and occasional breaking changes while core workflows are still being built out.
This project is licensed under the MIT License.