Ready-to-use agents

There are two ways to start. hubzoid init writes a small starter you grow yourself, as in the quickstart. A ready-to-use Hub is a complete agent for one job, in its own GitHub repository, that you clone and set up from its README.

By the end of this page you will know what each ready-to-use Hub does, what it needs and the one command that gets it onto your machine.

Choose a HubCopy Anchor Link

hubzoid init prints these clone lines too. It still lists Engineering Desk under its earlier name, GitZoid, with the old address, which GitHub forwards to the new one. Every Hub is a normal Hub folder, so project structure applies to all of them.

Software FactoryCopy Anchor Link

Software Factory turns engineering requests into reviewed draft pull requests. It classifies the work, plans in a real checkout of your repository, builds in an isolated sandbox with no network and no credentials, and has an independent reviewer check the exact commit. For a request from chat, you approve the exact plan in your Inbox first. A person reviews the draft, marks it ready and merges.

▶

git clone https://github.com/hubzoid/software-factory-hub software-factory

Keep the folder name software-factory, because it is the Hub's name and its channel files use it. The README and its setup guide connect a scratch repository and GitHub, then walk through a planted bug in a labelled sample. It has no merge tool and never pushes to the default branch.

Order & Invoice DeskCopy Anchor Link

Order & Invoice Desk reads customer orders and supplier invoices from Gmail, turns each one into a record with field-level evidence from the source, and gives you reports without an ERP. Anything its rules do not decide comes back as a question for a person. Connect ERPNext when you want master-data checks and reviewed drafts.

▶

git clone https://github.com/hubzoid/order-desk-hub order-desk

Gmail uses an OAuth client you own. The README's setup guide covers the Gmail connection, a bounded history import and the four reports. A labelled sample with a fictional distributor lets you try it before you connect a mailbox.

Customer DeskCopy Anchor Link

Customer Desk reads each customer request in your helpdesk, finds the answer in your approved knowledge, the ticket's conversation and resolved answers, and prepares a reply your team reviews and sends. It works with Zoho Desk or Freshdesk. A read-only ERPNext connection lets it answer order, invoice, statement, price and delivery questions from your own records.

▶

git clone https://github.com/hubzoid/customer-desk-hub customer-desk

Keep the folder name lowercase. The desk never sends, closes or assigns a ticket, and its first runs are dry runs that record what it would write. A sample of twenty requests to a fictional distributor shows each case before you connect a helpdesk.

Engineering DeskCopy Anchor Link

Engineering Desk reviews pull requests against your team's rules and the repository's own rules, answers questions about your code in chat, watches dependencies for security problems and writes a weekly digest. Each repository you list has three switches, Reviews, Security and Reports, all off until you turn them on. Reviews start in preview, so nothing is posted to GitHub until you allow it. On a pull request, people steer it with slash commands such as /hubzoid review and /hubzoid pause.

▶

git clone https://github.com/hubzoid/engineering-desk-hub engineering-desk

Start with its fictional sample of five pull requests, which needs no GitHub token. Its README shows the setup and a prompt to paste into Claude Code or Codex. See also the Engineering Desk page.

Set one upCopy Anchor Link

Each ready-to-use Hub is its own project and is updated in its own repository, separately from Hubzoid.

Moving from a bundled templateCopy Anchor Link

Earlier releases bundled templates in the package and kept six role Hubs in the repository. They are gone now. hubzoid init writes the starter, and complete agents are the ready-to-use Hubs above.

Hubs you already made from a template keep working. init copied the files into your Hub folder, and upgrading Hubzoid never deletes, regenerates or updates them.

Scripts that pass --template stop. hubzoid init <name> --template <template> exits with code 2, says where that template went and creates nothing:

hubzoid init my-hub --template operations

Hubzoid no longer bundles templates. The operations sample was retired. `hubzoid init` writes a smaller starter for the same shop.
Nothing was created. Run `hubzoid init my-hub` for the starter.
The 2.0.1 template files are at https://github.com/hubzoid/hubzoid/tree/v2.0.1/hubzoid/templates/operations

Remove the flag to get the starter, or clone a ready-to-use Hub instead.

To start a new Hub from a retired template anyway, copy its folder from that release, including hidden files such as connectors/.mcp.json, then add your own .env with MODEL= and a random BRIDGE_API_KEYS=, for example from openssl rand -hex 32. This gets you the files only. It does not downgrade Hubzoid. Do not run hubzoid init --force on an existing Hub for this, because it overwrites the starter's files in that folder.

Repository templatesCopy Anchor Link

The six role Hubs (morning-briefing, accounts-desk, supplier-slip-check, stock-drift-watch, company-qna and it-ops-digest) were in the repository's templates/ folder. That folder is not in the current release. The files stay in the last release that had them (opens in a new tab), each with its own README and .env.example, and you can copy one the same way.

WatchtowerCopy Anchor Link

Watchtower, the workflow sample with a scheduled metrics check and a report people ran from chat, was retired. Its files stay in the last release that bundled it (opens in a new tab). To write your own workflow, run hubzoid new workflow <name> my-hub, which scaffolds workflows/<name>/main.py with a runnable example. See code workflows.

Next stepsCopy Anchor Link