hubzoid 2.0.7

One brain for your internal agents.

Provide context once. Reuse it across workflows, chat, and the AI tools your team already uses.

Watch the video · Quick start · Documentation · Ready-to-use hubs · Website · Discussions

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 the AI assistant you already use. The rules live in files you can read, edit and version.

Why Hubzoid

• Your rules live in files you own. Knowledge, skills and agent instructions are Markdown in a folder. Read them, edit them, version them in Git. Authoring a hub
• One hub, three ways to use it. Ask in chat, run repeatable workflows on demand or on a schedule, or bring the same knowledge and tools into Claude Code, ChatGPT or Codex over MCP. Connect your assistant
• Runs on the login you already have. Claude Code or Codex signed in on your machine is enough. A model API key works too. Choose a runtime
• Built for a team. Sign-in, access per person and per agent, approvals before consequential actions, and a record of every run. Team setup
• Open source and yours to host. Apache-2.0, including team controls. Run it on your laptop, then on a server you control. Deploying

Quick start

You need Python 3.11 or 3.12, and Claude Code or Codex signed in on this machine. No API key.

Paste this into Claude Code or Codex:

Set up Hubzoid for me using the quickstart:
https://github.com/hubzoid/hubzoid/blob/main/docs/quickstart.md
Run the starter, show me one answer, then help me make it mine.

The quickstart tells your assistant to use a virtual environment, keep secrets out of chat, and show you each file change before making it.

Or by hand:

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?

The assistant answers from knowledge/house-rules.md and names the file. That is the whole loop: a rule in a file, an answer that follows it, and a source you can check.

my-hub is a small starter for Kestrel & Oak, a fictional shop. 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. Windows, uv or from source

Make it yours

The starter is a folder. Every folder Hubzoid reads is there, with sample content only where it teaches the loop.

my-hub/
├── AGENTS.md          the assistant's job: who it is, what it answers from
├── knowledge/         what it knows: rules, policies, notes, one Markdown file each
│   └── house-rules.md
├── skills/            step-by-step procedures it follows when a task matches
├── agents/            specialist agents it can hand work to
├── tools_local/       your own Python tools
├── connectors/        MCP connections to other systems
├── workflows/         repeatable work in Python
├── schedule/          tasks that run on a schedule, one Markdown file each
├── evals/             checks that answers stay right
│   └── refund-window.md
└── raw_data/          files the assistant can search and read

Change one rule and watch the answer follow it:

1. Open my-hub/knowledge/house-rules.md and change the refund window from 30 days to 45. Or ask Claude Code or Codex to make the change and show you the diff.
2. Stop hubzoid run and start it again.
3. Ask the same question. The answer now follows your rule. hubzoid eval run my-hub checks it stays that way.

Then replace the sample with your own material: your rules and notes in knowledge/, the assistant's job 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, and your coding assistant's conversation with you is not saved into the hub. Authoring a hub

Ready-to-use hubs

Complete agents built on Hubzoid, each in its own repository. Each one starts with a labelled sample you can run before connecting anything of your own, and its README says what it needs.

Use it three ways

For Claude Code, paste the connection command hubzoid run prints, open /mcp in Claude Code and approve the connection.

Host it for your team

Local mode is private to your machine. To share a hub, turn on sign-in and set its public address in the hub's .env:

HUBZOID_AUTH=true
HUBZOID_PUBLIC_URL=https://hub.example.com

Create the first administrator, then 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. Each person gets the agents and capabilities they need. Shared knowledge does not mean shared credentials or access to another person's private results.

Every way of hosting works the same way: one image built from the hub's Git repository, one durable folder at /data, sign-in on, one public address, and weekly verified backups.

hubzoid deploy verify https://your-address checks a deployment from outside. Deployment overview · Backup and restore · Upgrading

Go further

All guides · Website documentation · Release notes

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.

Help, contributing and license

Questions and ideas go to GitHub Discussions. Bugs go to issues. To contribute, start with the contributing guide.

Hubzoid is Apache-2.0, including team controls. Dependencies and brand assets keep their own terms. Licensing

Need help with your company's agents? Build with us uses the same open-source product.