One brain for your internal agents.
Build agents around your knowledge and your way of working. Start on your laptop. Bring them to your team.
Documentation · Quickstart · Website · Contribute
Hubzoid turns a folder of your knowledge, rules and tools into an agent you can use yourself and share with your team. Ask it questions in chat, run repeatable workflows, or connect your own assistant through MCP. The rules live in files you can read, edit and version.
Start in two minutes
You need Python 3.11 or 3.12, and Claude Code or Codex signed in on this machine (or a model API key).
python3.12 -m venv .venv
source .venv/bin/activate
pip install hubzoid
hubzoid init my-hub
hubzoid run my-hub
The web app opens at http://127.0.0.1:3080. Ask:
A customer wants a refund 40 days after delivery. What can we offer?
my-hub is a small starter for Kestrel & Oak, a fictional shop. It has every
folder Hubzoid reads, three house rules in knowledge/house-rules.md, and a
check in evals/. The assistant answers from the rules and names the file.
init uses the Claude Code or Codex you are signed in to. Without one, it offers
to save a model API key in the hub's private .env. Subscription limits or
provider charges apply. Choose a runtime
Make it yours
- Open
my-hub/knowledge/house-rules.mdand change the refund window from 30 days to 45. Or ask Claude Code or Codex to make the change and show you the diff. - Stop
hubzoid runand start it again. - Ask the same question. The answer now follows your rule.
Then replace the sample with your own material: your rules and notes in
knowledge/, your job for the assistant in AGENTS.md, your checks in
evals/. Only what is in the files is shared. A correction in chat is not saved
on its own. Authoring a hub
Prefer to set up with Claude Code or Codex?
Paste this into your coding assistant:
Help me set up a Hubzoid agent using the quickstart:
https://github.com/hubzoid/hubzoid/blob/main/docs/quickstart.md
Use a new folder and a Python 3.11 or 3.12 virtual environment.
Help me choose an available runtime without pasting secrets into chat.
Run the starter and show me one answer from its house rules.
Then help me turn it into an agent for one task, using material I choose.
Show me each file change before you make it.
Your coding assistant helps you write the hub. Its conversation with you is not saved into the hub.
Use a ready-to-use hub
Complete agents built on Hubzoid, each in its own repo. Clone one and follow its README.
| Hub | What it does | You need |
|---|---|---|
| Software Factory | Turns issues into reviewed draft pull requests, with people on the judgment calls | Docker, a GitHub repo, Claude Code or Codex |
| Order & Invoice Desk | Organizes orders and invoices from your inbox, every line tied to its source | An inbox, Claude Code or Codex. An ERP is optional |
| Customer Desk | Drafts customer replies from your knowledge and systems. A person approves each one | A helpdesk, Claude Code or Codex. A labelled sample is included |
| GitZoid | Pull request reviews and answers about your code | Claude Code or Codex. A GitHub token for your own repos |
git clone https://github.com/hubzoid/software-factory-hub software-factory
Each hub's README has a setup prompt for Claude Code or Codex, too.
One hub, three ways to use it
| You want to | Use |
|---|---|
| Ask about your work and get a useful answer | Chat, with your hub's knowledge and permitted tools |
| Repeat a report or check, with saved inputs and results | Workflows, on demand or on a schedule. Reports and sharing |
| Bring the same capabilities into your own assistant | MCP, with your own access. Connect your assistant |
For Claude Code, paste the connection command hubzoid run prints, then open
/mcp in Claude Code and approve the connection.
Share with your team
Local mode is private to your machine. To share, turn on sign-in and set the
public address in my-hub/.env:
HUBZOID_AUTH=true
HUBZOID_PUBLIC_URL=https://hub.example.com
Then create the first administrator and start the hub:
hubzoid admin create you@example.com my-hub --owner
hubzoid run my-hub
Open the one-time sign-in link it prints, set a password, and add teammates in Settings → People & access. Give each person the agents and capabilities they need. Shared knowledge does not mean shared credentials or access to another person's private results.
For a public deployment, use HTTPS and persistent storage. Team setup · Deployment · Backup and restore
Go further
| Next step | Guide |
|---|---|
| Add knowledge, skills, tools or specialist agents | Authoring a hub |
| Connect business systems | MCP connectors |
| Write repeatable work | Python workflows, Markdown tasks |
| Check answer quality and inspect runs | Evals, observability |
| Put the chat inside your own app | Embedding the chat |
| Use Slack or other channels | Slack, other channels |
| Keep answering when a Claude login hits its limit | Claude failover |
| Run on Windows, with uv, or from source | Quickstart |
All guides · Website documentation · Release notes · Upgrading
The chat and its Settings come with pip install hubzoid: no separate UI or
Node install. Hubzoid 2 no longer includes Open WebUI. Deployments that need it
stay on 1.x (pip install "hubzoid<2"). Python 3.12 workflows need SQLite 3.42
or later, or PostgreSQL. hubzoid doctor my-hub checks this.
Hubzoid is Apache-2.0, including team controls. Dependencies and brand assets keep their own terms. Licensing. To contribute, start with the contributing guide. Need help with your company's agents? Build with us uses the same open-source product.
Metadata
Release files for hubzoid 2.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hubzoid-2.0.3.tar.gz | 5.4 MB | With provenance | Details for hubzoid-2.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hubzoid-2.0.3-py3-none-any.whl | Python 3 | none | any | Details for hubzoid-2.0.3-py3-none-any.whl |
Total release size: 10.3 MB
Release files / hubzoid-2.0.3.tar.gz
| Download URL | hubzoid-2.0.3.tar.gz |
|---|---|
| Size | 5.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26112bde352598e68ea4abebd9cf952bf3880eb9de2788b278a5256baa3d3446
|
|
BLAKE2b-256 checksum How to use checksums |
15d576e255956fadb461f2a49261bd1380db38b40744a9cdc470e6f19fe2b484
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / hubzoid-2.0.3-py3-none-any.whl
| Download URL | hubzoid-2.0.3-py3-none-any.whl |
|---|---|
| Size | 4.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
509616e356f85734aea601e190931fe7d03ba583e90cd382614098bf226649f0
|
|
BLAKE2b-256 checksum How to use checksums |
3ba2d7e7475ac72be5a493e6d735b170ef2a7101e230aae112eec083ca78f3b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for hubzoid 2.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for hubzoid-2.0.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.