Hub

Capabilities

The Hub (/hub) is the map of your Kontext — Overview, Apps, Workforce, Access, Network, Money. Studios and Workspace change things. The Hub shows them. Access lists who can act as you; it does not create a Kontext ID.

• Overview — Needs you, where you stand, what happened

• Apps — What you built, servers you hold, Sign in with Kontext

• Workforce — OS staff, app workers, employees, agents — Open in studio → /agents

• Access — Who can act as you, apps you allowed, daily send limit (not Authority)

• Network — Groups you run and groups you are in — not the /network feed

• Money — Spend/earn slice. No checkout. Not Finance, not Audit, not Pricing

What is the Hub?

The Hub (/hub) is the map of your Kontext — apps, people who work for you, who can act as you, groups, and a slice of money. Studios and Workspace change things. The Hub shows them. It does not keep its own copy. It is a full page, not a My Kontext window. There is no ?tab= link.

The Hub tabs

• Overview: Needs you, where you stand, what happened. Empty Needs you means every axis was read.
• Apps: What you built, servers you hold, Signed in with Kontext, Sign-in clients you issue, Registered by you.
• Workforce: OS staff, app workers, employees, agents — kind from markers, not the name. Open in studio goes to /agents.
• Network: Groups you run and groups you are in. Not the /network social feed.
• Access: Who can act as you, apps you allowed, daily send limit, sign-in methods. Code id is authority — say Access.
• Money: A spend/earn slice. No checkout. Full billing is Profile, Audit, Gas Station, Business → Revenue.

Overview and Apps blocks

Needs you is derived: Apps · Lines · Workforce · Access · Money. Empty is a real answer. Where you stand does not count courses, groups, or communities. What happened merges recent activity (about 25 shown). Apps: What you built, Servers you hold, Signed in with Kontext (grants you gave — Revoke access), Sign-in clients you issue, Registered by you (apps you operate). Issuer vs consumer: registered-by-you is apps you run; signed-in-with-Kontext is grants you gave as a user.

Money on Hub

Earned through the platform — someone else paid to use your agents. Not your chats, not Marketplace Stripe, not KTX. What you pay, standing — credits, subscription, runway when known. No combined total. Your domains. What you used · last N days — Calls, Texts, Email, Model calls. Recent, on your bill.

How you sign in

Sign-in is the chooser: Google, Microsoft, Apple, a passkey, Kontext ID, or recovery. Internet Identity is off unless an admin turns it back on. Kontext ID is a passkey account with no Google, Apple, or Microsoft attached. Hub → Access lists methods; it does not create a Kontext ID. One person can use more than one method. They all open the same account.

Hub vs My Kontext vs Workspace

Hub is the map. My Kontext is the desktop you work from. Workspace is where you write and deploy an app. Access is not Profile API keys.

What Access can and cannot do

Can: revoke apps you allowed; set the daily send limit (zero is reply-only); remove a passkey; change account policy; name or remove a linked computer when the account is new enough; revoke a personal key. Cannot: unlink Google / Microsoft / Apple; revoke you or this sign-in; add workspace people (Business → Workspace); buy a number; add a sending domain; top up fuel; turn on project sharing for assistants; mint recovery codes.

Not yet

The Hub (/hub) is the map of your Kontext — apps, workforce, who can act as you, network, and money. Studios configure. Sign-in is the chooser (Google, Microsoft, Apple, passkey, Kontext ID, recovery) — not Internet Identity.

• Overview — Counts for apps, workforce, and what needs you

• Apps — Apps you built and apps that may use this account

• Workforce — Agents, employees, workers, OS staff

• Access — Sign-in methods, computers, keys, apps you allowed, who can act as you

• Network — Groups you run and groups you are in

• Money — The spend/earn slice the Hub can already see

What is the Hub?

The Hub (/hub) is where you stand to see all of it. Studios and Workspace configure. The Hub is the map of your Kontext — what you built, who works for you, who can act as you, and what needs you. It does not store its own records. Every panel is a window onto live platform state.

The Hub tabs

• Overview: A first glance: apps, workforce, permissions, and what needs you.
• Apps: Apps you built and apps that may use your account. Sign-in clients you issue are a window onto Developers.
• Workforce: Who works for you: agents, employees, app workers, and OS staff — not a leftover project list.
• Access: Who can act as you: this sign-in, other sign-in methods, KTX Code and other computers, keys, and apps you allowed.
• Network: Groups you run and groups you are in — connections the account can prove.
• Money: A spend/earn slice the Hub can already see. Full billing stays in Profile and Business → Revenue. A small number here is not your whole bill.

Sign-in methods and Kontext ID

Sign-in is the chooser, not Internet Identity. Production offers Google, Microsoft, Apple, passkey, Kontext ID, and recovery. Internet Identity is admin-togglable and is off in production. Kontext ID is a passkey-native account with no Google/Apple/Microsoft attached. Recovery is the way back in if you lose the device. One person can use more than one sign-in method. They all resolve to the same account. Hub → Access → Who can act as you lists every sign-in and computer that can act as you.

User journeys

HUB-01. Open the Hub

Path: Module switcher · dock · /hub

You do:

1. Sign in with a current method (Google, Microsoft, Apple, passkey, Kontext ID, or recovery).
2. Open Hub from the module switcher, the OS dock, or go to /hub.
3. Wait for Overview counts to settle — Apps, Workforce, and Access should stop showing skeletons.
4. Use the tab row: Overview · Apps · Workforce · Network · Access · Money.

Result: You are in the Hub looking at live account state, not a studio editor.

HUB-02. See the apps you built

Path: Hub → Apps

You do:

1. Open Hub → Apps.
2. Read apps you built and apps that may use your account as two lists.
3. Open a row to inspect. Edit the app in its studio or Workspace, not by inventing settings on this page.
4. To register or edit sign-in for other people, follow Manage in Developers.

Result: You can tell what you made and what is attached. The Hub does not replace Deploy or App Studio.

HUB-03. Review the workforce

Path: Hub → Workforce

You do:

1. Open Hub → Workforce.
2. Read agents, employees, app workers, and OS staff as people who work for you.
3. Do not treat an empty-looking list as “you have no agents” while a row is still loading.
4. Change someone in Agents, OS Employees, or the channel desk — the Hub is the map.

Result: You can see who works for you without opening each studio first.

HUB-04. See who can act as you

Path: Hub → Access → Who can act as you

You do:

1. Open Hub → Access.
2. Open Who can act as you.
3. Read this sign-in, other sign-in methods, and computers such as KTX Code.
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.

HUB-05. Create a Kontext ID

Path: Any sign-in screen → Kontext ID / passkey signup

You do:

1. Open a sign-in control and choose Create a Kontext ID (or the passkey signup row).
2. Complete the device passkey prompt — this is not Google or Apple.
3. If the ID is created but the session does not open, use Sign in with a passkey on the same screen.
4. Confirm you land in Kontext OS, Hub, or the page you came from.

Result: You have a Kontext ID you can sign in with on this device, with no provider account attached.

HUB-06. Link KTX Code from the Hub

Path: /ktx-code/connect · Hub → Access

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.
3. Wait — the page usually sends the code to the local app by itself. Paste only if it asks you to.
4. A brand-new free account may not have a workspace yet — wait for a code or the honest empty state.
5. Open Hub → Access and confirm the computer appears under who can act as you.

Result: KTX Code acts as your computer. Revoke its personal key when you want it gone.

HUB-07. See the worker your app got at deploy

Path: Hub → Workforce · Workspace → Agents · kontext-app.json

You do:

1. Deploy an app (or open one you already shipped).
2. Open Hub → Workforce and look for the row tied to that app — it is an app worker, not a person you hired.
3. Open Workspace → Agents on that project and confirm the dedicated worker (not only an agent you linked yourself).
4. Do not look in project.deployedAgents — that list is leftover. The live link is the app's files.
5. To give it mail or a phone line, open the worker's Channels card in Agents — same panel as other profiles.

Result: You can see the persistent worker minted at deploy. It stays until the app is removed.

HUB-08. Sign in with recovery

Path: Sign-in chooser → Recovery

You do:

1. Open any Sign in control.
2. Choose Recovery — this stays on the page (it does not leave for Google).
3. Enter the recovery material the account issued. This is not Internet Identity.
4. Confirm you land in Kontext OS, Hub, or the page you came from.

Result: You are back in the same account without the original device passkey.

HUB-09. Use a second sign-in method on the same account

Path: Chooser → a door you have not used yet · Hub → Access

You do:

1. Sign in with a method you already use (Google, passkey, Kontext ID, …).
2. Open Hub → Access → Who can act as you and note this sign-in.
3. Sign out, then sign in with a second method the chooser shows.
4. Return to Access — both doors should list as you, not as a second account.

Result: One person, several doors, one account. Missing doors appear after you use them once.

How it works

Route /hub. The Hub is a map, not a studio. Every panel reads live account state (apps you built, workforce, who can act as you, groups, a spend/earn slice). It does not store its own records. Sign-in is the chooser — Google, Microsoft, Apple, passkey, Kontext ID, recovery. Internet Identity is off in production.

Benefits

• See the whole account in one place instead of hunting studios.
• Know who can act as you (this sign-in, other doors, KTX Code and other computers).
• Create a Kontext ID when you do not want a Google/Apple/Microsoft door.

Who it's for

Primary: every signed-in owner. Also: anyone linking KTX Code or a second sign-in method. Not: a replacement for Workspace, Business, or Agents studios.