What an extension can add.
An extension can put something in almost every part of OpenChamber, and some of its work needs no window at all. Pick a number to see what goes there, how one of ours uses it, and which part of the SDK does it.
Pick a number to see what goes there.
1 A full-screen page A row under Pages opens the extension full screen, in place of the chat.
2 Marks on sidebar rows A small icon on the sessions and worktrees the extension names, with its text in the tooltip.
3 A panel on the rail An icon on the right-hand rail opens the extension's page beside the chat.
4 A live screen The extension's panel shows a picture of what the agent works in, such as a phone simulator, and a click into the picture takes control from the agent.
5 A section in Work Status A section in the panel next to the chat, with up to four controls in its header.
6 Tools in the chat Calls to the extension's tools get its icon and title, and the output shows as a card, a list, a table, JSON, Markdown or code.
7 Blocks in agent replies Agents can write the extension's components into a reply, and its page draws them.
8 IDs that become links A task ID like UPL-31 in a message, or a link to the extension's tracker, becomes clickable.
9 Toasts A short message in the bottom right corner of the window, over everything else.
10 A Git host beside GitHub A project whose remote is on the extension's Git host gets its merge requests and issues on the Issues and PRs board, in the host's own terms.
11 A tracker beside Linear Tasks from the extension's tracker get their own tab on the Issues and PRs board, next to Linear.
-
A row under Pages opens the extension full screen, in place of the chat. Acme Tasks draws its task board there.
UsesRead in the docscontributes.page -
A small icon on the sessions and worktrees the extension names, with its text in the tooltip. Acme CI puts a red cross on every session of a branch whose checks failed.
UsesRead in the docscontributes.markshost.setMark() -
An icon on the right-hand rail opens the extension's page beside the chat. A dot on the icon says something is waiting, and the tooltip gives the count.
UsesRead in the docscontributes.panelhost.setBadge() -
The extension's panel shows a picture of what the agent works in, such as a phone simulator, and a click into the picture takes control from the agent. The extension can dock its own controls beside the picture.
UsesRead the SDK referenceservice.surfacepanel.dock -
A section in the panel next to the chat, with up to four controls in its header. OpenChamber can draw the rows itself from what the extension's service answers, so the section needs no page.
UsesRead in the docscontributes.statusSectionhost.setStatusControls() -
Calls to the extension's tools get its icon and title, and the output shows as a card, a list, a table, JSON, Markdown or code. That takes a few lines in the manifest and no code.
UsesRead in the docscontributes.tools -
Agents can write the extension's components into a reply, and its page draws them. A button in the block answers the agent.
UsesRead in the docscontributes.blockshost.answerBlock() -
A task ID like UPL-31 in a message, or a link to the extension's tracker, becomes clickable. A click opens the task in the extension or attaches it to the message.
UsesRead in the docscontributes.links -
A short message in the bottom right corner of the window, over everything else. It can carry a Copy button for an error or a link, and stay until the user closes it.
UsesRead in the docshost.toast() -
A project whose remote is on the extension's Git host gets its merge requests and issues on the Issues and PRs board, in the host's own terms. They are reviewed and merged there, and a worktree or a session starts from any of them.
UsesRead in the docsprovides: ["source-control"]contributes.sourceControl -
Tasks from the extension's tracker get their own tab on the Issues and PRs board, next to Linear. The same tasks show up in the + menu, in New Worktree and among a session's linked items.
UsesRead in the docsprovides: ["tracker"]contributes.tracker
A full-screen page
A row under Pages opens the extension full screen, in place of the chat. Acme Tasks draws its task board there.
contributes.pagePick a number to see what goes there.
1 An entry in the + menu The extension's entry in the chat box's + menu opens its picker in a window.
2 Attached items An item the extension attaches sits on the chat box as a chip, where GitHub and Linear items land too.
3 Slash commands /task UPL-31 attaches the task without opening anything.
4 Rows in the @ menu The extension's service answers what the user types after @.
5 The command palette Session actions and slash commands turn up in ⌘P when the user searches for them or for the extension's name.
6 Provider logos When the extension's OpenCode plugin adds a model provider, the model picker and Settings show the provider with its own logo.
-
The extension's entry in the chat box's + menu opens its picker in a window. What the user picks lands on the message as a chip.
UsesRead in the docscontributes.attach -
An item the extension attaches sits on the chat box as a chip, where GitHub and Linear items land too. The model reads the text that comes with it, and a click on the chip opens the item in the extension.
UsesRead in the docshost.attach() -
/task UPL-31 attaches the task without opening anything. The extension looks the task up and hands it back as a chip.
UsesRead in the docscontributes.commandshost.onResolve() -
The extension's service answers what the user types after @. The row they pick goes to the agent as text, and they see a chip.
UsesRead in the docscontributes.mentions -
Session actions and slash commands turn up in ⌘P when the user searches for them or for the extension's name.
UsesRead in the docscontributes.actionscontributes.commands -
When the extension's OpenCode plugin adds a model provider, the model picker and Settings show the provider with its own logo.
UsesRead in the docscontributes.providerLogos
An entry in the + menu
The extension's entry in the chat box's + menu opens its picker in a window. What the user picks lands on the message as a chip.
contributes.attachPick a number to see what goes there.
1 A Git host The extension adds a Git host next to GitHub, GitLab and Gitea.
2 A tracker The extension adds a tracker next to Linear.
3 A notification channel The extension's service gets every notification the phone would and posts it to a chat or a server of its own.
4 An account card A card under Extension accounts where the user connects the service with a token or by signing in.
5 A usage provider A card on the Usage page next to the built-in providers, which can show in Work Status too.
6 The agent's browser The extension's service can answer the agent's browser actions, so agents browse with no desktop app open.
-
The extension adds a Git host next to GitHub, GitLab and Gitea. A project on that host gets the Issues and PRs board, pull request badges and worktrees from pull requests.
UsesRead in the docsprovides: ["source-control"]contributes.sourceControl -
The extension adds a tracker next to Linear. Tasks from that tracker show up in the picker, the + menu, New Worktree and the linked items of a session.
UsesRead in the docsprovides: ["tracker"]contributes.tracker -
The extension's service gets every notification the phone would and posts it to a chat or a server of its own. The token stays in OpenChamber.
UsesRead in the docsprovides: ["notifications"]contributes.notifications -
A card under Extension accounts where the user connects the service with a token or by signing in. The extension calls the service through OpenChamber and never sees the token.
UsesRead in the docscontributes.integrationhost.request() -
A card on the Usage page next to the built-in providers, which can show in Work Status too. The extension reads the numbers and OpenChamber draws them.
UsesRead in the docsprovides: ["quota"]contributes.quota -
The extension's service can answer the agent's browser actions, so agents browse with no desktop app open. The user picks that service as the browser provider.
UsesRead in the docsprovides: ["browser"]
A Git host
The extension adds a Git host next to GitHub, GitLab and Gitea. A project on that host gets the Issues and PRs board, pull request badges and worktrees from pull requests.
provides: ["source-control"]contributes.sourceControlPick a number to see what goes there.
1 Blocks in agent replies Blocks an extension adds to agent replies show on the phone at the reply's width, with nothing more from the author.
2 IDs that become links Task IDs like UPL-31 in chat messages become links on the phone too, with nothing more from the author.
3 Tools in the chat Calls to an extension's tools show on the phone with the extension's icon, title and output layout, with nothing more from the author.
4 Attached items An item an extension attached sits on the phone's chat box as a chip, as on desktop.
5 Toasts A toast from an extension shows on the phone as a banner at the top of the screen, Copy button included.
6 A workspace tab With panel.mobile: true, an extension's panel becomes a full-screen tab of the phone's workspace, after the built-in tabs.
7 A live screen An extension with panel.mobile: true and a live picture shows the picture in its workspace tab, with the author's own controls docked to it.
8 A section in Work status An extension's Work Status section shows in the workspace's Work status tab, with nothing more from the author.
9 Popovers as a bottom sheet A popover an extension opens from an anchor shows on the phone as a bottom sheet titled with the extension's name, with nothing more from the author.
10 A full-screen page A page marked page: { entry, mobile: true } is listed under More in the phone's sessions list and opens full screen with a back arrow.
11 Marks on session rows Marks an extension puts on sessions and worktrees show in the phone's sessions list, with nothing more from the author.
12 Actions in a session's long-press menu Session actions with mode: "background" show after Archive in the menu a long press on a session row opens.
13 Extension rows in the + sheet With panel.mobile: true, an extension's attach entry shows in the composer's + sheet, under the pickers.
14 A tracker in the + sheet A tracker an extension adds shows in the composer's + sheet next to GitHub and Linear, with nothing more from the author.
15 Slash commands An extension's slash commands work in the phone's chat box, with nothing more from the author.
16 Rows in the @ menu Rows an extension's service adds to the @ menu show on the phone too, with nothing more from the author.
17 Message actions Message actions with mode: "background" show in a message's More actions sheet on the phone.
18 Actions on selected text Selection actions with mode: "background" show as buttons in the phone's sheet for selected text.
19 A file editor An extension's editor for a file type fills the Files tab on the phone, with nothing more from the author.
20 Actions on a long press in Files File actions with mode: "background" show after Copy Path in the menu a long press on a row in Files opens.
21 Actions on selected diff lines Diff actions with mode: "background" show as labelled buttons under the comment field of selected lines on the phone.
22 Provider logos A provider logo an extension ships shows in the phone's model picker, with nothing more from the author.
23 Settings → Extensions The phone's Settings has an Extensions page to add, approve, pause and remove extensions.
24 Account cards An extension's tracker, notification channel and account cards show under Settings → Integrations on the phone.
25 A usage card An extension's usage provider gets a card on the phone's Settings → Usage page, with the extension's icon, with nothing more from the author.
26 The agent's browser Settings → OpenChamber Tools on the phone lets the user pick an extension's service as the agent's browser.
-
Blocks an extension adds to agent replies show on the phone at the reply's width, with nothing more from the author. A tap on a button in the block answers the agent.
UsesRead in the docscontributes.blocks -
Task IDs like UPL-31 in chat messages become links on the phone too, with nothing more from the author. A tap opens the extension's workspace tab when the extension has panel.mobile: true, and otherwise the link keeps its usual meaning.
UsesRead in the docscontributes.links -
Calls to an extension's tools show on the phone with the extension's icon, title and output layout, with nothing more from the author.
UsesRead in the docscontributes.tools -
An item an extension attached sits on the phone's chat box as a chip, as on desktop. With panel.mobile: true a tap opens it in the extension's tab, and without it a toast says the extension does not open on the phone.
UsesRead in the docshost.attach()panel.mobile: true -
A toast from an extension shows on the phone as a banner at the top of the screen, Copy button included. The author does nothing more for it.
UsesRead in the docshost.toast() -
With panel.mobile: true, an extension's panel becomes a full-screen tab of the phone's workspace, after the built-in tabs. Its badge count sits on the tab's icon, and Settings → General orders and hides the tab with the others.
UsesRead in the docspanel.mobile: truehost.setBadge() -
An extension with panel.mobile: true and a live picture shows the picture in its workspace tab, with the author's own controls docked to it. The status says Tap to take control, and Hand back to agent returns control.
UsesRead the SDK referencepanel.mobile: trueservice.surface -
An extension's Work Status section shows in the workspace's Work status tab, with nothing more from the author. Its controls grow to 36px for a finger, and the section chooser labels it Extension.
UsesRead in the docscontributes.statusSection -
A popover an extension opens from an anchor shows on the phone as a bottom sheet titled with the extension's name, with nothing more from the author. The sheet is as tall as the extension asked and closes with the cross, the scrim or Back.
UsesRead the SDK referencemountPopoverAnchor() -
A page marked page: { entry, mobile: true } is listed under More in the phone's sessions list and opens full screen with a back arrow. A page declared as page: true reuses the panel's HTML, so it follows panel.mobile.
UsesRead in the docspage: { entry, mobile: true } -
Marks an extension puts on sessions and worktrees show in the phone's sessions list, with nothing more from the author. A tap opens the extension's workspace tab when the extension has panel.mobile: true, and otherwise shows the mark's text and opens its link, when it has one.
UsesRead in the docscontributes.marks -
Session actions with mode: "background" show after Archive in the menu a long press on a session row opens. An action that opens the panel shows there only with panel.mobile: true.
UsesRead in the docswhere: "session"mode: "background" -
With panel.mobile: true, an extension's attach entry shows in the composer's + sheet, under the pickers. A dialog opens full screen, and a panel opens as the extension's workspace tab.
UsesRead in the docscontributes.attachpanel.mobile: true -
A tracker an extension adds shows in the composer's + sheet next to GitHub and Linear, with nothing more from the author.
UsesRead in the docsprovides: ["tracker"] -
An extension's slash commands work in the phone's chat box, with nothing more from the author. A command that opens the panel needs panel.mobile: true.
UsesRead in the docscontributes.commands -
Rows an extension's service adds to the @ menu show on the phone too, with nothing more from the author.
UsesRead in the docscontributes.mentions -
Message actions with mode: "background" show in a message's More actions sheet on the phone. An action that opens the panel shows there only with panel.mobile: true.
UsesRead in the docswhere: "message"mode: "background" -
Selection actions with mode: "background" show as buttons in the phone's sheet for selected text. An action that opens the panel shows there only with panel.mobile: true.
UsesRead in the docswhere: "selection"mode: "background" -
An extension's editor for a file type fills the Files tab on the phone, with nothing more from the author. OpenChamber keeps and saves the file, as on desktop.
UsesRead in the docscontributes.fileEditors -
File actions with mode: "background" show after Copy Path in the menu a long press on a row in Files opens. An action that opens the panel shows there only with panel.mobile: true.
UsesRead in the docswhere: "file"mode: "background" -
Diff actions with mode: "background" show as labelled buttons under the comment field of selected lines on the phone. An action that opens the panel shows there only with panel.mobile: true.
UsesRead in the docswhere: "diff"mode: "background" -
A provider logo an extension ships shows in the phone's model picker, with nothing more from the author.
UsesRead in the docscontributes.providerLogos -
The phone's Settings has an Extensions page to add, approve, pause and remove extensions. Permissions open in a bottom sheet, and the author does nothing for it.
Read in the docs -
An extension's tracker, notification channel and account cards show under Settings → Integrations on the phone. There, an account connects with a token.
UsesRead in the docscontributes.integration -
An extension's usage provider gets a card on the phone's Settings → Usage page, with the extension's icon, with nothing more from the author.
UsesRead in the docsprovides: ["quota"] -
Settings → OpenChamber Tools on the phone lets the user pick an extension's service as the agent's browser.
UsesRead in the docsprovides: ["browser"]
Blocks in agent replies
Blocks an extension adds to agent replies show on the phone at the reply's width, with nothing more from the author. A tap on a button in the block answers the agent.
contributes.blocksWork with no window open
A local service runs next to OpenChamber and keeps working while nobody looks.
service.keepRunningservice.schedule contributes.sessionEvents contributes.sessionControl contributes.instructionscontributes.skills contributes.opencodePlugin contributes.waits host.generate() host.readFile()contributes.filesystem host.storage host.onRunningShells() provides: ["opencode"] Start building
An extension is a folder with a manifest and a web page. Build an extension covers both and how to install it from the folder while you work, and the Example page has a complete one to copy.