Open source · Apache-2.0
Your backlog works the night shift.
Coding agents take the ready tickets of your tracker and deliver verified pull requests. The questions they could not settle are waiting on the ticket at breakfast.
One ticket, start to merge
No new board to learn: the questions, the answers and the delivery report live on the ticket you already write. Below, a real run of Owlshift on its own backlog, in UTC: the ticket is kept in a private Linear workspace, the pull request is public.
-
Nov 8
You mark the ticket ready
OWL-513 asks for a red check that fails outside the branch to be re-run before anything is repaired. You file it ready; intake reads it four minutes later.
-
A question only you can answer
Re-running a job needs a permission Owlshift's GitHub App does not ask today. Owlshift settled five other points itself, and asked you this one on the ticket.
QUESTIONS · round 1
Q1 · May Owlshift's GitHub App ask Actions (write) so the runner can re-run jobs?
Reply
Q1: A,okto take every recommendation, or in your own words. -
You answer when you have a minute
Q1: A, thengo. The answer is checked before anything resumes: half an answer is asked again. -
A plan, before any code
The design is written with your answer, reviewed by a fresh run, then put to you for approval. You approve it at 23:49.
-
Nov 10
A verified pull request
The build waited a day, while other tickets held a design document it would change. The project's gate passed, and Verify's findings were answered. You merged it at 07:49.
✓#486Re-run a red check once before any fix run
What's different
Ticket-to-agent runners exist. Owlshift makes three bets of its own.
01
The question loop is the product
Questions can come at any stage, and they are asked on the ticket. The answer is checked before anything resumes, and there is no limit on rounds.
02
Scheduling is enforced
Blockers gate dispatch. Declared resources keep two tickets in flight from colliding, whether an agent or a person holds them.
03
A ticket is a pipeline, not a session
A plan before code, review by a fresh run, on another model when the configuration names one, the project's gate run confined, and the cost measured for each ticket.
It stays yours
Your tracker
Linear, GitHub Issues or Markdown files in your repository. Questions, answers and delivery reports live on the ticket: no new board.
Your agents
Claude Code, with Codex if you want it, on your own subscription. Owlshift never asks for a model API key.
Your machine
One light native background service. Agent runs are confined, and secrets are kept in the system keychain.
Your merge
No agent merges. Owlshift opens the pull request and repairs it; merging stays a person's unless the project opts in.
What it is not
- Not an IDE, a chat or a new board.
- Not an auto-merger by default.
- Not a hosted service.
Install
Install the latest release, on macOS, on Linux, or on Windows through WSL2.
macOS
brew tap pitchopp/owlshift https://github.com/pitchopp/owlshift
brew trust --formula pitchopp/owlshift/owlshift
brew install owlshift
Linux, and Windows through WSL2
curl -fsSL https://raw.githubusercontent.com/pitchopp/owlshift/main/install.sh | sh
Then owlshift doctor checks the machine: git, Claude Code, and whether agent runs can be confined.
Adopt a project
owlshift init in your repository to a first pull request, then to the background service.
Adopt a project on Linear
GitHub Issues
Your tickets are the repository's own issues.
Adopt a project on GitHub Issues
Markdown files
Your tickets live nowhere yet, or you want to try without an account.
Adopt a project with Markdown tickets
Owlshift is young: several developers on one project, a runner on a server, more trackers and forges and a desktop app are later steps of the roadmap. See the latest release.