Brain
Choose how you want to keep and use information.
Memos are your drafts and personal text. Their Memory switch saves a separate copy for AI recall. Memos are never automatically added to Vault. Previously imported Vault copies remain available independently.
Web research
Search through your self-hosted service. Search terms go to search engines; visited websites receive page requests. Results are not automatically saved to Memory or Vault.
Your private memory
Memories are isolated by account and used only to make your future conversations more useful.
Other family members and the administrator cannot browse these memories through the hub.
Memory extraction and embeddings use your private Ollama connection.
Memory spaces
Create any category you need, such as Client, Project, Family, Work, Research, or Health.
Memos
Save private text. Switch Memory on to save a copy for AI recall; switch it off to remove that copy. To refresh an edited memo’s Memory copy, turn it off and on. Vault notes are separate.
No memos yet
Keep drafts, snippets, and reference information here until you decide to use them as memory.
Knowledge Vault
Keep lasting notes about projects, people, decisions and reference material. Link related notes with [[double brackets]], search them later, and review earlier versions. Memos are kept separately and are not imported automatically.
Every item is stored under /vault. SQLite and Qdrant are rebuildable search indexes.
Agents receive read, propose, or direct-write permission per identity and memory space.
Your Knowledge Vault is empty
Create a project, person, decision, meeting, reference, or daily note. Memos are separate. Previously imported copies remain here independently.
BuildX
Your projects, browser workspace and AI building team.
Describe your first task
Permission needed
Review this action before BuildX proceeds.
Open the running development preview. Test results and deployment status are reported separately.
External development clients
Give a client access to this project’s tasks and progress. The key cannot approve changes or deploy.
Review and publish
Review the Changes and Checks tabs, then accept the task into your project. Release creates a version in Gitea; deployment is a separate confirmed step below.
- Review the proposed changes and completed checks.
- Accept changes to update the project workspace and linked Gitea branch.
- Create a release, then prepare and confirm Development or Production deployment below.
Deploy an environment
Deploy tested, accepted source from Gitea, verify its containers, then request its CottonCaddy route. Administrator approval remains in CottonCaddy.
Acceptance and publishing always require your confirmation, including in Auto-Approve mode. Undo restores changed files; deployment rollback does not restore databases.
Earlier file proposals for projects without Gitea
Existing folder projects and file proposals remain available here. Use project tasks for connected Gitea repositories.
Code workspace
Give the Hub access only to folders mounted under /workspace. AI edits are proposals and are written only after your approval.
No file is changed until you approve this proposal.
Account Settings
Preferences & security
Connections & development
Admin Settings
Workspace administration
Container updates
Checks run hourly for this Hub's containers, including future services added to its stack. Updates stay under your control.
Open PortainerLoading update status…
Registry checks follow the displayed tag. A different digest is a candidate to review. Locally built containers follow reviewed Hub releases; unavailable information is not a confirmation that a container is current.Resource Monitor
Live resource readings and confirmed model activity. This page observes; it does not unload or restart models.
Waiting for measurements...
Model activity
Confirmed loads and unloads are recorded separately from requests. A decrease in VRAM is not proof of eviction or an out-of-memory failure. Events start when this Hub process starts; the last 512 are kept in memory.
System Wide AI Models
Providers supply models. A shared hub is a saved selection of those models plus routing settings. Configure each hub once here; sharing it gives users that same selection automatically, even without separate model access.
Automatic presets have no saved selection yet. Choose their models before sharing. Provider credentials remain on the server. Memory, Vault, Memos and conversations are not included; Memory spaces use their own Read only or Can add memories sharing.
Support
Help & troubleshooting
Account
Manage your profile, memory preference, and password.
Passkeys
Sign in and unlock protected notes with Windows Hello, Touch ID, your phone, or a security key. Passkeys are bound to aihub.mini.bebz.net.
Authenticator app (2FA)
Checking security settings…
When enabled, every new sign-in asks for an authenticator code, including sign-ins with a passkey. Keep your recovery codes in a safe place.
Scan this QR code in your authenticator app. If you cannot scan it, enter the key shown below.
Manual key:
Save your recovery codes now
These codes are shown only once. Each code can be used once if you lose your authenticator.
Users
Create accounts, manage roles and choose Model access for each user. New accounts need a shared model before they can chat. You cannot demote or disable your own account. At least one enabled admin must remain.
Accounts
Model providers
Add local and cloud AI services without editing code. Credentials remain encrypted in your Unraid appdata.
Private chats may use only enabled connections marked Private. Standard cloud connections are removed from the eligible list before a prompt is sent.
Add a private connection to enable sensitive chats.
Your connections
Test, edit, disable, or remove a provider at any time.
Connect your first model provider
Start with your existing Ollama container. The Docker endpoint and qwen3.5:9b model are already filled in.
Private auto router
Select private-hub-auto in chat. A tiny CPU model classifies each new turn; the Hub enforces local-only connections, hardware limits and capability checks. Replies are never interrupted to change models.
Loading your routing preferences…
Automatic prefers qwen3.5:9b for everyday/vision and qwen2.5-coder:7b for coding when available, but may keep a suitable loaded model. Preferences never override privacy, capability or size checks. CPU-policy models have a conservative 12 GiB weight limit while Colibri uses 88 GB of RAM; these are guardrails, not measured memory availability.
Colibri: add a private Colibri connection above, use http://YOUR-UNRAID-IP:38765/v1 and model glm-5.2-colibri, then press Test. Use its API key if configured. Do not reinstall or download the existing 407 GB model.
Quick add
Email and archive accounts
Connect Gmail, Google Workspace, Microsoft 365, Outlook.com, other IMAP servers, and your MailStore Windows VM. Every server and account is configured here.
New email accounts default to read-only. Sending must be enabled explicitly per account. MailStore is always treated as a private, read-only archive connection.
Client secrets, access tokens, refresh tokens, passwords, and app passwords are encrypted in local appdata.
Sign in with Google or Microsoft
After the administrator configures each provider once, adding another account is just a secure provider login popup.
- Select a providerThe Hub checks whether its shared provider profile is ready.
- Sign inGoogle or Microsoft opens its normal account and consent popup.
- FinishedThe Hub encrypts the tokens locally and tests the connection.
Your email sources
OAuth accounts require a client ID, secret, and callback URL configured in the account settings.
Add your first email source
Choose OAuth for Google or Microsoft, IMAP for another provider, or MailStore for your separate Windows VM.
Quick add
Calendars
Discover calendars from connected Google and Microsoft accounts, then choose which calendars the hub may use and whether each one is read-only.
A calendar marked read-only can be searched for availability and events, but create, update, and delete operations are rejected for it.
Connect and authorize a Google or Microsoft account first, then discover its calendars here.
Discovered calendars
Provider-side read-only calendars cannot be made writable here.
No calendars discovered yet
Enable calendar access on a Google or Microsoft account, complete OAuth, and select Discover from accounts.
MCP servers
Private Streamable HTTP servers such as Home Assistant. Tokens are encrypted locally; no server is reachable from the internet through the Hub.
Discover a server’s tools, approve only the ones the Hub may expose, then assign an individual subset to each agent or chat.
In Unraid Management Agent → AI Agent Access (MCP), Generate a Connect Secret and Apply. Paste the complete http://YOUR-UNRAID-IP:8043/mcp/CONNECT-SECRET URL here and choose No additional header. Alternatively paste http://YOUR-UNRAID-IP:8043/mcp, choose Bearer token, and enter the agent API token. Test, save, discover, then approve selected tools.
Configured servers
Action-capable tools are blocked for agents that retain “Require approval for changes”.
No MCP servers yet
Add Home Assistant or another private Streamable HTTP MCP server.
API and MCP Access
Give external apps model access, and separately choose which MCP tools an agent may use.
Use your client key for authentication. Both model APIs use the same Hub model access permissions.
Agents see only assigned model routes, connections, memory spaces, email sources, calendars, and MCP tools.
/mcp using the agent API key as a Bearer token.
Open Interpreter, Open WebUI or another AI client
This gives the external app a scoped Hub API key for model requests. You do not need to add that app under AI connections: AI connections are providers the Hub calls, such as Ollama and Colibri.
Permission edits apply to new requests using this identity’s pah_agent_ key. General API keys do not inherit these permissions. After editing access, refresh the external app’s model catalog; in ChangeDetection, choose Load available models. An existing selected model is not automatically replaced.
For Open Interpreter, choose Provider: API, Base URL: Custom endpoint, Use Chat Completions: On, and model ID private-hub-auto.
- Create and enable a client identitySelect Add client or agent; name it Open Interpreter; allow the
private-hub-autoroute and at least one enabled local model connection. Leave MCP access empty if you only need model replies. Save and copy the key shown once. - Set up the external appBase URL:
https://aihub.mini.bebz.net/v1. API key: the new agent key. Model ID:private-hub-auto. Open Interpreter must use Chat Completions; the Hub does not have a Responses API endpoint. - Check access, then test a promptRequest
/v1/modelswith the same key and check thatprivate-hub-autoappears; then ask the app a short question. A 401 means the key or its enabled status is wrong; a 403 means the saved agent does not allow the requested model route; confirm both the allowed route and the local model connection are checked.
Allow an agent to use MCP tools
The Hub’s MCP endpoint is separate from its model API. Assigning MCP permissions does not automatically enable them in a client app; configure the MCP server separately in clients that support it.
- Add and test the serverUnder MCP servers, enter its exact URL. Discover tools, then approve only the ones the Hub may expose.
- Assign tools to an enabled agentEdit the identity above, choose that MCP server and the subset of approved tools it may call. Keep approval required for changes unless you deliberately grant write access.
- Configure the client’s MCP connectionIf the client supports Streamable HTTP MCP, set its MCP URL to
https://aihub.mini.bebz.net/mcpand use that same agent key as a Bearer token. The model Base URL remainshttps://aihub.mini.bebz.net/v1.
No agents configured
Add OpenClaw or Hermes when you are ready.
Recent agent activity
Successful model and MCP tool use is recorded without prompts or responses.
Diagnostics
Content-free operational events help troubleshoot the hub without recording prompts, responses, memories, credentials, email, or calendar content.
Logs contain timestamps, components, actions, severity, usernames, and reference IDs only. Up to 5,000 recent events are retained.
Detailed runtime output remains available through Portainer or docker logs private-ai-hub.
Recent events
Administrators see system metadata; members see only their own events.
Open this section to load diagnostics.
Routing and compatible APIs
Create virtual model names that choose a connection and model while enforcing private-only rules.
Connection access by account
Administrators can see every model, email/calendar, and MCP connection. Check the accounts where each connection should appear. This does not share conversations, memory, Vault items, Memos, attachments, or Code workspaces.
Open Routing & API to load connection assignments.
A private conversation cannot use a cloud-standard connection, even when an alias targets one.
/v1 for OpenAI clients and the standard /api routes for Ollama clients.
Hubs and model aliases
Changes apply immediately without rebuilding the container.
Route inspector
Preview exactly which endpoint, model, loaded state, and device policy the Hub would choose.
Legacy unrestricted client key
Retained for compatibility and bound to the personal account. Use a scoped key from Agent and Access for OpenClaw, Hermes, and new clients.
Loading…