The product
One Hub. Many ways to put it to work.
Bring knowledge, skills and authorized tools together. Let your team use that foundation through chat, workflows and their existing assistants.
The Hub
Build context once. Keep making it useful.
A Hub is the shared foundation for a product, team or company. Keep instructions and knowledge understandable, maintain reusable skills, and connect the systems where authoritative data lives.
- Knowledge: terms, rules, decisions and reference material
- Skills: reusable instructions for doing a particular job
- Tools: authorized connections, scripts and MCP capabilities
- Ownership: someone responsible for keeping the foundation current
How this team works
Prepare concise briefings. Cite the source for each finding. Say when a source is missing. Ask for review before taking a consequential action.
Chat
A useful answer is only the beginning.
Teammates can ask about the business and request the next action in web chat, Slack, WhatsApp or Telegram. Bring relevant context into a familiar conversation, with access appropriate to the person and the channel.
- Use the context relevant to the question
- Bring sources into the conversation
- Keep action and review boundaries explicit
- Web
- Slack
- Telegram
Two items need a closer look before the weekly review.
- The operations handover has one unresolved exception.
- The reporting guide changed. The new definition applies next week.
Workflows
Give repeatable work a dependable home.
Define the task, connect the inputs and make the result easy to inspect. Use supported schedules and triggers for recurring work, and keep failures and review steps visible to its owner.
- Run a task on demand or through a supported trigger
- Inspect inputs, steps and outputs
- Decide what can happen automatically and what needs review
Summarize the changes and connect each finding to a source. Separate observations from proposed actions.
Connect your assistant
Keep your tools. Add the shared brain.
Connect Claude Code, Codex and Hermes to the Hub’s context and tools through MCP. Each connection has its own authorization. Shared context does not mean shared credentials or identical conversations.
- Claude Code
- Codex
- Hermes
- Claude Code
- Codex
- Hermes
Your HubShared context + toolsThe assistant can retrieve relevant shared knowledge within the connection’s scope.
assistant → Hubzoid MCP
→ reporting guide
→ relevant contextRelevant context. Authorized capabilities.
The Console
Know what ran. See what needs you.
Give builders and owners one place to inspect agents, runs and team access. Follow a result back to its work, spot failures and make responsibility visible.
Workflow runs across your agents. Select a run to inspect its result.
Access and responsibility
Control access down to the tool.
Decide who can use an agent and which tools they can call. Restricted tools are gated before execution. Agent access and tool permissions are separate decisions, and neither is made by the model.
Try the Hub
Start with one Hub on your own laptop.
Add your team’s context, then share it once it proves useful. Or ask us to build it with you.