quc: hand an agent your repo, sit in the chair, watch #220

Closed
opened 2026-10-22 07:24:47 +00:00 by teahubxyz · 4 comments
Owner

What it is

quc (future home quc.lol; v0 at quc.yolopreneur.lol, slug quc) is a tongue-in-cheek coding agent app. You give it a repo and one task; a cocky agent runs it in full yolo mode and you only get to watch. The joke is the cuckjak meme: every place a normal agent tool asks "approve this change?", quc shows you the corner-chair view instead. The change is already happening. Your options are watch, safeword, or say the magic words.

It is a real product underneath the joke: yolo-mode agents are scary because you either trust them or babysit them. quc makes "you can't touch anything" the experience, and makes it safe by running everything on a throwaway branch.

Tone: cheeky, adult-humour adjacent, never explicit. No sexual content, no slurs; the bit is power dynamics and swagger, not anything graphic.

v0 scope

  1. Start a run. Paste a public GitHub repo URL and a one-line task. One run per visitor at a time.
  2. The cage. The agent works in a sandbox on a fork/throwaway branch with full permissions (--yolo). It never touches the user's default branch and never pushes to the user's repo.
  3. The chair (main view). Read-only, live: a diff stream of files changing, commits landing, and the agent's running commentary. There is no approve, edit or accept button anywhere. Visual: a small chair-in-the-corner motif; confirmations are replaced by "you may watch".
  4. The agent's attitude. Persona powered by Grok (the factory's Venice Grok seat): swaggering, teasing narration of what it's doing to your code ("rewriting your auth layer, you weren't using it right anyway"). The persona narrates; the actual edits come from the coding seat.
  5. Safeword. One big, always-visible button. Kills the run immediately and discards the branch. Must work within a couple of seconds, every time; this is the trust mechanic.
  6. Key phrases (unlock the cage). Typing a phrase in the single input box unlocks one notch, each with a reaction from the persona:
    • notch 1: leave a note the agent must read and respond to
    • notch 2: veto one file (the agent reverts and avoids it)
    • notch 3: full unlock, take the wheel (run ends, you get the branch)
      Phrases are discoverable but not obvious (hints in the persona's lines). Unknown input just gets mocked.
  7. The replay. When a run ends (finished, safeworded or unlocked), a shareable link with a scrubber over the timeline: diffs, commentary, unlock moments. "Watch what quc did to my repo." No account needed to view.
  8. Aftermath card. Lines touched, files changed, tests broken/fixed, and the branch as a downloadable patch.

Limits and safety for v0

  • Public repos only; size cap (e.g. 50 MB, 2,000 files). One task, time cap (e.g. 10 minutes), token cap per run, daily run cap per visitor.
  • Sandbox has no secrets, no outbound network except the package registries the build needs.
  • Nothing is pushed anywhere except the run's own storage; the patch is the only output.
  • Replays are public by link; the start screen says so.

Done when

  • quc.yolopreneur.lol loads the start screen with the pitch and the repo + task form.
  • A run against a small public repo streams live diffs and persona commentary in the read-only chair view.
  • Safeword stops a run in under 5 seconds and the branch is gone.
  • At least one key phrase notch works end to end.
  • A finished run produces a replay link with a working scrubber, viewable logged out.
  • Phone and desktop render cleanly.

Later (not v0)

Private repos via GitHub app, paid unlock tiers tied to key phrases, multiple agents ("bring a friend"), leaderboard of most-destroyed repos.

## What it is **quc** (future home quc.lol; v0 at `quc.yolopreneur.lol`, slug `quc`) is a tongue-in-cheek coding agent app. You give it a repo and one task; a cocky agent runs it in full yolo mode and you only get to watch. The joke is the cuckjak meme: every place a normal agent tool asks "approve this change?", quc shows you the corner-chair view instead. The change is already happening. Your options are watch, safeword, or say the magic words. It is a real product underneath the joke: yolo-mode agents are scary because you either trust them or babysit them. quc makes "you can't touch anything" the experience, and makes it safe by running everything on a throwaway branch. Tone: cheeky, adult-humour adjacent, never explicit. No sexual content, no slurs; the bit is power dynamics and swagger, not anything graphic. ## v0 scope 1. **Start a run.** Paste a public GitHub repo URL and a one-line task. One run per visitor at a time. 2. **The cage.** The agent works in a sandbox on a fork/throwaway branch with full permissions (`--yolo`). It never touches the user's default branch and never pushes to the user's repo. 3. **The chair (main view).** Read-only, live: a diff stream of files changing, commits landing, and the agent's running commentary. There is no approve, edit or accept button anywhere. Visual: a small chair-in-the-corner motif; confirmations are replaced by "you may watch". 4. **The agent's attitude.** Persona powered by Grok (the factory's Venice Grok seat): swaggering, teasing narration of what it's doing to your code ("rewriting your auth layer, you weren't using it right anyway"). The persona narrates; the actual edits come from the coding seat. 5. **Safeword.** One big, always-visible button. Kills the run immediately and discards the branch. Must work within a couple of seconds, every time; this is the trust mechanic. 6. **Key phrases (unlock the cage).** Typing a phrase in the single input box unlocks one notch, each with a reaction from the persona: - notch 1: leave a note the agent must read and respond to - notch 2: veto one file (the agent reverts and avoids it) - notch 3: full unlock, take the wheel (run ends, you get the branch) Phrases are discoverable but not obvious (hints in the persona's lines). Unknown input just gets mocked. 7. **The replay.** When a run ends (finished, safeworded or unlocked), a shareable link with a scrubber over the timeline: diffs, commentary, unlock moments. "Watch what quc did to my repo." No account needed to view. 8. **Aftermath card.** Lines touched, files changed, tests broken/fixed, and the branch as a downloadable patch. ## Limits and safety for v0 - Public repos only; size cap (e.g. 50 MB, 2,000 files). One task, time cap (e.g. 10 minutes), token cap per run, daily run cap per visitor. - Sandbox has no secrets, no outbound network except the package registries the build needs. - Nothing is pushed anywhere except the run's own storage; the patch is the only output. - Replays are public by link; the start screen says so. ## Done when - `quc.yolopreneur.lol` loads the start screen with the pitch and the repo + task form. - A run against a small public repo streams live diffs and persona commentary in the read-only chair view. - Safeword stops a run in under 5 seconds and the branch is gone. - At least one key phrase notch works end to end. - A finished run produces a replay link with a working scrubber, viewable logged out. - Phone and desktop render cleanly. ## Later (not v0) Private repos via GitHub app, paid unlock tiers tied to key phrases, multiple agents ("bring a friend"), leaderboard of most-destroyed repos.
teahubxyz added the specventure labels 2026-10-22 07:24:47 +00:00

⏱️ Time: planned #221, #222, #223, #224, #225, #226, #227, #228, #229, #230, #231, #232, #233, #234, #235, #236. They run one at a time: each starts when the one before it merges.

⏱️ Time: planned #221, #222, #223, #224, #225, #226, #227, #228, #229, #230, #231, #232, #233, #234, #235, #236. They run one at a time: each starts when the one before it merges. <!-- time {"beat":"planned","cards":[221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236]} -->
time added planned and removed spec labels 2026-10-22 08:08:35 +00:00

⚠️ planned failed (1/3): 'winner'. Retrying next tick.

⚠️ planned failed (1/3): `'winner'`. Retrying next tick. <!-- time {"venture":true,"beat":"planned","cards":[221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236],"at":"2026-10-22T08:08:35Z","errors":1} -->

⚠️ planned failed (2/3): 'winner'. Retrying next tick.

⚠️ planned failed (2/3): `'winner'`. Retrying next tick. <!-- time {"venture":true,"beat":"planned","cards":[221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236],"at":"2026-10-22T12:28:21Z","errors":2} -->

🧭 Digest: stuck at planned after 3 tries: 'winner'. Closing; the next card starts fresh.

🧭 Digest: stuck at `planned` after 3 tries: 'winner'. Closing; the next card starts fresh. <!-- time {"venture":true,"beat":"done","stuck":"planned"} -->
time closed this issue 2026-10-23 00:28:17 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: teahubxyz/time#220