Skip to content

README, credit and install docs #11

Closed

Description

@JacobStephens2

Parent

#2

What to build

A README that lets someone else run thirdshift:

  • what it is, with the day-shift/third-shift framing and the quality-over-quantity principle;
  • usage (thirdshift <Issue URL>, stdout/stderr/exit codes, logs location);
  • install (cargo install --path .);
  • the runner's prerequisites: claude and gh logged in, git user.name and user.email, auto mode and what the classifier may block;
  • how Continuation and Failed runs behave.

Plus licensing: an MIT LICENSE for thirdshift, credit to mattpocock/skills, and his MIT copyright notice kept with the embedded Factory skills.

Acceptance criteria

  • README covers the purpose, usage, install, prerequisites, logs, Continuation, and Failed runs, using CONTEXT.md vocabulary
  • A LICENSE file (MIT) for thirdshift
  • mattpocock/skills credited in the README, and its MIT copyright notice included with the embedded skills

Blocked by

Activity

  1. JacobStephens2 commented on Sep 25, 2026

    @JacobStephens2
    OwnerAuthor

    Findings from the first real run of the walking skeleton (vacation#3 → JacobStephens2/vacation#13), worth covering in the README:

    Git identity. The runner's user needs a global user.name and user.email. Without them, the agent borrowed the last commit's author (see the comment on #4).

    What sessions leave outside the worktree. Sessions run with the Linux user's full permissions, and cleanup only removes thirdshift's own worktree, local Issue branch and temp plugin directory. This run left behind:

    • a JDK downloaded to ~/.local/jdk/ (the server had no Java)
    • a Playwright install in /tmp/pw (for a screenshot attempt)
    • the PR body draft in /tmp/pr3.md

    This is by design, but users should know. The README should suggest installing the target repo's toolchains up front, so agents don't download their own each run.

    Headless browser dependencies. The agent's screenshot attempt failed because headless Chromium needs libgbm1, which isn't installed by default on Ubuntu server. It fell back to checking the CSS by reading it. The README could mention installing libgbm1 for agents to verify UI changes visually.

    Subscription usage. When claude is logged in with a claude.ai subscription, runs use the plan's usage allowance, not API billing. The total_cost_usd in the logs is the API-price equivalent. An unattended run that hits the plan's usage limit will stall or fail partway through.

  2. added a commit that references this issue on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions