Skip to content
steading
/
skift
Projects
Plan and deliver
console
A web console for everything your agents do
skift
A task graph agents and people share
mill
A runner that delivers tasks as merged changes
knowledge
In design
A memory agents can ask, with sources
Fence it in
croft
In design
Sandboxes and virtual machines for agent work
gateway
In design
A proxy that holds credentials so agents don't
Keep it maintained
almanac
Early
Automatic repair for broken dependency updates
fallow
In design
Disk cleanup for what agents leave behind
Ways in
thicket
Early
Agents you reach from Slack or a phone call
stead
Early
One command that runs Steading on a Mac
Every project, by the problem it fixes
Docs
GitHub
Overview
Vision
Core Principles
Domain Model
Architecture
Roadmap
CI
Decisions
Store the DAG in plain PostgreSQL tables, not a graph database
Connect-RPC is the only door, with identity resolved by transport
Artifacts are content-addressed: managed blobs plus external references
Authorization by embedded OPA and Rego policy
Align with A2A: a skift node maps to many A2A tasks, one per lease
Provenance is not client-assertable, and the store never confers authority
Core tech stack: Go, buf, sqlc, goose, pgx, Ginkgo
Short enum names are the JSON wire form, through one derived codec
The default gate policy is a notification channel, not a safety boundary
Parking work is a hold on the graph, not a status and not orchestrator configuration
Plans
Claims and reads select nodes by one filter, across every project
The built skift is published to GHCR on every push to main
Sprint: prove the bet
Research
METR and Redwood investigation of the OpenAI / Hugging Face incident
Retrospectives
Retrospective: the first build
Research
METR and Redwood investigation of the OpenAI / Hugging Face incident