Workspaces (Rooms)
Workspaces (Rooms) in Imperal Cloud are dedicated operating environments — like Thoughts and Ops — where human and agent collaborate with focused state.
In Imperal Cloud, a Workspace (also known as a Room) is not just an ordinary webpage or dashboard tab. It is a dedicated operational space where you and Webbee 🐝 work together on a specific domain of your cloud, with focused context, persistent state, and specialized tools.
You reach every workspace directly from the top navigation dropdown: Workspaces: in the Imperal Panel, and each room lives under a canonical route:
https://panel.imperal.io/workspace/thoughts— the unified conversation workspace.https://panel.imperal.io/workspace/ops— the cloud operational center for deployments, runs, and telemetry.
The Philosophy: Why Workspaces?
Traditional cloud dashboards present long, fragmented lists of pages: "Settings", "Analytics", "Logs", "Chats". This structure scatters context and forces the user to jump back and forth between disconnected tabs.
In an AI Cloud OS powered by ICNLI, we treat work as collaborative environments rather than passive pages:
-
A Place You Work In, Not a Page You Visit: When you enter a Room, Webbee aligns her attention with that specific domain. In Thoughts, her focus is on your dialog history, past decisions, and reasoning threads. In Ops, her focus is on system health, active background tasks, and incident resolution.
-
Decoupled Extensions vs. Visible Rooms: Under the hood, capabilities are powered by extensions (such as the
thoughtsextension or infrastructure monitoring extensions). But to you, they manifest as cohesive, ambient workspaces. An extension provides the tools and background capabilities; the Room provides the interactive home. -
Cross-Surface Continuity: A Room isn't tied to one browser session. If you start discussing an architecture migration in the Thoughts room on your desktop, and later follow up via Telegram or Webbee Code in the terminal, Webbee recalls the exact same conversation thread from that Room.
The Core Rooms
1. Thoughts (/workspace/thoughts)
The shared conversational brain of your cloud.
While thoughts is technically packaged as a first-party platform extension, its true nature is The Thoughts Room:
- Unified Hub-Chat History: Every turn, decision, and question you have ever exchanged with Webbee across all surfaces is indexed here.
- Surface Awareness: Each message in the room is stamped with its real originating surface (terminal, panel, or API), preserving true context.
- Multi-Thread Management: You can branch conversations into dedicated topics (e.g., "Database Migration", "Billing Audit", "Kubernetes Incident"), rename them, switch the active live thread, or permanently clean up old threads.
- Tool Access for Webbee: Webbee can query her own past conversations via tools (
list_conversations,read_conversation,continue_conversation), so she can look up past decisions even when they took place weeks ago.
2. Ops (/workspace/ops)
The command and telemetry bridge.
The Ops workspace provides real-time visibility into what the AI Cloud OS is executing:
- Active Runs & Deploys: Monitor background operations, extension builds, and marketplace synchronizations as they happen.
- Failure Forensics: When a step stumbles, the Ops room highlights the root cause, execution logs, and recovery actions without hiding behind vague error codes.
- System Health: Continuous monitoring of platform workers, storage tiers, and external connectivity targets.
Room Navigation & The Workspaces Switcher
The top bar of Imperal Panel features the dedicated Workspaces: switcher:
- Breadcrumb Context: The trigger displays
Workspaces: ThoughtsorWorkspaces: Ops, making your current operational context immediately obvious. - Instant Switching: Switch between rooms with keyboard navigation or a single click without losing your background task state.
- Mobile Drawer Integration: On mobile devices, the workspace switcher seamlessly nests inside the mobile drawer, ensuring fluid navigation on phones and tablets.
Workspaces bridge human intent and agentic execution into structured, focused environments where complex cloud operations feel natural, organized, and transparent.
What we built that nobody else has
Twenty platform-and-agent surfaces with no known precedent that fall out of the first ICNLI AI Cloud OS — AI inside the kernel, cloud-modular, proactive by design.
Context channels — how Webbee remembers
How Webbee remembers — the three channels the web-kernel feeds into every LLM turn: the skeleton, ctx.cache, and the fact-ledger verbatim recall surface.