What is Labtagon AI OS
Labtagon AI OS is the platform through which an organisation uses AI. People chat with models in the console, connect the AI tools they already use, such as Claude or Claude Code, and hand work to agents. AI OS decides what each of them may use, can hold risky actions until a person approves them, and records what happened.
Models and AI tools change; the tools, rules and history an organisation builds up stay in AI OS.
What it brings together
Section titled “What it brings together”- Models. Every model call goes through AI OS: from the chat, from agents and from people’s own tools with an API key. Administrators choose which providers and models the organisation offers.
- Tools. Tool servers (MCP servers) give AI access to systems such as a ticket tracker or a wiki. AI OS hosts them and offers all of them at one address.
- Clients. An AI tool from outside, such as Claude, Claude Code, Codex or Cursor, connects to that one address and signs in with your company account. See Clients and the gateway.
- Profiles. A profile says what a client or an agent may use. See Profiles.
- Agents. Agents of AI OS work on their own, by hand, on a schedule or when a webhook calls them. See Agents and jobs.
- Memory. Memory spaces keep what AI learned in earlier conversations. See Memory spaces.
- Tasks. What AI or a colleague asks of you, such as an approval, waits in your inbox. See Tasks and approvals.
- Files and shares. What AI makes stays with you as a file or a shared page. See Files and shares.
The four areas of the console
Section titled “The four areas of the console”The switcher at the top of the sidebar opens the areas you have:
| Area | What is there |
|---|---|
| Chat | Your chats and workspaces, the inbox, tasks and files |
| Studio | Your agents, and the servers, skills and knowledge they use |
| Insights | Spend, use, analyses and logs |
| Administration | Organisations, people, policies, models and the platform (administrators only) |
Your own Settings (appearance, language, notifications, your account) are at the foot of the sidebar. The console is in English and in German (in an informal and a formal form).
How it keeps control
Section titled “How it keeps control”- Every tool call goes through the gateway of AI OS. It checks the call, can hold it for your approval and records it.
- Keys and sign-ins for other services are not handed to the AI. AI OS fills them in only on the way out, and only for the hosts a tool server is allowed to reach.
- Administrators decide with policies who gets which tool servers, skills, capabilities and models.
- AI OS is installed with a Helm chart on a Kubernetes cluster. Where it runs is the choice of whoever operates it.
Security and privacy explains this in detail.
Where to go next
Section titled “Where to go next”- New here: First steps.
- Rolling AI out in your organisation: Introducing AI in your organisation.