Kontext OS

Capabilities

My Kontext is the desktop you work from — Today, Team, Build, and History. Talk is where you reach Kontext. Turn on OS Intelligence once; six platform staff come with it and you cannot fire them. Hub is the map of the account. Workspace is where you write code.

• Activate once — Turns on OS Intelligence on your Main Agent. Six platform staff come with it

• Today cockpit — Today / Team / Build / History; Daily Brief is the longer morning read

• Talk — Kontext on the Assistant rail (not a Chat tab)

• Employees — Roster (you hired) / Platform (six staff) / Activity

• Routines — Standing work. Hidden on this list when it is already assigned to someone

• Native apps — Notes, To-do, Interview, Files, Calendar, Mail

• Kontext Ecosystem first — agents look inside your account before they reach for Gmail or Slack

• Connected apps — Gmail, Slack, Stripe, calendars — after Ecosystem is on

• Hub — the map of apps, workforce, and who can act as you (not this desktop)

What is My Kontext?

My Kontext is the desktop you work from. Today, Team, Build, and History are the four rooms. Talk is where you speak to Kontext. There is no Chat tab here — Workspace Chat is for writing code on a project. Turn on OS Intelligence once. It runs on your Main Agent (the first agent server). The six platform staff come with it. You cannot fire them.

Today, Team, Build, and History

Today is the cockpit: the day’s work, things that need your OK, and the short brief. It is not the longer Daily Brief on the left rail, and it is not the standing plan. Team is people and standing work you can see at a glance. Build is making and shipping. History is what already ran. Progress and Operations still exist. They live under Settings, not as top tabs. If you are looking for “the Operations tab,” open Settings.

Staff, people you hired, and app workers

Platform staff are six roles the OS ships: Managing Director, Scheduling, Memory, Tool, Communications, and Build Manager. You cannot fire them. They run about every six hours, write reports into the knowledge vault, and park risky changes in Needs your OK. Roster is teammates you hired. They can have routines. An app worker is created when you deploy an app. It serves that app. Hub → Workforce lists it. It is not someone on the Roster, and it is not a bot that only exists while the app is open. Business digital employees email you scheduled reports. They are not the six platform staff.

The brain, memories, and how facts get in

The brain is the knowledge vault on your account — not a decorative planet. Learned facts (Talk, Notes, remember-this), staff reports, interview answers, and workflow outcomes all land there. AME routes where a save or recall goes; Mem0/Notion/Drive are optional extras. The morning brief composes cards from live signals plus those reports. Connected-app calendar/mail in the brief are live reads, not a Gmail dump. Project apps stay private until you opt in to sharing. Talk gets a bounded pack: goals, playbook peek, a few memories, latest staff clocks, channels (or unknown if the list failed), and guides when you ask how Kontext works. Missing slice = “I have not read that,” not “you have none.”

Talk vs Chat vs Messenger

Talk is where you reach Kontext. The mobile ask bar opens Talk. Voice settings on My Kontext apply here, not in Workspace. Workspace Chat writes code on the project you have open. If you asked to generate or fix an app, you want that lane. Messenger (/messages) is people — Direct and Groups, plus KTX Bot. Same assistant path as Talk, different shell. Business Omni “Messenger” is Meta, not this inbox. Forum is public threads. Helpdesk is a private ticket (**+ Create Ticket). Documentation is the product book Kontext looks up. Kontext Docs is make a document. Kontext is none of those queues. Name the door — do not say “open Help” or “open Chat.”

What My Kontext is not

It is not Kontext Business (business intelligence). AIOS is your day — Talk, the brief, six platform staff. Business is the company’s day — leads, customer inbox, Revenue, Insights. They share the Main Agent and one phone number. They are not the same product. It is not the Hub (the map of the account). It is not Workspace (where you write an app). It is not Messenger (people). Talk here is Kontext, not Workspace Chat.

Where it lives: My Universe / My Kontext dashboard, OS setup wizard, Today & brief surfaces

OS Intelligence is your business-aware assistant layer on top of Kontext OS — not for writing code (use Workspace chat for that). It connects your tools, learns your preferences, delivers daily briefs, and runs delegated personas (employees) on schedules you control.

Kontext OS (/os) is the desktop shell — dock, Start menu, multi-window apps, native AIOS windows (Notes, To-do, Interview, Files, Calendar, Mail), and OS Intelligence. Notes and To-do can be shared by @handle (Can edit or Can view); nothing is copied into the other person’s book. The menu-bar bell opens How often may Kontext interrupt you? Talk has a resting bar, a normal thread, taller, and full screen. World has no left Inspector: search and Tools float on the map, and Legend is a Desk tab. Open My Kontext: the Today canvas is Today / Team / Build / History. The left rail is Today, Daily Brief, Activity · Talk · Employees, Routines · Ecosystem, Settings. Activate OS Intelligence once; it runs on your Main Agent runtime. For the global view of apps, workforce, and who can act as you, open Hub. For writing code, open Workspace.

• Activate once — Creates the os-intelligence profile on your Main Agent runtime

• Today cockpit — Today / Team / Build / History; Daily Brief is the longer morning read

• Talk — Kontext on the Assistant rail (not a Chat tab)

• Employees — Roster (you hired) / Platform (six staff) / Activity

• Routines — Standing work on the same runtime (hidden when assigned to an employee)

• Native apps — Notes, To-do, Interview, Files, Calendar, Mail

• KESA first — 462 in-platform actions via kontext-ecosystem MCP before external Composio apps

• Composio — Gmail, Slack, Stripe, calendars — OAuth after KESA on profiles

• Hub — /hub is the map of apps, workforce, and who can act as you (not the same as this desktop)

Where it lives: My Universe / My Kontext dashboard, OS setup wizard, Today & brief surfaces

OS Intelligence is your business-aware assistant layer on top of Kontext OS — not for writing code (use Workspace chat for that). It connects your tools, learns your preferences, delivers daily briefs, and runs delegated personas (employees) on schedules you control.

Core experience

• Desktop — App icons, layouts, and backgrounds; open multiple modules without losing place
• Dock — Quick launch to My Kontext, native apps (Notes, To-do, Interview, Files, Calendar, Mail), Browser, Marketplace, University, Community, Network, Forum, Kontext Business, and related surfaces
• Start menu / My Kontext — Categorized launcher (Workspace, discovery & learning, community, tools, account)
• Multi-window — Run several apps side by side; project-dependent apps (Workspace, Agent Studio, App Studio, Refine, Kontext Business, etc.) show a project selector in the window chrome when a project is required
• Widgets — Optional desktop widgets (for example University, Marketplace, Network, Communities, Forum, Kontext Business, Workspace shortcuts)
• Command layer — Natural-language intents (e.g. create app, create agent, open business solution) routed to the right capability; pairs with the floating command UI where enabled

OS-native creation flows

High-impact flows can run entirely inside OS windows (without opening the Workspace), including guided create app and create agent pipelines: server pair selection, streaming generation, preview, and handoff to Live Preview or Agent Studio as appropriate.

Kontext OS Intelligence (expanded)

Where it lives: My Universe / My Kontext dashboard, OS setup wizard, Today & brief surfaces

OS Intelligence is your business-aware assistant layer on top of Kontext OS — not for writing code (use Workspace chat for that). It connects your tools, learns your preferences, delivers daily briefs, and runs delegated personas (employees) on schedules you control.

Core capabilities

Daily Brief

Employees (OS teammates)

Not the same as: Kontext Business Digital employees (/business/employees) — those deliver owner operational reports on a schedule; OS employees serve your creator/operator cockpit.

Routines (OS)

Branding: Also marketed as Kontext AIOS (July 2026). Same product as OS Intelligence — journeys may still say “OS Intelligence” where that label appears in UI.

Kontext AIOS highlights

• Six platform staff (immovable) — Managing Director, Scheduling Manager, Memory Manager, Tool Manager, Communications Manager, Build Manager
• Today cockpit — Today / Team / Build / History (not Progress / Operations as top tabs)
• Talk — Kontext on the Assistant rail; there is no Chat tab
• Native AIOS apps — Notes, To-do, Interview, Files, Calendar, Mail
• Goal Spine — structured owner goals drive brief ranking and manager work
• AME v2 — on-chain memory source of truth; optional Mem0 / Notion / Documents
• Needs your OK — plain-language approvals; autonomy dials

Command layer & OS-native flows (summary)

User journeys

KO-01. Open Kontext OS after login

Path: /os · post-login landing · dock My Kontext

You do:

1. Sign in with the Kontext chooser (Google, Microsoft, Apple, passkey, Kontext ID, or recovery). Internet Identity appears only if the platform still offers it.
2. If your account lands on marketing chrome, open Kontext OS from the module switcher or follow the post-login dock.
3. Wait for the OS loader to finish — desktop, dock, and default University widget appear.
4. Confirm the URL is /os (or OS embed route) before opening project work.
5. Glance at My Kontext in the dock — that is your Today / intelligence hub.
6. Hard-refresh once after a deploy if widgets look stale (PWA cache).

Result: You are in the Kontext OS shell with desktop, dock, and widgets — not a standalone module page.

KO-02. Reach OS from module switcher

Path: Global module switcher → Kontext OS

You do:

1. From Workspace, Business, or any module, open the global module switcher (top bar).
2. Choose Kontext OS.
3. Confirm OS windows restore or the desktop loads without losing your signed-in session.
4. Use the switcher again to return to the module you came from — OS stays open in background windows if you had any.
5. Bookmark /os for a direct return when the switcher is hidden on mobile.

Result: OS is reachable from every module without logging out or cold-starting the PWA.

KO-03. Launch apps from the dock

Path: Kontext OS dock → app icon

You do:

1. Open /os and locate the always-visible dock (My Kontext, Browser, Marketplace, University, Community, Network, Forum, Kontext Business, … per your role).
2. Click an dock icon — the app opens in an OS window or navigates to its route.
3. For chat-based dock apps, confirm the correct project is selected in the window title bar.
4. Open a second dock app — both windows stay in the OS shell.
5. Hover dock icons for tooltips when labels are icon-only on narrow screens.

Result: Dock apps launch in OS context with correct role visibility — no hunting through URLs.

KO-04. Browse Start menu / app catalog

Path: Start menu · Applications folder in My Kontext

You do:

1. Open the Start menu or Applications folder inside My Kontext.
2. Scan categories: Workspace, Discovery & Learning, Community, Tools, Account.
3. Pick an app — Workspace tabs, Agent Studio, Launchpad, Messages, Profile, etc.
4. Pin frequently used apps to the start menu if the UI exposes pin controls.
5. Notice admin-only or team-only apps hidden unless your role qualifies.

Result: Full app catalog is categorized like a desktop Start menu — not every app sits on the dock.

KO-05. Open an app from desktop icons

Path: OS desktop grid → app shortcut

You do:

1. On the OS desktop, double-click or click a shortcut (My Kontext, Workspace, Agent Studio, App Studio, …).
2. If the icon is dimmed, OS Intelligence or a server pair may be required first (KO-28, OS-01).
3. Window opens with OS chrome — title bar, minimize, project selector when applicable.
4. Drag icons only if icon edit mode is enabled in preferences (KO-09).

Result: Desktop shortcuts mirror dock/catalog apps for muscle-memory launching.

KO-06. Run two OS windows side by side

Path: Dock or desktop → open two apps · window chrome

You do:

1. Launch first app from dock or desktop (e.g. My Kontext).
2. Launch second app without closing the first (e.g. Workspace or Browser).
3. Use window minimize / restore on each OS window title bar.
4. Click the desktop between windows to focus the right context before typing.
5. Avoid editing the same project in two Workspace windows without checking the project picker on each.

Result: Multiple OS windows run concurrently — OS is a desktop, not a single-page app.

KO-07. Switch project in a project-scoped window

Path: OS window title bar → project selector dropdown

You do:

1. Open a project-dependent app: Workspace, Chat, Agents, Deploy, Agent Studio, App Studio, Refine, Kontext Business, etc.
2. Click the project selector in the window title bar.
3. Pick another project or Create project.
4. Wait for tab content to reload against the new project id.
5. Confirm canister/hosting hints if you plan to deploy from this window.

Result: Project-scoped OS windows target one project at a time — wrong picker causes wrong deploys.

KO-08. Change desktop background

Path: Start menu → background · personalization

You do:

1. Open Start menu personalization or background controls (preset grid).
2. Preview built-in background presets.
3. Apply a preset — desktop wallpaper updates immediately.
4. Re-open OS later to confirm the choice persisted on your user canister preferences.

Result: Desktop background reflects your choice across sessions.

KO-09. Customize dock and desktop icons

Path: My Kontext → settings → Icon preferences (or OS access panel)

You do:

1. Open Icon preferences from OS settings / My Kontext gear.
2. Toggle which apps appear on desktop, dock, or Start menu pins (within role limits).
3. Reorder dock slots if drag-and-drop is enabled.
4. Save — layout persists per account.
5. Reset to defaults if the grid becomes unusable.

Result: Your OS chrome shows only the apps you want on desktop and dock — role caps still apply.

KO-10. Add a desktop widget

Path: OS desktop → Add widget · widget dialog

You do:

1. Right-click desktop or use Add widget control.
2. Pick a module widget: University, Marketplace, Network, Communities, Forum, Kontext Business, Workspace, Automations, …
3. Place the widget on the grid — default new users get University / Kontext 101.
4. Resize within widget frame limits if handles are shown.
5. Open widget links — they deep-link into the module inside OS or a new window.

Result: Module previews live on the desktop without opening full apps.

KO-11. Configure a universal multi-tab widget

Path: Widget → configure → Universal tabs

You do:

1. Add or select a Universal widget that combines multiple modules.
2. Open widget Configure.
3. Enable tabs for each module you want in one frame (e.g. Network + Forum preview).
4. Save — switch tabs on the desktop without new windows.

Result: One desktop tile rotates between module previews.

KO-12. Remove or rearrange widgets

Path: Desktop widget → configure · remove

You do:

1. Enter widget edit mode or open widget menu (⋯).
2. Drag to reposition on the snap grid.
3. Remove widgets you no longer need — University can be removed but is the default onboarding widget.
4. Confirm layout saves after refresh.

Result: Desktop widget layout matches how you work — clutter-free.

KO-13. Open My Kontext (Today hub)

Path: Dock My Kontext · desktop My Kontext icon

You do:

1. Click My Kontext on the dock or desktop.
2. The left rail groups Today (Today, Daily Brief, Activity), Assistant (Talk), Your team (Employees, Routines), and Your stuff (Ecosystem, Settings).
3. Open Today — the main canvas is Today / Team / Build / History, not a stack of Daily Brief + Employees + Chat tabs.
4. If activation banner shows, complete Activate OS Intelligence (OS-01) before the team and brief unlock.

Result: My Kontext is the AIOS control panel. Talk is where you reach Kontext on the rail — not a Chat tab. Routines replaced the old Automations tab name.

KO-14. Open Kontext Browser

Path: Dock → Browser · OS Browser app

You do:

1. Click Browser on the dock.
2. Use in-OS browser for live previews, external docs, or OAuth flows that open in-window.
3. Navigate via address bar or home shortcuts.
4. Open live preview URLs from App Studio handoffs without leaving OS.

Result: Built-in browser keeps external browsing inside OS windows when possible.

KO-15. Read mail in OS Mail

Path: OS app catalog → Mail · kontext-mail window

You do:

1. Open Mail from Start menu, dock, or Today’s app dock (with Notes, To-do, Interview, Files, Calendar).
2. Connect mail source via Composio or native connector if prompted.
3. Read threads in the OS Mail window — not Kontext Business inbox (that is /business/inbox).
4. Use Mail for owner operator email triage tied to OS Intelligence signals when configured.

Result: OS Mail is an in-shell mail surface for connected accounts — separate from Business SMS/email inbox.

KO-16. Use OS Calendar

Path: OS app catalog → Calendar

You do:

1. Open Calendar from OS apps.
2. Connect Google/Outlook or native calendar via Composio if not already linked (OS-03).
3. View upcoming events that feed Daily Brief calendar sections (OS-06).
4. Jump to Business Today → Calendar when operational booking lives in Kontext Business.

Result: OS Calendar surfaces schedule context for briefs and operator chat — Business calendar remains /business Today tab.

KO-17. Browse files in OS Files

Path: OS app catalog → Files · OSFilesBrowser

You do:

1. Open Files from OS apps.
2. Browse user file storage — OS activity digests, imports, and scoped documents for AME.
3. Preview supported file types in the in-OS viewer.
4. Use Files to verify bundle imports or context pack uploads landed.

Result: OS Files is your canister-scoped file browser inside the shell — not Workspace project files.

KO-41. Write in OS Notes

Path: OS app catalog → Notes · dock Notes

You do:

1. Open Notes from the dock, Start menu, or Today’s app dock.
2. Write in the page. The first line is the title. Folders sit on the left, including From Kontext for notes Kontext filed.
3. A note you keep private is never searched by your assistant. A note you share with the assistant can be.
4. Press Share with people on a note you wrote here, once it is saved and unlocked.

Result: Notes is your own notebook inside Kontext — not the Journal, and not Drive.

KO-42. Use OS To-do

Path: OS app catalog → To-do · dock To-do

You do:

1. Open To-do from the dock or Today’s app dock.
2. Add an item with a date, a time, a repeat, a priority (none, !, !!, !!!), and a flag.
3. Lists are Today, Upcoming, Watching, and Done.
4. Press Share list… when you want someone else on that list. This is not a Project Management board.

Result: To-do is your own list. Sharing it does not copy it into the other person’s book, so their assistant does not read it.

KO-45. Share a note with someone

Path: Notes → a note you wrote → Share with people

You do:

1. Open a note you wrote in Notes, saved and unlocked.
2. Press Share with people and invite them by @handle.
3. Choose Can edit or Can view.
4. They accept or decline the invite. A shared note shows Shared by you. Can view cannot change it.

Result: The note stays on your account. Nothing is copied into their notebook, and their assistant does not read it.

KO-46. Share a to-do list

Path: To-do → a list → Share list…

You do:

1. Open the list and press Share list… (it reads Shared with people… once someone is on it).
2. Invite them by @handle. Choose Can edit or Can view.
3. They see the list under invites and Assigned to me. Comment on an item, or assign it.
4. A Can view person cannot edit. Nothing is copied into their own book.

Result: You still own the list. Their assistant does not read it, because it was never copied into their book.

KO-47. Choose how often Kontext may interrupt you

Path: Menu bar bell → How often may Kontext interrupt you?

You do:

1. Open the bell in the menu bar.
2. Open How often may Kontext interrupt you?
3. Three dials: Fuel and hosting, Problems and failures, and Everything else.
4. The left end is Never. The right end is Every time. Stops in between are Weekly, Daily, 4 hours, Hourly, and 15 min.

Result: The dial only decides whether a notice pops up or is read aloud. The notice still stays in the bell. If this workspace has not taken its update, the screen says the choice is saved on this device only.

KO-48. Change the size of Talk

Path: Talk bar → size controls

You do:

1. Talk has four sizes: the resting bar, a normal thread, taller (↕), and full screen (⤢).
2. Taller stays in the room and you can see through it. Full screen is a chat under the menu bar, with New chat and your history.
3. × always collapses the thread. Escape steps down one size.
4. On World, only the galaxy slides up for a normal thread. Day, Apps, and the desk do not squash.

Result: A conversation covers the room. It does not resize the room.

KO-43. Answer an Interview

Path: OS app catalog → Interview · dock Interview · goal interview

You do:

1. Open Interview when Kontext or a manager needs facts only you have (taste, targets, constraints).
2. Answer one question at a time. Questions attributed to a manager must be a real pass for your goal — not a canned quiz wearing that name.
3. Save answers so they file as knowledge and feed the plan.
4. On a phone, Interview fills the visor pane; on desktop it opens as a fitted card.

Result: Interview closes gaps the team cannot guess. It is a native AIOS window, not a Business intake form.

KO-44. Use Today, Team, Build, and History

Path: My Kontext → Today canvas tabs

You do:

1. Open Today on My Kontext — this canvas is the day cockpit people also call the intelligence dashboard.
2. Use Today for this morning’s brief, what needs you, and approvals.
3. Use Team for platform staff (Managing Director, Scheduling, Memory, Tool, Communications, Build) plus hired teammates and recent activity. Say “open the Team tab” — “my team” opens Employees.
4. Use Build to start an app, agent, or routine without leaving the cockpit.
5. Use History for the intelligence ledger of what already ran.
6. For the vault (overview, timeline, explorer), open Settings → Everything it knows — not this canvas.
7. Ask from the bar at the bottom — it opens Talk (Kontext), not a Chat tab.

Result: The cockpit is Today / Team / Build / History. Platform staff live on Team; hired people live on Employees (Roster / Platform / Activity).

KO-18. Talk to Kontext / command layer

Path: OS desktop Talk chrome · Talk · CommandChatPanel

You do:

1. Locate Kontext command cluster on desktop or menubar (signed Talk chrome).
2. Type or use Talk for voice when enabled — one conversation surface (legacy OS Chat tab redirects here on mobile).
3. Describe a goal in plain language; heuristics or LLM match capabilities (create app, deploy, business setup).
4. Follow in-window overlays for OS-native flows (KO-19–KO-21) instead of leaving /os.
5. Use Workspace Chat only for code generation — operator tasks stay in Kontext/OS Chat profile.

Result: Natural-language command layer routes intents to the right OS flow or app.

KO-19. Create an app (OS-native flow)

Path: Kontext / command → Create app · generation overlay

You do:

1. Describe the app in Kontext or command input (e.g. “Build a todo app”).
2. Confirm capability match create-app.
3. If prompted, choose server pair: Create new, Assign existing, or Skip (KO-27).
4. Watch the generation window stream files — project is created and switched automatically.
5. When deploy-ready, Live Preview and Browser windows may open without opening Workspace.
6. If OS-native fails, Kontext falls back to Workspace Chat tab — retry or continue there.

Result: Full create-app pipeline runs in OS overlay windows; you never leave /os on the happy path.

KO-20. Create an agent (OS-native flow)

Path: Command → Create agent · project picker → agent creation window

You do:

1. Describe the agent in command layer.
2. Pick target project in OS-native project selection.
3. Resolve server pair (create / assign / skip).
4. Review spec preview — name, instructions, integrations.
5. Complete Composio OAuth in-window for required apps.
6. Wait for deploy phases: agent canister, project linkage, integration codegen.
7. Open Agent Studio from completion panel or dismiss.

Result: Agent is deployed and linked to a project entirely inside OS windows.

KO-21. Create a routine (OS-native flow)

Path: Command → Create · Today → Build · Routines create window

You do:

1. Describe standing work in plain language from command layer, Today → Build, or Routines → create.
2. Select project in OS project picker if the flow needs one.
3. Review workflow spec preview — steps, connections, integrations.
4. Complete provisioning: workflow server, agent server if needed, workflow engine, Composio OAuth.
5. Save — workflow appears in Routines unless assigned to an employee (OS-17).

Result: Standalone OS routine is created without opening Workspace Agents tab.

KO-22. Start a business solution from OS

Path: Command → business intent · /business handoff

You do:

1. Type a business-oriented goal (CRM, leads, booking, marketing automation).
2. Confirm business-solution capability match.
3. Kontext opens Kontext Business (/business) with intake dispatch.
4. Complete Business-specific fields Business wizard needs (phone, payments, recipes).
5. Return to OS Today for cross-module signals once the solution is live.

Result: Business setup starts from OS intent routing — not a dead link.

KO-23. Deploy from a deploy intent

Path: Command → Deploy · Workspace Deploy tab

You do:

1. Ask Kontext to deploy or publish your app.
2. Confirm deploy capability — Workspace Deploy tab opens with intent prefilled.
3. Verify active project in window chrome (KO-07).
4. Run deploy; use Gas Station if cycles block (KO-35).

Result: Deploy intent opens the right Workspace tab with context — you confirm deploy in Workspace.

KO-24. Edit an app from an edit intent

Path: Command → Edit · Workspace Chat

You do:

1. Describe the change (“add dark mode”, “fix checkout”).
2. Confirm edit-app capability.
3. Workspace Chat tab opens with edit intent dispatched to the active project.
4. Iterate in Chat; preview in App tab per workspace journeys.

Result: Edit intents land in Workspace Chat — OS routes you; generation stays project-scoped.

KO-25. Open Agent Studio in OS

Path: Desktop · Start menu → Agent Studio

You do:

1. Open Agent Studio from desktop or catalog.
2. Select project in title bar if prompted.
3. Use resource bar for agents, workflows, executions on that project's server pair.
4. Jump from employee cards or automation completion panels directly when offered.

Result: Agent Studio in OS is the same powers as /agents detail — scoped to OS window chrome.

KO-26. Open App Studio in OS

Path: Desktop → App Studio

You do:

1. Open App Studio for the selected project.
2. Tabs cover live site, database, context, storage, hosting, deploy in one window.
3. Use App Studio after OS-native create app handoff instead of hunting Workspace subtabs.

Result: App Studio consolidates publish surfaces for one project inside OS.

KO-27. Pick or create a server pair for OS create

Path: OS-native modal → Server pair selection

You do:

1. Trigger any OS-native create flow (app, agent, automation).
2. When modal appears, choose Create new server (allocate credits), Assign existing, or Skip if allowed.
3. For new servers, confirm credit allocation (~540 credits typical for fresh Main Agent pair).
4. For assign, pick the server pair that already hosts your Main Agent / workflows.
5. Proceed — generation or deploy uses that pair consistently.

Result: Server pair choice is explicit before long OS-native pipelines run.

KO-28. Finish post-activation setup wizard

Path: OS setup window → goals · team · apps · brief steps

You do:

1. After Deploy Agent & Workflow Engine (OS-01), continue the setup wizard if shown.
2. Complete Goals step — strategy objectives feed Goal Spine and brief ranking (OS-26).
3. Skim Team and Apps steps — connect suggested Composio apps.
4. Configure initial Brief preferences (OS-07).
5. Land on Ready — Today and Employees tabs unlock.

Result: Post-activation wizard connects goals, apps, and brief defaults in one pass.

KO-29. Import an employee or automation bundle

Path: My Kontext → Import bundle · OSBundleImportWizard

You do:

1. Open bundle import from OS settings or Employees/Automations import entry.
2. Upload bundle file or pick marketplace pack marked OS import.
3. Review included employees, automations, and Composio requirements.
4. Connect missing OAuth apps before enabling schedules.
5. Confirm import — roster cards and workflows appear; disabled until you turn them on.

Result: Prebuilt OS teams land on your canister with remapped ids — nothing runs until you enable.

KO-30. Export an OS bundle

Path: OS bundle export controls

You do:

1. Open export from OS settings or employee roster menu.
2. Select employees, automations, or full snapshot to export.
3. Download bundle JSON for backup or another account.
4. Store securely — bundles may include profile instructions and integration hints.

Result: You can backup or share OS employee/automation configurations as a bundle file.

KO-31. Manage server pairs from OS

Path: OS → Server management window

You do:

1. Open server management from OS settings or welcome modal when no server exists.
2. View paired agent and workflow canisters, cycle hints, and initialization status.
3. Create, assign, or troubleshoot pairs before hiring employees.
4. Use No server welcome path if Main Agent is missing — links to pair creation.

Result: Server pairs are visible and manageable from OS without admin console.

KO-32. Open Iteration Hub

Path: Start menu → Iteration Hub

You do:

1. Open Iteration Hub from tools category.
2. Select project when prompted.
3. Use hub to coordinate multi-step iteration across Chat, preview, and deploy.

Result: Iteration Hub groups iteration workflows for active projects inside OS.

KO-33. Use mobile Talk icon rail

Path: Mobile PWA /os · bottom icon rail

You do:

1. Open Kontext OS on mobile — Talk replaces separate OS Chat tab (UNIFY-01).
2. Use bottom icon rail for Today, Talk, key dock apps.
3. Open conversation sheet for operator tasks; voice settings in Talk panel (OS-39).
4. Rotate to landscape only if your device supports OS desktop chrome.

Result: Mobile OS keeps one Talk surface and a thumb-friendly rail — no duplicate chat tabs.

KO-34. Restrict OS apps by member role (admin)

Path: Admin → access control · OS app visibility

You do:

1. As platform admin, open member or role access editor.
2. Under OS app visibility, allowlist apps for restricted roles (customer, ambassador, team).
3. Save — affected users see fewer dock/desktop/catalog icons on next load.
4. Verify with a test account — hidden apps should not appear in Start menu.

Result: Role-based OS visibility hides modules a member should not open — switcher respects same rules.

KO-35. Open Gas Station from OS

Path: Start menu · catalog → Gas Station · /gas-station

You do:

1. Open Gas Station from OS catalog or after deploy/cycle errors.
2. Top up cycles or credits for canisters tied to your projects.
3. Return to Deploy or OS-native create after successful top-up.

Result: Gas Station is reachable from OS when hosting or deploy blocks on low cycles.

KO-36. Open Documentation from OS catalog

Path: Discovery → Documentation

You do:

1. Open Documentation from Start menu discovery category.
2. Browse platform docs module inside OS window or embedded route.
3. Use for owner guides while staying in /os.

Result: Product documentation is a first-class OS app — not an external-only link.

KO-37. Open Kontext Team hub (team members)

Path: Desktop Kontext Team · team-only icon

You do:

1. If your account is a team member, open Kontext Team from desktop.
2. Hub surfaces Helpdesk, Project Management, Google Workspace shortcuts, Social tools per team config.
3. Customers without team role never see this icon.

Result: Team hub consolidates internal ops apps for staff — hidden from solo owners.

KO-38. Sign in with a current login door

Path: Any sign-in screen → Login chooser

You do:

1. Open a sign-in control (landing, comment, deploy, or /ktx-code/connect).
2. Choose Google, Microsoft, Apple, a passkey, Kontext ID, or recovery — whichever the chooser offers.
3. Internet Identity appears only while the platform still turns that door on (it is off in production).
4. Finish the provider redirect or in-page passkey/Kontext ID flow.
5. Confirm you land in Kontext OS or the return path you came from — not a spinner that never resolves.

Result: You are signed in through a door the platform actually maps to your account.

KO-39. Link KTX Code as a device

Path: /ktx-code/connect · KTX Code desktop

You do:

1. Open KTX Code on your computer and start the link flow.
2. Sign in on kontext.network /ktx-code/connect with a current sign-in method (KO-38).
3. Wait for a link code to mint — this requires a workspace. A brand-new free account may have none yet.
4. Paste or confirm the code in KTX Code. Keep the Terminal/desktop window open on Mac.
5. Confirm Hub → Access → Who can act as you lists this computer. Revoke its personal key if you want to cut it off.

Result: KTX Code acts as your computer, not a Marketplace app — it can sync keys and write as you.

KO-40. Review who can act as you

Path: Hub → Access → Who can act as you

You do:

1. Open Hub → Access after signing in.
2. Open Who can act as you.
3. Read every sign-in and computer that can act as you: this sign-in, linked computers such as KTX Code, and other sign-in methods.
4. Remove access on a linked row when the control is offered. To cut off KTX Code, revoke its personal key.
5. If a sign-in you expected is missing, sign in that way once so it can appear.

Result: You can see who can act as you. Remove is offered only when this account has taken the update that actually unlinks.

OS-01. Activate OS Intelligence (first time)

Path: Kontext OS → Activate OS Intelligence (banner, Start Building, or My Kontext)

You do:

1. Sign in and open /os or My Kontext.
2. Click Activate OS Intelligence — the os-setup window opens ("Setting up OS Intelligence").
3. Review what will be created: hidden OS project, Main Agent runtime check, and reserved os-intelligence system profile.
4. Click Deploy Agent & Workflow Engine.
5. Confirm hosting credits only if no initialized Main Agent runtime exists yet (~540 credits for a new pair).
6. Wait for completion — activation is instant when a unified runtime is already running.

Result: The os-intelligence system profile is created on your Main Agent runtime; Talk, Daily Brief, Employees, and Routines unlock.

OS-02. Activate onto an existing Main Agent runtime

Path: OS setup → Deploy Agent & Workflow Engine (when Main Agent already exists)

You do:

1. Ensure you already have a workspace-registered Main Agent server with an initialized unified runtime.
2. Open Activate OS Intelligence from Talk, Today, or My Kontext.
3. Read the setup copy — it should indicate colocation on your existing runtime, not a new canister.
4. Click Deploy Agent & Workflow Engine without a second credit consent.
5. Confirm the pinned os-intelligence profile appears in Agent Studio on the same server as your global agents.

Result: OS Intelligence shares your Main Agent for free; fuel reserve floor protects the system profile from cycle starvation.

OS-03. Connect an external tool (Composio OAuth)

Path: OS → Composio services or employee/automation create → Connected services

You do:

1. Open the Composio services manager from OS Intelligence settings, Employees hire flow, or Routines create.
2. Browse the unified native + Composio catalog — KESA (kontext-ecosystem) is listed first; external apps follow.
3. Pick an app (Gmail, Slack, Stripe, Notion, Google Calendar, …).
4. Click Connect and complete OAuth in the popup.
5. Return to the manager and confirm the app shows Connected.
6. Optionally open the profile's Tools allowlist to restrict which Composio actions this persona may call.

Result: External SaaS tools are authorized for OS profiles; agents and employees can use them in tasks after KESA is enabled.

OS-04. Restrict Composio tools on a profile

Path: Composio services manager → connected app → Tools allowlist

You do:

1. Open Composio services from OS settings or a profile's Connected services panel.
2. Select an already-connected app.
3. Expand Tools allowlist (or equivalent restrict panel).
4. Disable actions you do not want this employee or automation to invoke (e.g. send email but not delete).
5. Save the allowlist.
6. Re-run a small test task from the profile to confirm blocked tools are not offered.

Result: Least-privilege Composio access per OS employee or standalone automation without disconnecting OAuth.

OS-05. Open Composio services from OS Intelligence settings

Path: /os → OS Intelligence settings hub → Composio services

You do:

1. Open Kontext OS and navigate to OS Intelligence settings (gear or settings hub).
2. Select Composio services (same manager used by Employees and Routines).
3. Review connected vs available apps in one place.
4. Connect a new app or disconnect one you no longer use.
5. Note which profiles reference each connection when the UI shows linkage hints.
6. Close settings — changes apply to all profiles sharing that OAuth connection.

Result: Central place to manage external integrations for the entire OS layer without opening each employee card.

OS-06. Read your Daily Brief

Path: My Kontext → Daily Brief (or Today when Business is linked)

You do:

1. Open My Kontext from the OS shell or dock.
2. Select Daily Brief (or the brief section on Today when Business modules feed signals).
3. Scan color-coded sections: revenue, calendar, inbox, deployments, and other enabled sources.
4. Read overnight/morning items composed from live state signals and AME memory (on-chain + optional Mem0/Notion/documents).
5. Note action rail suggestions attached to hot signals (e.g. hot leads, open tickets).
6. Tap an action rail to jump into the module that can resolve the item.

Result: A scannable morning summary grounded in real platform state, not a static template.

OS-07. Configure Daily Brief preferences

Path: Daily Brief → Preferences or settings gear

You do:

1. Open Daily Brief on My Kontext or Today.
2. Click Preferences (or the settings gear on the brief header).
3. Toggle sections you want each morning (revenue, calendar, inbox, deployments, notifications, etc.).
4. Choose which data sources and signal types feed each section.
5. Adjust delivery tone or density if the UI exposes tone controls.
6. Save preferences.

Result: Future briefs respect your section choices, sources, and tone; disabled sections no longer clutter the scan.

OS-08. Generate a brief on demand

Path: Daily Brief → Generate or refresh control

You do:

1. Open Daily Brief after connecting Composio apps and enabling KESA on OS profiles.
2. Confirm brief preferences are saved (journey OS-07).
3. Click Generate brief or the refresh action (not only waiting for the scheduled run).
4. Watch the compose step pull state signal collection snapshots and KESA module reads.
5. Review newly persisted brief items when generation completes.
6. Use action rails on any fresh hot signals surfaced in this run.

Result: An up-to-the-minute brief without waiting for the next scheduled workflow cycle.

OS-09. Act on a state signal action rail

Path: Daily Brief or Today → signal row → action rail

You do:

1. Open Daily Brief or the Today surface where Business-linked signals appear.
2. Locate a fired state signal (hot lead, open ticket, failed deploy, unread notification cluster, etc.).
3. Read the suggested action rail chain shown beside the signal (e.g. list leads → mark contacted → open CRM).
4. Tap the primary rail action — Kontext routes you to the correct module with context prefilled where supported.
5. Complete the first step in that module (update record, send reply, acknowledge alert).
6. Return to the brief or Today to confirm the signal severity or count updated on refresh.

Result: Signals become one-click workflows instead of manual module hunting.

OS-10. Hire an OS Employee from a template

Path: OS → Employees tab → Hire teammate → template

You do:

1. Open Employees on My Kontext (Your team rail) — not a Chat tab.
2. Stay on Roster for people you hired. Platform is the six staff the OS ships. Activity is what they did.
3. Click Hire teammate and pick a template (research, inbox triage, deploy watch, etc.).
4. Name the persona and set role copy; choose delivery channel (email/text) if prompted.
5. Review pre-linked duties — native KESA actions and suggested Composio apps from the template.
6. Connect missing Composio services via the unified catalog picker (KESA first, then OAuth apps).
7. Confirm deploy on Main Agent if the wizard provisions a new workflow group.
8. Save — the roster card appears and assigned workflows leave the general Routines list.

Result: A named teammate card runs grouped workflows on your unified runtime with template-sensible defaults.

OS-11. Hire an OS Employee in plain language

Path: Employees → Hire teammate → describe duties

You do:

1. Open Employees and choose Hire teammate without a template.
2. Describe what the teammate should do in plain language (schedule, triggers, outputs).
3. Let entity orchestration generate a spec — review inferred KESA module scope and Composio needs.
4. Turn on Kontext Ecosystem (KESA) and tap Add to agent on each area this teammate should use. Skip any they should not touch — nothing added means they cannot use that area.
5. Complete Composio OAuth for any external apps the spec requires.
6. Name the persona, set delivery channel, and confirm workflow deploy on Main Agent.
7. Save — the employee registers with workflow linkage at create time (persistence on your canister).

Result: A custom OS teammate from natural language, same engine as Routines but hidden from the general list.

OS-12. Hire from existing routines

Path: Employees → Hire from existing routines

You do:

1. Open Employees and select Hire from existing routines.
2. Multi-select standalone routines you already run in Routines.
3. Review the inferred profile, combined duties, and shared Composio/KESA scope.
4. Name the teammate and adjust delivery channel or persona copy if needed.
5. Confirm — selected workflows re-parent under one roster card.
6. Open Routines and verify those workflows no longer appear in the standalone bucket.

Result: Standalone routines consolidate under one teammate without rebuilding workflows from scratch.

OS-13. Run an employee on demand

Path: Employees → select teammate → Run

You do:

1. Open the Employees tab and select the teammate card.
2. Review assigned workflows and last-run status on the card.
3. Click Run (single workflow) or the run control for the default duty.
4. Watch execution status on the Main Agent runtime (progress, success, or error).
5. Open execution detail or logs if the run fails — check KESA scope and Composio connectivity.
6. Confirm output (email, text, in-app notification, or module update) matches the persona's delivery channel.

Result: The employee's workflow group executes immediately on your unified agent runtime without waiting for schedule.

OS-14. Run an employee sequence (Run all)

Path: Employees → teammate with multiple workflows → Run sequence / Run all

You do:

1. Open an employee card that owns an ordered run sequence or multiple linked automations.
2. Review sequence order (fleet-level or per-employee grouping shown on the card).
3. Click Run all or Run sequence.
4. Monitor each step's status as the runtime executes in configured order.
5. Pause or cancel mid-sequence only if the UI exposes safe stop controls.
6. Review combined results in activity or Agent Studio executions when finished.

Result: Ordered automation groups fire as one operator action — useful for morning routines tied to a teammate.

OS-15. Pause an OS Employee

Path: Employees → teammate menu → Pause

You do:

1. Open the Employees tab and select the teammate to pause.
2. Open the card menu (⋯) and choose Pause.
3. Confirm pause — schedules and automatic triggers for this employee stop firing.
4. Verify the card shows a paused state (badge or dimmed run controls).
5. Leave workflows assigned — they remain under the employee, not moved back to Routines.
6. Optionally run Run manually later to test while paused schedules stay off.

Result: The teammate stops autonomous runs without deleting workflows or firing the persona.

OS-16. Fire an employee and return workflows

Path: Employees → teammate menu → Fire

You do:

1. Open the employee card you want to remove.
2. Choose Fire from the card menu.
3. When prompted, decide whether to move workflows back to Routines or delete them.
4. Confirm fire — the roster card disappears from Employees.
5. If you chose move-back, open Routines and verify workflows reappear in the standalone bucket.
6. Disconnect Composio allowlists tied only to that persona if you no longer need them.

Result: The teammate is removed; workflows are either released to Routines or deleted per your choice.

OS-17. Create a standalone OS routine

Path: My Kontext → Routines (Your team) → create

You do:

1. Open Routines on My Kontext (workflows not assigned to an employee).
2. Click Create — OS-native entity orchestration opens (same pipeline as /agents). You can also start from Today → Build.
3. Describe the routine in plain language or pick Quick/Editor mode if offered.
4. Enable Kontext Ecosystem (KESA) and tap Add to agent on each built-in area this routine should use. Skip the rest. Connect Composio apps after KESA.
5. Complete OAuth for external tools; review tools allowlist per connected app.
6. Name, describe, and confirm deploy to Main Agent (credit consent only if runtime missing).
7. Save — the workflow appears in Routines until assigned to an employee.

Result: A standalone OS routine on the unified runtime, visible in Routines and Agent Studio registry.

OS-18. Move a standalone routine to an employee

