0 Fork 0

T

Claude 35860f4bf8 Worker: a command that never exits is stopped and reported, not a crash

Docscope's fix round ran 'python -m http.server' to test its page; the
600s timeout raised and took the whole round down. The run tool now stops
a command after TIME_RUN_TIMEOUT (default 180s) and tells the model to use
one-shot commands.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UpT7eWzeLhRwuYmsSQnbRb

2026-10-11 16:46:13 -07:00

.claude/skills/time

Docs: Venice-first setup, and the venture loop in the setup skill

2026-10-11 16:14:48 -07:00

.github

Worker: a command that never exits is stopped and reported, not a crash

2026-10-11 16:46:13 -07:00

.gitignore

Hands-off Time: spec planner, auto-merge on Approve + green checks, next card, update workflow

2026-10-11 11:46:43 -07:00

CHANGELOG.md

Venture loop: launch products, not pages

2026-10-11 15:48:21 -07:00

README.md

Docs: Venice-first setup, and the venture loop in the setup skill

2026-10-11 16:14:48 -07:00

README.md

time

A GitHub-native agent factory. GitHub is the ledger, GitHub-hosted runners are the clock (Time), the worker is a Venice seat with hands or a Cursor cloud agent, and chat is where you plan.

Cards: an issue with a DONE: line, labelled ready.
Heartbeat (heartbeat.yml, hourly and whenever a card is labelled ready): moves cards forward. In dry-run (default) it only says what it would do; with TIME_MODE=live it dispatches each card to the worker (TIME_WORKER: a Venice seat such as venice:kimi, which edits the repo and opens the PR itself, or a Cursor cloud agent), which opens a PR that closes the card. An optional reviewer (TIME_REVIEW) checks the PR. At most TIME_DAILY_CAP launches a day.
Mentions (mention.yml): @kimi, @grok 4.7, @qwen max high in any issue, PR or comment gets that seat's reply (Venice).
Hands-off (TIME_AUTOMERGE=on): label an issue spec and Time splits it into cards that run one at a time. A card's PR merges itself once the reviewer approves and checks are green, then the next card starts. Objections, red checks and protected paths (workflows, deploy, secrets) go to a human.
Venture loop (venture.yml, every 20 min once TIME_VENTURE=on): one venture card a day. It scouts the repos that gained the most stars this week; seats pitch; the board votes (Borda, quorum of two); every board seat writes a launch plan (positioning, first users, pricing, channels, 7-day success and kill lines) and one seat synthesizes them into LAUNCH.md; the worker builds a launch page around a working product on gh-pages in its own design direction; deterministic checks and headless Chrome (phone and desktop) gate it, with two fix rounds before an andon; GitHub Pages ships it at /ventures/<slug>/. Signups go through an issue form (.github/ISSUE_TEMPLATE/early-access.yml), each one thanked on its issue; after 7 days the count of distinct people decides: build v2, kill, or watch a week more. The studio index lives at /ventures/. Launch posts are drafts for a human; nothing is posted outside the repo.
Doctor (doctor.yml, manual): runs the tests and checks label, settings and keys.
Update (update.yml, weekly or manual): opens a PR with the latest engine from teahubxyz/time, so every project stays on one Time instead of drifting copies.

Setup

Open this repo in Claude Code or Cursor and say "set up Time": the agent follows .claude/skills/time/SKILL.md. The quickest path needs one secret, VENICE_API_KEY: Venice seats plan, build and review (TIME_WORKER=venice:qwen coder, TIME_REVIEW=venice:grok). A Cursor cloud agent can be the worker instead if you have a Cursor API key. The landing page walks through it: https://teahubxyz.github.io/time/

Status

For changes and release history, see CHANGELOG.md.