From 217907fe6c5d96af20447354c990011a7ba833aa Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Thu, 15 Oct 2026 05:23:17 -0700 Subject: [PATCH 1/2] docs(adr-011): lift the cloud sandbox pause for the out-of-the-box goal Sam's direction on 2026-10-15: a brand-new signup gets a working hosted agent with nothing to install and a useful reply in under 60 seconds. That lifts the Tier 2 cloud sandbox pause for this purpose only; the runtime choice (today's hosted runtime or an OSS sandbox/VM/container) is decided by numbers in a one-page decision due 2026-10-17. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_015NDyNbwmCco62PAAviSL1k Co-authored-by: folio Agent-Model: claude/claude-haiku-5-5/high --- docs/adr/ADR-011-shell-first-pre-gtm.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/adr/ADR-011-shell-first-pre-gtm.md b/docs/adr/ADR-011-shell-first-pre-gtm.md index 14cb151441..c8d6ccbc54 100644 --- a/docs/adr/ADR-011-shell-first-pre-gtm.md +++ b/docs/adr/ADR-011-shell-first-pre-gtm.md @@ -6,6 +6,23 @@ --- +## Status update — 2026-10-15: the cloud sandbox pause is lifted for "out of the box" + +Sam's direction on 2026-10-15: make Commonly usable immediately, with a cloud +agent as the main lever for that, "whether we adopt new OSS sandbox/vm/container +solution or no". The target is a brand-new signup with a working hosted agent in +their pod, nothing to install, and a useful reply in under 60 seconds. Bring your +own CLI becomes the second path. + +That lifts the **Cloud sandbox runtime (Tier 2)** pause below for this purpose. +The trigger is Sam's direction, not the "heavy-compute agent" trigger the table +names, and it is scoped to the out-of-the-box goal; the other paused tracks are +unchanged. The direction does not decide the runtime itself. Whether today's +hosted runtime is enough, or Commonly adopts an OSS sandbox, VM or container, +is decided by numbers in a one-page decision due 2026-10-17: time to a first +useful reply from a fresh account, what the agent can do, where it breaks, and +the cost per team at the hosted cap. + ## Status update — 2026-04-29 **Phase 1 of shell polish is on `main` and deployed.** PR #251 mounted the `/v2` shell (V2App router, V2Layout, V2NavRail, V2PodsSidebar, V2PodChat, V2PodInspector, V2MessageBubble, V2Avatar, V2Login, V2FeaturePage, plus `useV2Api` / `useV2Pods` / `useV2PodDetail` / `useV2Pinned` / `useV2Embedded` hooks) and bundled the YC sprint reorg: trimmed nav rail (Pods · Agents · Apps · Settings), "Your Team" roster page with Hire CTA, Plan/Execute mode pill in the chat header, per-pod displayName overrides for agent messages, inline file-pill + reaction rendering (fixture-only — agents never react and there's no human write path; real reactions backend ships post-YC). From 9f9fc3237f5aaf11a2b094962819ca9448eaad53 Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Tue, 27 Oct 2026 17:40:22 -0700 Subject: [PATCH 2/2] docs(adr-011): record the shipped E2B runtime and what is still open The status update said the runtime was undecided, with a decision due 2026-10-17. The E2B sandbox is on main as commonly_run_code (#2232, TASK-266, 2026-10-15). The status line now names what is still open: the decision memo is not in the repo, and self-hosting an OSS sandbox is not decided. Co-Authored-By: Claude Haiku 5.5 Co-authored-by: folio Agent-Model: claude/claude-haiku-5-5/high --- docs/adr/ADR-011-shell-first-pre-gtm.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/adr/ADR-011-shell-first-pre-gtm.md b/docs/adr/ADR-011-shell-first-pre-gtm.md index c8d6ccbc54..69cb27be6c 100644 --- a/docs/adr/ADR-011-shell-first-pre-gtm.md +++ b/docs/adr/ADR-011-shell-first-pre-gtm.md @@ -17,11 +17,15 @@ own CLI becomes the second path. That lifts the **Cloud sandbox runtime (Tier 2)** pause below for this purpose. The trigger is Sam's direction, not the "heavy-compute agent" trigger the table names, and it is scoped to the out-of-the-box goal; the other paused tracks are -unchanged. The direction does not decide the runtime itself. Whether today's -hosted runtime is enough, or Commonly adopts an OSS sandbox, VM or container, -is decided by numbers in a one-page decision due 2026-10-17: time to a first -useful reply from a fresh account, what the agent can do, where it breaks, and -the cost per team at the hosted cap. +unchanged. The direction does not decide the runtime itself. The runtime was to be chosen by +numbers in a one-page decision due 2026-10-17: time to a first useful reply from a +fresh account, what the agent can do, where it breaks, and the cost per team at the +hosted cap. + +**Status now:** the E2B sandbox is on `main` as `commonly_run_code` (#2232, TASK-266, +2026-10-15). **Still open:** the 2026-10-17 decision memo is not in the repo, so its +numbers are not recorded here. E2B is a hosted outside service, so whether to +self-host an OSS sandbox is not decided. ## Status update — 2026-04-29