Path: Routines → workflow card → Move to employee (or Employees → assign)

You do:

1. Open Routines and locate a standalone workflow not yet under a teammate.
2. Open the card menu and choose Move to employee (or start from Employees → assign existing).
3. Pick an existing employee or create a new roster name inline.
4. Confirm re-parent — the workflow leaves the general Routines list.
5. Open Employees and verify the workflow appears under the chosen teammate card.
6. Run the employee once to confirm scope and triggers still work after the move.

Result: Standalone routine becomes an employee duty without rebuilding steps or reconnecting services.

OS-19. Inspect on-chain memory (AME)

Path: Kontext Assistant → Settings → Everything it knows (also called the memory intelligence dashboard)

You do:

1. Open Settings on My Kontext and choose Everything it knows — or ask Kontext “open the intelligence dashboard” / “show everything it knows.”
2. Use Overview for layer health, Timeline for when facts landed, Explorer to switch source (registry, activity, brief, Mem0, Notion, drives).
3. Open the inline knowledge graph or Open brain for the Mind overlay.
4. Edit or delete an on-chain entry you no longer want remembered.
5. Clean slate wipes typed stores too — leftover plans for deleted goals are a bug.
6. Note optional Mem0, Notion, or document sources when connected — they appear alongside on-chain rows.

Result: AME routes reads/writes correctly; you control what persists on-chain vs optional external memory sources.

OS-20. Scope KESA modules for an OS profile

Path: Employee or automation profile → Connected services → Ecosystem

You do:

1. Open a hired OS employee or automation — not Kontext. Kontext can use built-in areas without this list.
2. Expand Connected services on the right rail or profile panel.
3. Enable Kontext Ecosystem (KESA) if not already on.
4. Tap Add to agent on each built-in area this person should use (Helpdesk, Business, Finance, …). Skip the rest.
5. If none say On agent, this person cannot search or act in any built-in area.
6. Run a small task that needs a skipped module — it should refuse, not pretend it ran.

Result: Hired teammates only get the areas you added. Your assistant (Kontext AIOS) is not this rule. Account-wide offs still apply to everyone.

OS-21. Opt in projects for OS delegation

Path: OS → Steer your AI → project opt-in

You do:

1. Open OS Intelligence settings or Steer your AI from My Kontext.
2. Locate project opt-in — the catalog of projects OS may delegate into.
3. Enable opt-in for each project whose agents and workflows OS Intelligence may invoke.
4. Confirm workspace-global agents (All projects badge) are always visible without per-project opt-in.
5. Save opt-in choices.
6. Optionally verify opted-in projects in Workspace → Agents show linkable agents for delegation targets.

Result: OS assistant builds a delegation catalog from opted-in project agents plus all workspace-global agents.

OS-22. Delegate a task to a project agent

Path: Talk → task needing project agent → confirm delegation

You do:

1. Complete project opt-in (journey OS-21) for target projects.
2. Open Talk on My Kontext — tasks execute on the os-intelligence profile by default.
3. Ask OS Intelligence to perform work that requires a specific project's agent (e.g. "run the deploy checker on Project X").
4. Read the delegation prompt — OS shows which agent or workflow it will invoke.
5. Confirm delegation when prompted.
6. Monitor execution status; open Agent Studio logs if the handoff fails (scope, opt-in, or runtime fuel).

Result: OS assistant delegates to the opted-in project agent or workspace-global catalog entry instead of guessing in Chat alone.

OS-23. Use the Today cockpit (Today / Team / Build / History)

Path: My Kontext → Today

You do:

1. Open Today on My Kontext after OS Intelligence is active.
2. Stay on Today for this morning’s brief, what needs you, and Needs your OK.
3. Switch to Team for the six platform staff plus hired teammates and recent activity.
4. Switch to Build to start an app, agent, or routine without leaving the cockpit.
5. Switch to History for the ledger of what already ran.
6. Use the ask bar at the bottom — it opens Talk (Kontext), not a Chat tab.
7. Open Daily Brief on the left rail when you want the full morning read (same signals, longer view).

Result: Today is Today / Team / Build / History. Daily Brief is the deep read. Talk is where you reach Kontext. Employees and Routines are on the team rail.

OS-24. Browse OS capability catalog

Path: OS Intelligence settings → Capability catalog

You do:

1. Open OS Intelligence settings from /os.
2. Select Capability catalog (automations and workflows you can turn on/off).
3. Browse grouped capabilities — native OS flows, KESA actions, and connected Composio duties.
4. Toggle capabilities on or off to match what you want OS and employees to offer.
5. Save catalog choices.
6. Open Employees or Routines and confirm disabled capabilities no longer appear in create wizards.

Result: You control which OS-native and connected capabilities surface in hire/create flows without disconnecting OAuth globally.

OS-25. Talk to Kontext (operator tasks)

Path: My Kontext → Talk (Assistant rail) · Kontext visor

You do:

1. Activate OS Intelligence (journey OS-01) if not already done.
2. Click Talk on the Assistant rail (or the ask bar on Today). There is no Chat tab.
3. Ask for operator tasks — inbox triage, module lookups via KESA, schedule checks — not code generation (use Workspace Chat for that).
4. Grant KESA or connected-app scope if Talk reports missing tools.
5. Follow delegation prompts when a task needs a project agent (journey OS-22).
6. Review responses enriched by AME memory and live state when connected.

Result: Natural-language operator layer on the os-intelligence profile with KESA-first routing. Talk is where you reach Kontext; Workspace Chat is for code.

OS-26. Set strategy objectives (Goal Spine)

Path: Talk to Kontext · or My Kontext → settings · setup Goals

You do:

1. Tell Kontext the goal — “add a goal to …”, “my goal is …”, or just say the outcome after Kontext asks. Kontext saves it on your Goal Spine. You do not have to open Settings first.
2. Or open OS Intelligence settings / the setup Goals step (KO-28) to add or edit strategy objectives by hand.
3. Link objectives to brief ranking and employee duties where the UI exposes goal chips.
4. Goal Spine stores objectives on your account. Staff start a plan after a new goal lands.
5. Revisit when priorities change; goal progress lives on Today and under Settings → Progress (OS-27). You can also log a number in Talk (“we’re at 12”).

Result: Objectives you said out loud (or typed in Goals) anchor briefs, memory, and manager reports.

OS-27. Review goal progress

Path: My Kontext → Today · Settings → Progress

You do:

1. Open Today after OS Intelligence activation and scan the goal snapshot on the canvas.
2. For the full evidence board, open Settings and choose Progress (not a top-level Progress tab).
3. Scan which objectives have recent workflow outcomes vs gaps.
4. Open Employees or Routines suggested for under-served goals.
5. Compare with Daily Brief headlines for the same morning.

Result: Progress shows whether the OS is moving your stated goals — it lives on Today plus Settings, not a separate top tab.

OS-28. Review team health (fleet pulse)

Path: My Kontext → Today → Team · Settings → Operations

You do:

1. Open Today → Team for platform staff glance, hired teammates, and last-day activity.
2. Open Employees for Roster / Platform / Activity (the full team room).
3. Open Settings → Operations for fleet tiles: connected services, teammate count, routine health.
4. Expand platform staff reports when shown — Managing Director, Scheduling, Memory, Tool, Communications, Build.
5. Fix red rows inline — reconnect OAuth, pause failing routines, or open connected services (OS-03).

Result: Team answers who is working. Operations (in Settings) answers whether the OS is healthy.

OS-29. Approve a platform staff recommendation

Path: Today · Team · Needs your OK queue

You do:

1. Open Needs your OK on Today (approvals panel) or a manager card on Team.
2. Read plain-language proposal — schedule change, tool swap, memory link, comms draft, build, etc.
3. Choose Approve, Edit, or Dismiss — mutations that touch runtime wait for you unless autonomy is on (OS-37).
4. Verify deed or outcome log after approval shows the change applied.

Result: Platform staff recommend; you approve mutations that matter — trust gradient preserved.

OS-30. Read platform staff reports

Path: Today → Team · Employees → Platform · manager cards

You do:

1. Open Today → Team and scan the six platform staff: Managing Director, Scheduling Manager, Memory Manager, Tool Manager, Communications Manager, Build Manager.
2. Open Employees → Platform for the same immovable roster (you cannot fire these).
3. Read each manager’s last-run report — synthesized headline, not raw JSON.
4. Drill into evidence (workflow outcomes, connection health, builds).
5. Act on queued recommendations (OS-29) or adjust hired-employee duties based on the report.

Result: Six platform staff audit the account and report. Hired teammates on Roster are different people you created.

OS-31. Browse Signals Studio

Path: OS Intelligence settings → Signals · OSSignalsStudio

You do:

1. Open Signals Studio or signals browser from settings.
2. Review registered state signals — hot leads, deploy failures, tickets, notifications.
3. Toggle or tune which signals feed Daily Brief sections (OS-07).
4. Test a signal source after connecting Composio or Business modules.

Result: You see which live polls drive brief sections and action rails before morning read.

OS-32. Set brief density (calm / normal / busy)

Path: Daily Brief preferences · OsIntelligenceControlPanel

You do:

1. Open Daily Brief Preferences (OS-07).
2. Choose density calm, normal, or busy — controls section count and verbosity.
3. Save and generate a fresh brief (OS-08) to preview the difference.

Result: Brief length matches how much morning noise you want — calm for scan, busy for operators.

OS-33. Run Routines fleet Run all sequence

Path: My Kontext → Routines · fleet room

You do:

1. Open Routines (standalone workflows not under employees).
2. Locate a sequence group or fleet package with Run all.
3. Confirm OS setup complete and at least one employee exists if assign prompts appear.
4. Click Run all — watch live progress panels per execution.
5. Review failures in Agent Studio executions if a step errors.

Result: Grouped routines fire in order from the Routines fleet room.

OS-34. Attach a bring-your-own skill to an employee

Path: Employees → teammate → Skills · import skill.md

You do:

1. Open an employee card → Skills or BYS attach panel.
2. Import a skill.md or pick a packaged skill.
3. Set domain allowlist and heartbeat schedule if prompted.
4. Save — skill runs on cron with namespaced keys separate from Composio.
5. Monitor first run in execution log; pause employee if skill misbehaves (OS-15).

Result: Custom skills extend employees without Composio — owner-supplied SOPs on a schedule.

OS-35. Import or attach a context pack

Path: OS → Context packs panel

You do:

1. Open Context packs from OS Intelligence settings.
2. Upload or select a pack scoped to OS or a project.
3. Confirm pack files appear in Files browser when stored on canister.
4. Reference pack in employee duties or Chat system context as described in UI.

Result: Scoped document bundles feed AME and agent context without polluting global memory.

OS-36. Review Agent outputs panel

Path: My Kontext → Agent outputs · OSAgentOutputsPanel

You do:

1. Open Agent outputs from intelligence hub or settings link.
2. Browse indexed artifacts from recent employee and Talk runs.
3. Open an output row to view summary or jump to source execution.
4. Use when an employee says it delivered but you need the artifact link.

Result: Recent agent deliverables are indexed in one lane — not buried in chat scrollback.

OS-37. Set employee autonomy / trust level

Path: Employees → teammate → Autonomy dial

You do:

1. Open employee card settings.
2. Adjust Autonomy or Ask me first dial — maps to requireApproval on routines.
3. Save — high autonomy runs low-risk steps silently; low autonomy queues approvals (OS-29).
4. Test with a manual Run (OS-13) to see approval behavior.

Result: Trust gradient is per employee — skeptical owners start strict and loosen over time.

OS-38. Configure Kontext voice settings

Path: Talk toolbar → Voice · JarvisVoiceSettings

You do:

1. Open Kontext conversation toolbar on desktop or mobile sheet.
2. Open Voice settings — pick voice, speed, push-to-talk if available.
3. Save — Talk mode uses new settings on next utterance.
4. Use headphones on mobile to avoid feedback.

Result: Voice Talk matches your preference without affecting Workspace Chat.

OS-39. Add personal API keys for OS memory

Path: Profile → API keys → OS memory · PersonalApiKeysPanel

You do:

1. Open Profile → Settings → API keys → OS memory (Notion token path pairs with AME-02).
2. Paste provider keys Mem0 or other optional layers require.
3. Return to Memory Providers (AME-01) and confirm health tiles turn green.
4. Never share keys in chat — paste only in Profile form.

Result: Optional memory providers authenticate via your Profile keys — separate from Composio OAuth.

OS-40. Copy Talk session to continue elsewhere

Path: Talk toolbar → Copy session · clipboard handoff

You do:

1. Mid-conversation, open the Talk toolbar.
2. Choose Copy session (clipboard handoff) when switching device or sharing with support.
3. Paste into a new Talk session on another tab if product exposes import handoff.
4. Note: full cross-device sync may be partial — treat as same-browser convenience (CAP-02).

Result: Session handoff preserves recent turns for continuity — not a full cloud chat history product yet.

OS-41. Use Employees Roster, Platform, and Activity

Path: My Kontext → Employees (Your team)

You do:

1. Open Employees from the Your team rail.
2. Use Roster for teammates you hired (pause, fire, run).
3. Use Platform for the six immovable staff: Managing Director, Scheduling Manager, Memory Manager, Tool Manager, Communications Manager, Build Manager.
4. Use Activity for recent runs and failures.
5. Do not look for a Chat tab here — Talk is on the Assistant rail.

Result: Hired people and platform staff are two different lists in the same room. You cannot fire platform staff.

How it works

Route /os. React OS shell with dock, desktop icons, multi-window apps, widgets, and Kontext/command layer. Kontext AIOS (OS Intelligence) persists on the user canister, runs employees/workflows on the agent runtime canister, and uses Zoe Assistant + droplet for headless briefs when the browser is closed. Composio OAuth and KESA extend employee reach. Six platform staff (including Build Manager) are first-class roster cards.

Benefits

• Start almost any Kontext job from one desktop.
• AIOS turns goals into briefs, approvals, and delegated employees.
• Multi-window + project selector keep build and ops side by side.

Who it's for

Primary: owners who live in Kontext daily (builders + business operators). Also: team roles with OS app allowlists. Not: people who only need a single public page.