Claude
ea9198a526
The daily sweep now compares every open card with the cards closed in the last 30 days and lists the ones another card looks to have finished, with the number of the card that did the work, under the stale list on the Astra log. Three signals, in order of how much they say and first-hit wins: the closed card's title repeats the open one's (the planner's own repeat rule), the closed card ports or follows the open card itself (`Port of #48`, `Follows #48`), or both carry the same card over. It closes nothing and labels nothing — the report is for Astra and the CEO, so the rule can stay a checkable hint instead of a verdict, and a card whose work landed under another number stops being silently ranked and queued again. The venture loop's own issues are out of both lists: they are not cards, and two signups for one venture carry the same title by design, which would have put every repeat signup on the report. A card whose `closed_at` is older than the window is dropped too, since Gitea's `since` filters on the last update. `repeat_of` moved from astra.py to router.py, which astra and housekeeping both already load, so the sweep and the planner share one copy of the rule rather than drifting apart. `refs` and `superseded` sit beside it, pure and testable. The card asked for the test in test_time.py with a World holding one superseded and one live card. The matching rule is there (check 198, two open cards: #48, whose work #139 did, and #60, which is live), and the report the sweep writes from it is checked in test_housekeeping.py, where the sweep's own fake forge lives — test_time.py's World drives the heartbeat and cannot run the sweep. No workflow change is needed: housekeeping.yml already runs the whole sweep. Closes #198 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0116Joj4QVA1Gg2WrUmbbfRT
time
A Gitea-native agent factory, running on Teahub prod (teahub.xyz). The Gitea repo is the ledger, Gitea Actions are the clock (Time), the worker is a Claude or Venice seat with hands or a Cursor cloud agent, and chat is where you plan.
- Cards: an issue with a
DONE:line, labelledready. - Heartbeat (
heartbeat.yml, hourly and whenever a card is labelledready): moves cards forward. Indry-run(default) it only says what it would do; withTIME_MODE=liveit dispatches each card to the worker (TIME_WORKER: a seat such asclaude:sonnetorvenice: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 mostTIME_DAILY_CAPlaunches a day. Spend governor: every model call is booked totime/ledger/<YYYY-MM>.jsonl(tokens and dollars); once today's spend reachesTIME_DAILY_USD(default 5) or the month's reachesTIME_MONTHLY_USD(default 100), Time stops calling models, opens anandonissue, and a monthly breach also setsTIME_MODE=dry-run. No model decides whether to spend. - Mentions (
mention.yml):@sonnet,@opus,@kimi,@grok 4.7,@qwen max highin any issue, PR or comment gets that seat's reply. - Hands-off (
TIME_AUTOMERGE=on): label an issuespecand 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 onceTIME_VENTURE=on): one venture card a day, or one right away from Actions → venture → Run workflow → "Start a new venture now". 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 intoLAUNCH.md; the worker builds the product as the page ongh-pages(the tool fills the first screen under a slim header with the one signup button; pricing, limits and the why sit below); 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. - Batches (
TIME_VENTURE_BATCH=3, or Run workflow → "batch"): one scout pass, a field of pitches, and the board's top k become venture cards in one milestone, built side by side and launched together. A held child gets one batch retry before it's counted dead; a retro compares the cohort once every child is measured. - Seed (
seed.yml, manual): land a venture that was built somewhere else. Give it a slug, the URL of a .tgz whose top folder is that slug (or of its parts, in order) and the .tgz's sha256, plus a name and a one-liner for a new venture.seed.pychecks the bundle, copies it toventures/<slug>/ongh-pagesin one commit, adds or refreshes its line inventures/ventures.json, and asks Teahub pages to pull, so it is live at<slug>.yolopreneur.lolwithin the minute. Nothing in the bundle runs. - Refresh (
refresh.yml, manual): for a venture that lives on gh-pages and makes some of its own files (fonts, art, screenshots, generated code). It runsventures/<slug>/tools/build.shon the runner, in place and without credentials, then commits what changed to gh-pages in one commit and asks Teahub pages to pull.fromtakes the folder from another branch first, so a reworked venture lands whole. - Backends (optional,
CLOUDFLARE_API_TOKEN+CLOUDFLARE_ACCOUNT_ID): each venture also gets its own Cloudflare Worker, D1 database and Workers AI, serving its Pages folder at<slug>.<TIME_VENTURE_DOMAIN>. The page talks to it throughtime.js(share links that save a creation, a rate-limited small model, and accounts with passkeys: no passwords, no email); every call degrades gracefully, so products still work on Pages alone. Code:.github/time/cloudflare.pyandcloudflare/worker.js. - Doctor (
doctor.yml, manual): runs the tests and checks label, settings, keys and today's spend. - 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
Started on GitHub as a proof of concept (teahubxyz/time, now read-only); ported to Gitea 2026-10-14.
Open this repo in Claude Code or Cursor and say "set up Time": the agent follows .claude/skills/time/SKILL.md. The recommended path needs one secret, ANTHROPIC_API_KEY: Claude seats plan, build and review (TIME_WORKER=claude:sonnet, TIME_REVIEW=claude:haiku; haiku, sonnet, opus, fable are the seats, priced in .github/time/seats.json). With VENICE_API_KEY instead, Venice seats do the same (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.