Skip to content
kinged007Public

About

Run autonomous coding agents against your GitHub issues and PRs — label an issue, an agent plans, builds, reviews and merges.

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Jigz

CI Release Go

Run autonomous coding agents against your GitHub issues with one command.

jig watches a repo's issues and pull requests, and for each labeled item spins up an AI coding agent that reads the issue, writes the code, and moves the work forward — planning, implementing, reviewing, and merging — mostly on its own. You manage the backlog by adding labels and assigning issues; the agents do the rest. GitHub is the only supported tracker.

Features

  • One command per repo: jig setup, then jig runs every loop in the foreground (or jig start in the background) plus a read-only web dashboard.
  • Label-driven backlog: add agent:build to an issue and the agent plans, codes, opens a PR, and chains through review to merge.
  • Two loops in the config that setup writes: issues (plan, build, docs) and prs (review, review-fix, merge); add a work: entry to add a loop.
  • Spend and schedule guardrails: per-loop token budgets, working hours, idle sleep, and workspace cleanup.
  • Fleet support: agent accounts and pools with usage-limit failover, and one shared dashboard across repos (--unite).

Quickstart

# once per machine (macOS/Linux): installs jig to ~/.local/bin/jig
curl -sSL https://raw.githubusercontent.com/kinged007/jigz/main/install.sh | sh
export GITHUB_TOKEN="ghp_..."   # or GH_TOKEN; needs Contents, Issues, Pull requests read/write

cd your-repo
jig setup     # writes .jigz/, generates the workflows, creates the labels in config.yaml, installs the engine
              # (jig setup --skip-build leaves out the workflows and labels)
jig           # run every loop in the foreground (Ctrl-C stops all)

Then, on GitHub: assign an issue to yourself and add the agent:build label. The loop polls roughly every 60 seconds, claims the issue, works on a auto/<issue-number> branch, and opens a PR labeled agent:review. See docs/usage.md and docs/concepts.md.

Requirements

  • macOS or Linux (Windows is unsupported, see Known limitations).
  • A GitHub token with repo scope (classic) or Contents, Issues, Pull requests read/write (fine-grained); see the token setup.
  • The gh CLI on PATH.
  • A coding agent CLI: Claude Code (claude) by default, or pi.
  • Go 1.26.0 or newer only to build from source.

How it works

Every loop polls GitHub roughly every 60 seconds with a search query built from trigger labels plus in-progress, scoped to assignee:@me and excluding needs-human. Claiming an item adds in-progress; the agent works on an auto/<issue-number> branch and routes its output through labels: build opens a PR labeled agent:review, review sends it back as agent:build or stops at agent:done, and an approved PR waits for a person to label it agent:merge. Because the trigger stays on the item for the whole run, an interrupted loop finds it again on the next poll. Details: docs/concepts.md.

Documentation

Known limitations

  • One crashed loop stops the run. A loop process exiting ends jig, as a signal does. The remaining loops are stopped cleanly and the registry entry is dropped, but nothing restarts them.
  • Prompt files are not version-stamped. A prompt file you have not edited is not updated when the binary is upgraded. Delete it and re-run setup to take the shipped version.
  • Windows is unsupported. The engine releases a .zip; the installer reads tar.gz.

Roadmap

  • Restart a loop that exits instead of ending the run. Currently one crashed loop stops every other loop; see Known limitations.
  • Stamp prompt files with the binary version that wrote them, so an upgrade can offer a new version of a file the user has not edited.

The full ordered plan lives in ROADMAP.md; where the product is heading is in VISION.md.

Contributing

Bug fixes and features go through GitHub issues and pull requests. Build and check with go build ./... && go vet ./... && gofmt -l cmd internal && go test ./...; see CONTRIBUTING.md for the test setup, commit style, and engine-bump rule.

Support

  • Questions about behavior: open a GitHub issue with the jig version (jig --version), the loop logs (.jigz/logs/<workflow>.log), and the workflow file involved.
  • Security issues: do not open a public issue; see SECURITY.md.

License

Apache-2.0; see LICENSE.

About

Run autonomous coding agents against your GitHub issues and PRs — label an issue, an agent plans, builds, reviews and merges.

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages