Skip to content

web: Computer sessions UI on the Computer API v1 - #1058

Merged
motatoes merged 25 commits into
mainfrom
feat/computer-sessions-ui
Nov 17, 2026
Merged

motatoes merged 25 commits into
mainfrom
feat/computer-sessions-ui

Conversation

@opencomputer-app

@opencomputer-app opencomputer-app Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Requested by @mohamed Habib in Slack.

Work 107's v1, web first: a Devin-style dashboard for starting and continuing Computer sessions, built on the Computer API v1 (/api/managed-agents/computer) with the dashboard cookie. Every dashboard page except /computer (the onboarding) and project pages now opens in this layout.

Web

  • Layout
    • A flat rail with Sessions, Automations and Secrets.
    • An account menu with an org switcher, Connections, Settings & members, API keys, Billing, a theme toggle and Sign out. Sessions only shows for orgs with a computer.
    • /computer/sessions adds the sessions sidebar. Every other page (settings, API keys, billing, automations, secrets, connections, new project) renders in the rail alone, at the same URLs as before, with the billing banner and halt modal.
  • Sidebar: New session and search (q), then Needs you, Working and Recent. Recent loads more as you scroll. There's also an archive toggle and unread dots.
  • Home: a composer with model, effort (default shown, medium) and mode pickers from GET /capabilities, and open asks answered inline.
  • Session page
    • Shows the last 20 turns, then follows new events by long-poll. Tool calls fold into Worked for ….
    • Approvals and questions are answered inline.
    • While a turn runs, you can steer or queue a message, or stop the turn.
    • Model, effort and mode can be changed, and a session can be archived.
    • Avatars for people, a "Computer" byline for the agent, and Open in Slack for Slack sessions.
  • VITE_PREVIEW=1 mocks for all of it.

Backend

  • GET /computer/capabilities without a session. The web needs it before a session exists. It's added to the api-edge allowlist too.
  • An actor's name falls back to their email, never the usr_… id.
  • stack.mjs: preview stacks get COMPUTER_API_ORGS=* and the SESSION_LOG durable object, so the sessions API works on them.

Runner (ships with the computer release)

  • A message sent from the web, CLI or API to a Slack-started session is quoted into its Slack thread under the sender's name.
  • API and web sessions get a generated title after the third message, as Slack threads do, unless a person renamed them (kept in the session's info, so it outlasts a restart). It's recorded as a session.updated title change.

Checks

  • tsc -b passes, and eslint is clean on the changed files.
  • Backend, api-edge and runner tests pass.
  • Runner: 908 tests pass. Web vitest: 369/370. Home.archive.test.tsx fails the same way on main.
  • Tried end to end on the preview stack devin-sessions-ui, against a real computer: sessions, model and effort pickers, generated titles (renamed to "Lisbon 3-day trip planning" after the third message) and every moved page.

Not in v1

The right-hand panel, the manager, multiplayer, diffs and PR cards, notifications, and moving project pages into the new layout. They need their sub-navigation and environment switcher rebuilt first, so they keep the old shell for now. Known gap: renaming a session while its computer is asleep doesn't stop the computer from naming it later.

A full-screen view at /computer/sessions: a flat icon rail, a sessions
sidebar (Needs you, Working, Recent with infinite scroll, search,
archive), a home composer that starts a session, and a session page
that follows events by long-poll, answers asks, steers or queues, stops,
and changes model/effort/mode. Calls the public API with the dashboard
cookie; no backend change. Preview mocks for VITE_PREVIEW.
@manicule-agent

manicule-agent Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

View docs preview
Commit e56b42b · 80 pages

Docs hosted with Margin

…n's thread

A turn sent to a Slack session from the web, CLI or API ran there and its reply
streamed into the thread, but the message itself never showed: Slack read as
answers with no question. The runner now quotes it into the thread under the
sender's name before the session takes it. Slack-origin sends are unchanged.
@motatoes
motatoes marked this pull request as ready for review November 17, 2026 19:48
@motatoes
motatoes merged commit 4129fb1 into main Nov 17, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants