Checkout v6 added post-fetch validation that the checked-out ref matches
github.sha. The git shim was returning a fake placeholder SHA (aaaa...)
in dirty workspace mode while github.sha used the real HEAD SHA, causing
the validation to fail. Use realHeadSha consistently everywhere and
remove the now-unnecessary computeFakeSha helper.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
The previous approach symlinked workspace/node_modules → /tmp/node_modules,
which broke esbuild path resolution in pnpm monorepos. Tools like rwsdk's
directive scanner resolved paths through the symlink incorrectly, producing
paths like apps/web/tmp/node_modules/.pnpm/... instead of /tmp/node_modules/.pnpm/...
Mount the warm cache as a Docker bind mount directly at the workspace
node_modules path. This makes the filesystem layout identical to production
GitHub Actions. The original EBUSY concern is already mitigated by the git
shim (blocks git clean) and checkout patching (clean: false).
Adds a smoke test exercising esbuild resolution through pnpm workspace
symlinks to prevent regression.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: clean up runner directory on SIGINT/SIGTERM
The signal handler was missing `hostRunnerDir` from its cleanup list,
causing runner directories to leak when the process was interrupted
via Ctrl+C. Moved variable declarations above the handler so it can
reference `hostRunnerDir`, and added it to the cleanup loop.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: detect and kill orphaned containers via parent-PID liveness
Label every container with `agent-ci.pid=<PID>`. On startup, scan
running agent-ci-* containers and check if their parent PID is still
alive. Dead PID → orphan → kill it along with its sidecars and network.
Also wires up the existing but unused `pruneStaleWorkspaces()` to
remove run directories older than 24 hours.
Closes#186
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: make GitHub auth opt-in for remote reusable workflow fetching
Remove implicit credential resolution (gh auth token / GITHUB_TOKEN fallback)
that could silently send user credentials. Auth is now opt-in via
--github-token CLI flag or AGENT_CI_GITHUB_TOKEN env var.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* chore: add changeset for opt-in GitHub auth
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: add --github-token flag and AGENT_CI_GITHUB_TOKEN to docs
Update CLI reference tables, environment variables section, and
compatibility matrix to reflect opt-in GitHub auth for remote
reusable workflows.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: make commit status posting opt-in via --github-token
Gate postCommitStatus() on the githubToken parameter. When no token
is provided, print a warning instead of silently using implicit
gh CLI credentials.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: add --commit-status flag to opt in to posting GitHub commit statuses
Commit status posting now requires both --commit-status and
--github-token. Without --commit-status, no warning is printed
and no status is posted.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: add tests for 403 error hint and public repo fetch without auth
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Mark @redwoodjs/ts-runner as private and add it to changeset ignore
list. The package was being published to npm but version 0.7.0 is
returning 404 errors, breaking installs.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
The ts-runner package had a "test": "vitest run" script but no test
files. Vitest exits with code 1 when it finds nothing to run, which
has been failing the Release workflow since the package was added,
preventing changesets/action from creating release PRs.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: mount warm-modules at /tmp/node_modules for pnpm TypeScript compat
TypeScript resolves @types/* by walking up from realpath(). With pnpm's
.pnpm virtual store symlinked to /tmp/warm-modules, the upward walk never
finds a node_modules directory. Mounting at /tmp/node_modules instead means
TypeScript's walk from /tmp/node_modules/.pnpm/... naturally finds
/tmp/node_modules/@types/.
Closes#176
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: preserve git-tracked symlinks in workspace snapshot
copyWorkspace was using cp/fs.cpSync which dereference symlinks, causing
git mode 120000 entries to be dropped from the workspace commit. Now we
check lstat() before copying and recreate symlinks via symlinkSync.
Closes#178
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: add pnpm symlink smoke test reproducing #176 and #178
Adds a committed fixture at .github/fixtures/pnpm-symlinks/ with a
git-tracked symlink (mode 120000) and a TSX file that requires
@types/react resolution through pnpm's .pnpm virtual store.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
TypeScript resolves @types/* by walking up from realpath(). With pnpm's
.pnpm virtual store symlinked to /tmp/warm-modules, the upward walk never
finds a node_modules directory. Mounting at /tmp/node_modules instead means
TypeScript's walk from /tmp/node_modules/.pnpm/... naturally finds
/tmp/node_modules/@types/.
Closes#176
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support composite action step outputs and push event context
Enable workflows that use composite actions with cross-step output
references (e.g. Khan/actions@get-changed-files + filter-files) by:
- Preserving steps.* expressions for runner-time evaluation instead
of expanding them to empty string at parse time
- Using correct BasicExpression token type (type 3, not 6) matching
the runner's wire format
- Adding ContextName to steps so the runner can resolve
steps.<id>.outputs.<name> expressions
- Adding push event before/after SHAs and GITHUB_API_URL so
changed-files actions can call the compare commits API
- Implementing compare commits and list-PRs-for-commit mock endpoints
in the DTU server using git diff on the original repo
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: resolve symlinks in agent-ci-dev.sh so it works when invoked via symlink
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Wire `with:` inputs from caller workflows to called workflows via
`inputs.*` context, resolve `on.workflow_call.inputs` defaults, and
propagate `on.workflow_call.outputs` back so downstream jobs can
access `needs.<callerJobId>.outputs.*`. Also fixes intra-workflow
`needs.*` resolution for composite job IDs.
Adds smoke test, unit tests, /validate command, and CLAUDE.md agent rules.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Replace the nesting guard in expandReusableJobs with recursive expansion,
cycle detection, and a depth limit of 4 matching GitHub Actions' max.
Closes#167
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support local composite actions (`uses: ./.github/actions/...`)
Set RepositoryType to "self" for local action references so the runner
resolves them from the workspace instead of trying to download a tarball.
Add defensive guard in actiondownloadinfo to skip local/empty actions.
Closes#162
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* style: fix formatting in .docs/ files
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support local reusable workflows (uses: ./.github/workflows/...)
Inline called workflow jobs into the caller's dependency graph so that
`jobs.<id>.uses` with local refs works end-to-end. Includes dependency
rewiring, smoke tests, runner seed resilience fix, boot-failure log
surfacing, and dev script improvements.
Closes#149
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: update website compatibility matrix for reusable workflows
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: add section descriptions to website compatibility matrix
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: add descriptions to compatibility matrix legend items
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: add 'not planned' status icon to compatibility matrix
Distinguish architectural limitations (concurrency groups, GitHub
secrets) from features that could be implemented in the future.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support remote reusable workflows (uses: owner/repo/path@ref)
Pre-fetch remote workflow YAML from GitHub Contents API before expansion,
cache SHA refs forever and always re-fetch mutable tag/branch refs. Also
changes missing workflow files from warn+skip to hard failure.
Closes#165
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* refactor: split monolithic smoke-tests.yml into discrete workflow files
Each smoke test area now has its own workflow file for isolated failure
visibility: matrix, artifacts/services, cross-job outputs, job conditions,
reusable workflows (local + remote), and binary smoke.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* style: fix formatting in .docs/ files
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* docs: clarify agent-ci-dev.sh is for local development only
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* kindling: start task
* Add marketing strategy research and synthesis
- investigation-plan.md: scope and search strategy for both tracks
- research-developer-channels.md: how CI tools gain adoption (act case study, HN, Reddit, npm, messaging)
- research-agent-discoverability.md: how AI agents discover tools (llms.txt, CLAUDE.md, MCP, training data)
- marketing-strategy.md: synthesized multi-step plan for human devs and AI agents
* Fix three evidence quality issues flagged by Critic review
- Source the 844k llms.txt adoption figure to BuiltWith tracking dashboard
(trends.builtwith.com/robots/LLMS-Text, as of Oct 25 2025); add caveat
that other methodologies (NerdyData, SE Ranking) show far lower counts
- Reword LLMs-do-not-use-llms.txt claim from tested negative to absence
of public documentation — more accurate epistemic framing
- Replace unsourced act tutorial claims with verified direct URLs: Red Hat,
BrowserStack, Microsoft Azure, LogRocket, freeCodeCamp, plus 10 dev.to
article links confirming the organic tutorial coverage
* Tighten sourcing and hedging language per Critic precision review
- HN traffic numbers: hedge 10k-100k as 'commonly estimated' with no single controlled measurement; add in-text Nebula Graph citation for 300+ stars figure
- Act HN appearances: reduce 'at least four times' to 'multiple times' (only two item IDs substantiated)
- Tutorial blog claim: 'all recommend act' softened to 'Leading tutorial blogs...recommend'
- Overnight agent commits: remove unsourced '1,000+' figure; soften to 'large batches of agent-generated commits'
- Reddit comment claim: reframe 'drives qualified signups for months' as 'can drive sustained qualified traffic'; note it reflects SEO best-practice inference, not a case study
- HN/Product Hunt 100 vs 30 comparison: add in-text citation bracket linking to Medium source
* Fix four citation issues flagged by Critic review
- Fix 1: Add inline WebProNews link to February 9, 2026 GitHub Actions outage claim (both files)
- Fix 2: Add HN item ID inline for Dagger stats (item?id=30857012)
- Fix 3: Replace 'typical' with 'commonly observed as' / 'reported in case studies'
- Fix 4: Generalize act fork/dependent stats with link to current repo instead of bare numbers
* Update strategy with Apr 7-9 tweet learnings and revised positioning
The Apr 7 "Running GitHub Actions locally" tweet hit 78K impressions —
revealing that the universal developer pain point is the primary hook,
not the AI agent angle. This updates the strategy doc with performance
data, a revised positioning funnel (hook → explain → differentiate →
convert), updated HN draft, and new action items. Adds tweet tracking
for the Apr 7-9 thread.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Add tweet queue with 8 drafts following screenshot-first formula
Each tweet follows the pattern that drove 78K impressions on Apr 7:
one-line hook, terminal screenshot, no AI-agent lead. Covers dirty
tree, speed comparison, retry, git hooks, service containers, matrix
strategy, quiet mode, and act comparison. Includes posting order and
cadence recommendations.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Remove the useless try/catch wrapper in handleWorkflow so errors are
only reported once by the top-level catch handler.
Closes#154
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: auto-detect Docker socket path when DOCKER_HOST is not set
Resolves#158. Adds resolveDockerSocket() which finds the Docker daemon
socket by checking DOCKER_HOST, resolving symlinks at /var/run/docker.sock,
parsing `docker context inspect`, and falling back to well-known macOS
provider paths (OrbStack, Docker Desktop, Colima, Lima). Throws with
actionable guidance when no socket is found.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: lazy-init Docker socket resolution and client
Defer resolveDockerSocket() and Dockerode construction until first use
so that module import (e.g. --help) doesn't throw or shell out to
docker context inspect on machines without Docker.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: suppress stderr leak and support non-origin remotes
- Extract `getFirstRemoteUrl()` that prefers 'origin' but falls back to
the first available remote, with stdio piped to suppress stderr
- Use `process.cwd()` instead of `PROJECT_ROOT` in `deriveGithubRepo()`
so it detects the user's repo, not the CLI install location
- Share the helper between config.ts and cli.ts
Closes#152
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: handle trailing slash in remote URLs
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: add tests for parseRepoSlug and getFirstRemoteUrl
Extract regex parsing into exported parseRepoSlug() so both
config.ts and cli.ts share the same logic, and it's testable.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* refactor: simplify getFirstRemoteUrl to single git remote -v call
One process spawn instead of up to three.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* refactor: extract resolveRepoSlug into config.ts with tests
Move repo detection out of cli.ts private function into a shared,
exported resolveRepoSlug() in config.ts so it's testable and
eliminates the duplicated logic between config.ts and cli.ts.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: don't auto-detect repo at import time from process.cwd()
The config default is just a last-resort fallback. Real detection
happens via resolveRepoSlug(repoRoot) in cli.ts, anchored to the
workflow path — process.cwd() at import time was a guess that could
be wrong.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: throw when repo cannot be detected instead of using unknown/unknown
Silently defaulting to "unknown/unknown" would produce wrong API URLs,
container env vars, and directory names. Now resolveRepoSlug() throws
with a clear message pointing users to set GITHUB_REPO.
Also removes dead config.GITHUB_REPO fallbacks from runner code — the
repo slug is always resolved from the workflow path in cli.ts before
jobs are created.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* refactor: use git config instead of parsing git remote -v output
git config --get remote.<name>.url returns just the URL — no
tab-delimited line parsing needed.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: propagate workflow-derived repo slug back to config.GITHUB_REPO
Once resolveRepoSlug detects the repo from the workflow path, write
it back to config.GITHUB_REPO so downstream code (commit-status.ts,
runner fallbacks) sees the correct value without needing it passed
through explicitly.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: env var GITHUB_REPO overrides auto-detection, not the reverse
GITHUB_REPO env var is the explicit override; auto-detection from
the workflow's git remote is the default.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: verify GITHUB_REPO env var overrides auto-detection
Tests the priority contract: env var wins over git remote detection,
auto-detection is the fallback, and missing both throws.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* refactor: make githubRepo required in CreateRunDirectoriesOpts
It's always provided by cli.ts after resolveRepoSlug. Remove the
inconsistent defensive fallbacks ("unknown-repo" vs "repo") that
were dead code.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use git remote get-url instead of git config --get
git config reads from the config hierarchy (local → global → system),
so on CI runners where actions/checkout configures git globally, it
finds the parent repo's remote.origin.url even inside a fresh git init
temp dir. git remote get-url is scoped to the repo's own remotes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use DOCKER_HOST socket path for container bind mount
The Docker socket bind mount was hardcoded to /var/run/docker.sock on the
host side, ignoring DOCKER_HOST overrides. Extract the resolved socket path
and pass it into buildContainerBinds so the host side matches the actual
daemon socket.
Closes#155
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: don't run dockerSocketPath through toHostPath
The socket path is already a host path (from DOCKER_HOST or the default),
so it should not be remapped by toHostPath which translates container
paths to host paths in nested Docker scenarios.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: enable horizontal scroll on code blocks in mobile in-app browsers
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use overflow-clip on Terminal and Panel components for mobile scroll
The outer overflow-hidden on these components creates a scroll container
that intercepts touch gestures in mobile WebViews, preventing the inner
overflow-x-auto from being scrollable. overflow-clip provides the same
visual clipping for rounded corners without creating a scroll container.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: make AGENTS.md terminal block full-width instead of half-grid
The AI Agent Integration section was in a 2-column grid with Quick Start,
constraining the AGENTS.md code block to half the page width. Now Quick
Start uses a 3-column grid for its short terminal blocks, and the
AGENTS.md block spans the full content width below.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: stack Quick Start terminals full-width instead of 3-column grid
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: stack Architecture Comparison as cards on mobile
Replace the horizontal table with stacked cards on mobile (md:hidden),
with the Agent CI row highlighted at the bottom of each card. Desktop
keeps the table layout.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
When @actions/workflow-parser cannot model certain expressions (e.g.
runner.temp in env values), it may return a template without a jobs
array. This caused a TypeError crash. Adding nullish coalescing
fallbacks lets the existing "no jobs found" / "task not found" error
paths handle these cases gracefully.
Closes#96 (issue 1 of 3).
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Introduces the packages/ts-runner package skeleton with build config,
planning docs (PLAN.md, SPEC.md), and a research document exploring
RivetKit Agent OS integration. No runtime code yet — this sets up the
foundation for subsequent PRs.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Adds a test that verifies resolveDtuHost() correctly uses the
AGENT_CI_DOCKER_BRIDGE_GATEWAY env var when the fs.existsSync mock
intercepts the /.dockerenv check. Verified passing both locally and
inside Docker via agent-ci.
Closes#126
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: propagate job-level env into DTU Variables and add AGENT_CI_LOCAL to container env
Closes#104. Job-level `env` from the CLI payload was not propagated into
the DTU's Variables store or ContextData, so `AGENT_CI_LOCAL` was unavailable
to the runner's expression engine. Also adds `AGENT_CI_LOCAL=true` to the
Docker container env for shell access.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* ci: re-trigger agent-ci checks
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: treat runner that never contacted DTU as failure
When the runner container exits with code 0 but never sent any timeline
entries (isBooting is still true), the job was incorrectly reported as
succeeded. Now checks !isBooting in the jobSucceeded condition.
Closes#102
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: treat runner that never contacted DTU as failure
When the runner container exits with code 0 but never sent any timeline
entries (isBooting is still true), the job was incorrectly reported as
succeeded. Extract isJobSuccessful() and add tests covering the #102
regression case.
Closes#102
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: remove stopped containers before network prune to prevent address pool exhaustion
Closes#107
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: clean up all containers on signal, not just the first job's
Each job registered process.once("SIGINT") with process.exit(1) in
the handler. The first handler to fire would kill the process before
other jobs' handlers could clean up their containers, leaving them
running indefinitely.
Changed to process.on so all handlers fire, removed process.exit(1)
from per-job handlers, and added a top-level handler in cli.ts that
defers exit until after all per-job cleanup completes.
Closes#107
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
When running --all, jobs seeded without runnerName landed in the shared
generic pool where runners from other concurrent workflows could steal
them, causing single-job workflows to hang indefinitely.
- Pin job.runnerName = containerName before the /_dtu/seed call
- Move container and ephemeralDtu cleanup into finally block
- Add process.setMaxListeners(0) for parallel job EventEmitter warnings
- Add reproduction test for generic pool job stealing
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: support pull_request_target in workflow relevance check
Treat pull_request_target identically to pull_request in isWorkflowRelevant(),
applying the same branch and paths filter logic. This fixes agent-ci --all
skipping workflows that use pull_request_target.
Closes#106
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: Docker container name collision when running multiple workflows via --all
Pre-allocate unique base run numbers per workflow before launching them
in parallel, so job suffixes (-j1, -j2, -j3) never produce duplicate
container names across concurrent workflows.
Closes#125
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: resolveDtuHost test and smoke-tests build
Clear AGENT_CI_DTU_HOST in resolveDtuHost tests so the bridge gateway
test exercises the correct code path when running inside agent-ci's
Docker containers (which inject AGENT_CI_DTU_HOST).
Scope binary-smoke build to @redwoodjs/agent-ci... to avoid building
apps/website which fails due to warm-modules symlink resolution.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use atomic mkdir for concurrent log directory allocation
Closes#105
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: add tests for atomic log directory allocation
Tests EEXIST collision handling, multiple consecutive collisions,
and uniqueness across many sequential calls.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: clear AGENT_CI_DTU_HOST in resolveDtuHost tests
The resolveDtuHost function returns early if AGENT_CI_DTU_HOST is set.
When tests run inside Docker via agent-ci, this env var is present,
causing the bridge gateway test to be bypassed.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
The catch block in handleWorkflow was returning an empty array on error,
causing the CLI to exit 0 even when workflow setup failed. Now re-throws
so failures propagate and exit non-zero.
Closes#101
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: action tarball disk cache, step output capture, and demo recording
- Cache action tarballs on first download and serve from disk on re-runs,
eliminating ~30s GitHub CDN delays
- Capture step output via tee to signals dir for reliable pause-on-failure
tail display
- Fix CLI to treat empty results as failure and skip summary print
- Add marketing demo recording setup with VHS tape and test project
- Add `agent-ci` script alias in root package.json
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* test: add tests for action tarball cache, group filtering, and empty-results fix (#119)
Cover the untested changes from the tarball cache PR: action tarball proxy
cache hit/miss, download info URL rewriting with sub-path stripping, step
output group filtering, tee output capture, and CLI empty-results exit logic.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: prevent concurrent tarball cache-miss race condition
Use an in-flight download map so concurrent requests for the same
tarball coalesce into a single GitHub fetch instead of racing on
the same tmp file, which could cause corruption or rename errors.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: use relative path in demo.tape for portability
Replace hard-coded absolute path with a relative path so the demo
recording works on any contributor's machine.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: correct sanitized-refs test to assert 404 for slash-containing refs
The test was passing vacuously (status >= 200 matches 404). Now it
properly asserts that Polka does not bind :ref across slashes, so
slash-containing refs return 404 and do not serve cached content.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: only mount relevant PM cache based on detected package manager
Projects using npm/yarn/bun no longer get unnecessary pnpm store bind
mounts (and vice versa). Detects PM from lockfile and conditionally
creates cache dirs, bind mounts, and virtual cache patterns.
Closes#112
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* chore: add debug log for detected PM, remove verbose bind mount log
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test: add PM-scoped caching integration tests
Tests createRunDirectories and buildContainerBinds for each package
manager (npm, pnpm, yarn, bun) plus the no-lockfile fallback. Each
test creates a real git repo fixture with the relevant lockfile and
verifies only the correct PM's cache dir and bind mount are produced.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat: show Docker image pull progress during runner boot
Display download progress (bytes downloaded / total with percentage) as
a sub-step under "Starting runner" while pulling the container image.
Aggregates per-layer progress from the Docker API and throttles UI
updates to every 250ms.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: only track Downloading events for pull progress
Extracting events reset the current byte count per layer, making
overall progress appear stuck or go backwards. Filter to only
"Downloading" status events so progress climbs steadily to 100%.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: handle Download complete events to reach 100%
Docker's last event per layer is "Download complete" with no
progressDetail, so layers were never marked as fully downloaded.
Now explicitly set current = total when a layer completes.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* debug: log all docker pull events to diagnose stuck progress
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: track download and extraction phases separately
The progress was getting stuck because:
1. "Download complete" events fired rapidly and got throttled
2. Extraction phase was invisible — no events passed the filter
Now tracks downloading and extracting as separate phases with
independent progress maps. The UI shows "Downloading: X/Y (Z%)"
then transitions to "Extracting: X/Y (Z%)" once extraction begins.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: force UI update on download→extract phase transition
The throttle was swallowing the first "Extracting" event, leaving
the display frozen on the last download snapshot. Now flushProgress
accepts a force flag and the first extraction event always triggers
an immediate store update regardless of throttle timing.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat: show reset hint when image pull takes over 60s
After 60s of pulling, shows a dim hint beneath the progress line:
"Taking a while? Run: docker rmi <image>"
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* debug: log logDir presence in boot node renderer
* fix: remove debug logging, shorten logDir, lower hint threshold to 30s
- Remove debug-renderer and pull flush diagnostic logging
- Shorten logDir display path to agent-ci/cli/runs/... so it stays
visible alongside the progress line without wrapping
- Lower the "Taking a while?" hint threshold from 60s to 30s since
Docker stalls immediately when resuming a partially cached layer
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat: remove reset hint from pull progress display
The docker rmi hint wasn't helpful since it doesn't fix the stalled
download (the partial blob lives inside Docker's VM, not the layer
store). Removed along with the now-unused image/startedAt fields.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* feat(website): add blog section with first post
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(website): integrate blog section with routing and styles
* Add lock file.
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat(website): add Copy Agent Instructions button to hero and quick start sections
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore: remove retry-proof failure test from CI
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Three fixes discovered while running agent-ci against a ~40K file
pnpm/turbo monorepo:
1. Sub-path actions (e.g. `actions/cache/save@v5`) produce invalid
tarball URLs. The DTU was using `action.nameWithOwner` directly
which includes the sub-path, producing
`api.github.com/repos/actions/cache/save/tarball/v5` (404).
Fix: strip to `owner/repo` before constructing the URL.
2. `copyWorkspace` uses `execSync("git ls-files ...")` with the
default 1MB maxBuffer. Repos with 30K+ tracked files overflow
this, causing ENOBUFS and an empty workspace in the container.
Fix: increase maxBuffer to 100MB.
3. Post-success cleanup `fs.rmSync(containerWorkDir)` can throw
ENOTEMPTY when the container hasn't fully released file handles.
Fix: wrap in try/catch for best-effort cleanup.
github-actions[bot]