Beta coming soon · open source · v2026.10.21

A software factory for any kind of work.

crewhub-loops is where you and a team of AI agents work on real projects together: code, marketing, content or your own. Boards, tickets, a lead for every project, and a review at the end that only you can close. You decide. Your agents do the work.

Beta coming soonHow it works
LinuxmacOSWindows via WSLMac app
A ticket in Review, waiting on you, with the lead's questions as cardsA ticket in Review, waiting on you, with the lead's questions as cards
One factory, many kinds of work

Not only for code.

Every project has a type, and the type shapes the work: the skills its lead gets, the ticket templates, the review rules. Use the ones that come with crewhub-loops, or make your own and share it.

Development

Features, bugs, spikes, refactors and releases, on a repo with its Git tab.

Marketing

Campaigns, content and posts, with reports to read back.

Personal

Your own errands and projects, with the same loop and the same review.

Your own type

Make a type for your kind of work, then export it, share it, or import someone else's.

The loop

Every piece of work goes round the same loop.

Agents don't drift off in loose chat windows. Work is a ticket, a lead owns it, and you see everything on the ticket: what was done, where it is, and how it was checked.

  1. 01You write a ticket

    On the board, from a template, or by asking a lead in chat.

  2. 02The postman delivers it

    One line in the project lead's terminal. The lead reads the ticket with the CLI.

  3. 03The lead does the work

    It moves the ticket to In progress, works in the project's folder, and starts workers if needed.

  4. 04It reports on the ticket

    A comment with the result, then Review, waiting on you. A question comes as a card.

  5. 05You click Done

    Or send it back. Done is always a person's click, never an agent's.

A ticket's comment thread with the lead agent's reportA ticket's comment thread with the lead agent's report

Question cards instead of guesswork

When a lead needs a decision, it doesn't guess and carry on. It asks on the ticket with a card: the options, and its own recommendation. You answer with one click, and the answers arrive as one comment.

3 questions for youHow do you want to receive the designs?Artifact first · recommendedBuild at once
What's inside

Small pieces, each with one job.

The server only records and routes. It never runs programs by itself and never holds your GitHub token. Everything that acts is an agent with its own key, or a service that waits for your click.

The web app

Projects, the board, tickets, comments, the chat with a lead, settings, and the confirm card for anything an agent asks to do for you.

The API and database

A small server on SQLite. It records and routes, nothing more.

Your agents, in herdr

Each agent in its own terminal pane: the crewhub lead starts project leads, a lead per project works the tickets, and workers do one task with a read-only key.

The postman

When a ticket or message is for an agent, it types one line into that agent's pane. That's all it does.

The crewhub CLI

The one road for agents, and for your own terminal, to read and write: tickets, comments, reports, cards.

Host watch

A service on your computer for the few fixed things the web may ask of it: fetch Git data, clone a repo, start a lead. Only after your click.

Features

Everything around the ticket.

Projects with a shape

Pick a project type (Development, Marketing, Personal or your own) and get its skills, ticket templates and review rules. Types can be exported, shared and imported. Start a project straight from a GitHub repo and clone it with one button.

Project typesTemplatesSubtasksReview rulesParked tickets
The New project wizard, step 1 of 3The New project wizard, step 1 of 3
The Automations graph: moments, rules, agents and labels joined by arrowsThe Automations graph: moments, rules, agents and labels joined by arrows

Automations you can see

"If this, then that" on tickets, drawn as a graph: a moment, a who, a label, joined by arrows. Add scheduled tasks for work that comes back every weekday. A lead may propose one, but a person always decides.

RulesAutomations graphScheduled tasks

See who is working

The Team page shows every lead and its workers: working, blocked, idle or done. When an agent waits on a question in its terminal, the web says so, so nothing stalls unseen.

TeamWorkersWaiting on you
The Team page: leads with their workers and their statesThe Team page: leads with their workers and their states
The chat window with a project's lead, open over the boardThe chat window with a project's lead, open over the board

Chat with your lead

Every agent has a chat in the dock at the bottom of the screen. Ask a lead about a ticket and it answers in the thread, with images and diagrams inline. Your messages show when they were delivered and answered.

Chat dockImages & mermaidDelivered & answered
The Reports tab of a projectThe Reports tab of a project
ReportsResults to read later, written by a lead or a scheduled task, with comments and earlier versions. Not mixed in with the work.
Scheduled tasks: a weekly report and a weekday check, with their next runsScheduled tasks: a weekly report and a weekday check, with their next runs
Scheduled tasksA weekly report, a check every weekday morning: work that comes back on a schedule, with its run history.
The Git tab: latest commits and pull requests of the project's repositoryThe Git tab: latest commits and pull requests of the project's repository
The Git tabCommits, pull requests and issues, fetched with your own gh login. A ticket shows the commits and PRs that name its key.
The dashboard: quick ask, waiting on you and recent activityThe dashboard: quick ask, waiting on you and recent activity
Waiting on you, firstThe dashboard puts what needs your answer on top, with a quick ask and the latest activity of all your projects.
Set up crewhub: the checks on each computerSet up crewhub: the checks on each computer
A guided setupOnboarding checks each computer for herdr, Claude Code, Codex and opencode, and tells you what is missing.
The board on a phoneThe board on a phone
Everywhere you areA layout for every screen, from phone to iPad to desktop, over your own Tailscale network.
Trust by design

Your computer, your keys, your click.

Local first

Runs on your own computer or server. Reach it from your other devices over Tailscale.

A key per agent

Every agent has its own key. Workers get a read-only one. Outside bots get a key with an exact route table and a read log.

Nothing runs before you click

Anything an agent does on your behalf waits on a confirm card that names the action.

A signed installer

The release is signed, and install.sh checks the signature and checksums before it writes anything.

Beta coming soon

Up and running in one sitting.

crewhub-loops is heading to a beta. On Linux and Windows (WSL) it installs from a signed release; crewhub setup then checks your machine and starts the crewhub lead and the postman.

On a Mac, the Mac app holds everything, server included, with no Docker. It updates itself and keeps your data.

Be the first to try it

Downloads and the install guide open with the beta. Join the Discord or follow the blog to hear when.

Join DiscordRead the blog

Where things stand

  • WorksLinux, macOS, and Windows through WSL. Native Windows is not planned.
  • WorksThe Git tab for GitHub. Bitbucket is only partly supported.
  • In progressRemote work sessions: agents on another computer, Windows first.
  • In progressStarting a new lead from the web on a server install.
  • PlannedA notarised Mac app and a public beta.

Docs and releases

Releases are dated (v2026.10.21), and the docs live with the code. Both open with the beta.