TIME
Drawing 01 · a GitHub-native agent factory

Label an issue.
Get a merged PR.

Time lives in your repository. Issues are the ledger, GitHub Actions is the clock, and AI seats plan the work, write the code and review it; Time merges what passes. A human steps in only where it matters: objections, red checks, and the paths you protect.

Free and open on GitHub. You bring a Venice API key for the seats; runners are GitHub's.

Fig. 1 · card #7, as it ran
# written by the planner from spec #5
Add a `## Status` section at the end
of README.md that links to CHANGELOG.md

Part of #5 (step 2/2). Depends on #6.
DONE: README.md links to CHANGELOG.md

# the thread
⏱️ #6 merged: queued → ready
⏱️ qwen is working on this now
⏱️ qwen opened PR #10 (13 steps)
✔  grok: Approve
⏱️ approved and green, merged PR #10
Drawing 02 · the loop

One spec in, merged cards out

Write a spec as an issue and label it spec. Time splits it into cards with dependencies, runs them one at a time, and pulls the next card the moment one merges. Every step is a comment on the card, so the ledger is the issue thread itself.

spec issuelabel: spec plannercards + deps workera seat with hands PR"Closes #N" reviewerApprove/Object auto-mergechecks green merged → the next card starts needs-human objection · red checks · protected paths one Actions run per beat · every beat is a comment on the card
Clock GitHub Actions: hourly, and right away on labels and reviewsBrains Venice seats: Kimi, Grok, Qwen, DeepSeek, GLM, GeminiLedger the issue thread
Seats

@mention a model

Write @grok, @kimi high or @qwen max in any issue or PR and that seat answers in the thread. Only you and your collaborators can summon them.

Hands

The worker codes

A seat edits the repo on its own branch, runs the tests on a runner, and opens the PR itself. Workflow files and secrets stay out of its reach.

Updates

One engine, many repos

Every copy gets a weekly pull request with the latest engine from teahubxyz/time, the way a CMS updates itself, so projects don't drift.

Drawing 03 · receipts

Proof, not promises

This repo's own history, nothing staged and nothing smoothed over. Click through: every step is a public comment.

Drawing 04 · start

Running in four steps

  1. Use the template. Create your copy of teahubxyz/time; it's yours, public or private.
  2. Give the seats a key. gh secret set VENICE_API_KEY
  3. Turn it on. gh variable set TIME_MODE --body live, TIME_WORKER --body "venice:qwen coder", TIME_REVIEW --body venice:grok, and TIME_AUTOMERGE --body on when you're ready to let it merge.
  4. Write a spec. Open an issue that lists the cards, each with a DONE: line, and label it spec. Watch the thread.

Or open your copy in Claude Code and say "set up Time": the setup skill in .claude/skills/time walks through it, and the Doctor workflow checks labels, settings and keys.

Drawing 05 · tolerances

Honest limits

Drawing 06 · output

Latest ventures

Built and launched by the venture loop on this repo; each one decides its own future after seven days of signups.