@boxes-dev/dvb-runtime 1.0.916 → 1.0.917

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/bin/dvb.mjs CHANGED
@@ -95582,8 +95582,8 @@ var init_otel = __esm({
95582
95582
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
95583
95583
  };
95584
95584
  readBuildMetadata = () => {
95585
- const rawPackageVersion = "1.0.916";
95586
- const rawGitSha = "4a1ec9313556e7bbc5accd34b7bd90b4e6d7e877";
95585
+ const rawPackageVersion = "1.0.917";
95586
+ const rawGitSha = "d6a6e4bf28b445047916e6140058d2dff5024d70";
95587
95587
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
95588
95588
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
95589
95589
  return { packageVersion, gitSha };
@@ -127984,9 +127984,9 @@ var init_sentry = __esm({
127984
127984
  uncaughtExceptionMonitorInstalled = false;
127985
127985
  currentDevboxSentryUser = null;
127986
127986
  readBuildMetadata2 = () => {
127987
- const rawPackageVersion = "1.0.916";
127988
- const rawGitSha = "4a1ec9313556e7bbc5accd34b7bd90b4e6d7e877";
127989
- const rawSentryRelease = "boxes-dev-dvb@1.0.916+4a1ec9313556e7bbc5accd34b7bd90b4e6d7e877";
127987
+ const rawPackageVersion = "1.0.917";
127988
+ const rawGitSha = "d6a6e4bf28b445047916e6140058d2dff5024d70";
127989
+ const rawSentryRelease = "boxes-dev-dvb@1.0.917+d6a6e4bf28b445047916e6140058d2dff5024d70";
127990
127990
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
127991
127991
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
127992
127992
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -136816,7 +136816,7 @@ var init_packageVersion = __esm({
136816
136816
  return path17.join(process.cwd(), "dvb");
136817
136817
  };
136818
136818
  readEmbeddedPackageVersion = () => {
136819
- const raw = "1.0.916";
136819
+ const raw = "1.0.917";
136820
136820
  return trimVersion(raw);
136821
136821
  };
136822
136822
  readNearestPackageMetadata = (basePath) => {
package/dist/bin/dvbd.mjs CHANGED
@@ -92318,8 +92318,8 @@ var init_otel = __esm({
92318
92318
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
92319
92319
  };
92320
92320
  readBuildMetadata = () => {
92321
- const rawPackageVersion = "1.0.916";
92322
- const rawGitSha = "4a1ec9313556e7bbc5accd34b7bd90b4e6d7e877";
92321
+ const rawPackageVersion = "1.0.917";
92322
+ const rawGitSha = "d6a6e4bf28b445047916e6140058d2dff5024d70";
92323
92323
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
92324
92324
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
92325
92325
  return { packageVersion, gitSha };
@@ -124614,9 +124614,9 @@ var init_sentry = __esm({
124614
124614
  uncaughtExceptionMonitorInstalled = false;
124615
124615
  currentDevboxSentryUser = null;
124616
124616
  readBuildMetadata2 = () => {
124617
- const rawPackageVersion = "1.0.916";
124618
- const rawGitSha = "4a1ec9313556e7bbc5accd34b7bd90b4e6d7e877";
124619
- const rawSentryRelease = "boxes-dev-dvb@1.0.916+4a1ec9313556e7bbc5accd34b7bd90b4e6d7e877";
124617
+ const rawPackageVersion = "1.0.917";
124618
+ const rawGitSha = "d6a6e4bf28b445047916e6140058d2dff5024d70";
124619
+ const rawSentryRelease = "boxes-dev-dvb@1.0.917+d6a6e4bf28b445047916e6140058d2dff5024d70";
124620
124620
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
124621
124621
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
124622
124622
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130268,7 +130268,7 @@ var init_packageVersion = __esm({
130268
130268
  return path8.join(process.cwd(), "dvb");
130269
130269
  };
130270
130270
  readEmbeddedPackageVersion = () => {
130271
- const raw = "1.0.916";
130271
+ const raw = "1.0.917";
130272
130272
  return trimVersion(raw);
130273
130273
  };
130274
130274
  readNearestPackageMetadata = (basePath) => {
@@ -4,19 +4,33 @@ Use this doc when a user asks how to connect AWS, how AWS sign-in stays current,
4
4
  which account or role a project uses, what the `boxes-dev` profile means, or
5
5
  why a tool or container is not using the managed AWS identity.
6
6
 
7
- The AWS integration is currently available only to boxes.dev's internal pilot
8
- accounts. If AWS does not appear under **Integrations**, the account has not
9
- been enabled for the pilot.
7
+ AWS is enabled once for a boxes.dev team, then each team member connects their
8
+ own company identity and chooses the account and role for each project.
10
9
 
11
- ## Connect AWS
10
+ ## Enable AWS For A Team
12
11
 
13
- Open **Integrations → AWS** in the desktop app. Enter:
12
+ A team admin opens **Integrations → AWS** in the desktop app and chooses
13
+ **Set up AWS**. Enter:
14
14
 
15
- - the AWS access portal URL your company gives you, such as
15
+ - the AWS access portal URL the company provides, such as
16
16
  `https://example.awsapps.com/start`; and
17
- - the AWS region where your company configured IAM Identity Center, such as
17
+ - the AWS region where the company configured IAM Identity Center, such as
18
18
  `us-east-1`.
19
19
 
20
+ Starting the normal AWS sign-in validates these details before boxes.dev saves
21
+ them for the team. The admin then finishes company sign-in and chooses an
22
+ assigned account and role for the current project.
23
+
24
+ Until AWS accepts a team admin's setup request, members see an explanation
25
+ instead of a Connect control. They do not need to collect or enter the portal
26
+ URL and region themselves.
27
+
28
+ ## Connect AWS
29
+
30
+ After a team admin enables AWS, open **Integrations → AWS** in the desktop app.
31
+ The team's access portal and region appear as read-only details. Choose
32
+ **Connect AWS**.
33
+
20
34
  IAM Identity Center is the AWS sign-in your company uses. Continue to AWS,
21
35
  finish the normal company sign-in in the browser, and return to boxes.dev. The
22
36
  AWS page continues automatically, so it is safe to reload or reopen the app
@@ -28,15 +42,19 @@ project can reuse the same central sign-in and choose a different assigned
28
42
  account or role without another browser sign-in.
29
43
 
30
44
  AWS setup does not change the repository and does not require a Template box
31
- snapshot. Open a new terminal or start a new Codex or Claude session after
32
- connecting or changing the role. Already-running shells and agent processes
33
- keep the environment and credentials they started with.
45
+ snapshot. New terminals start with `AWS_PROFILE=boxes-dev`. Existing Codex and
46
+ Claude sessions keep current work running, then pick up AWS before their next
47
+ turn: boxes.dev refreshes their idle runtime after its work drains. This also
48
+ applies to Claude sessions opened from mobile. Already-running shells keep the
49
+ environment they started with, so open a new terminal after connecting,
50
+ changing, or removing AWS.
34
51
 
35
52
  ## How Tools Receive Credentials
36
53
 
37
54
  For a connected project, boxes.dev manages an AWS profile named `boxes-dev` on
38
- the Template box and its devboxes. New terminals and agent sessions select it
39
- with the normal AWS environment settings:
55
+ the Template box and its devboxes. New terminals and newly started or safely
56
+ refreshed managed agent processes select it with the normal AWS environment
57
+ settings:
40
58
 
41
59
  ```text
42
60
  AWS_PROFILE=boxes-dev
@@ -57,6 +75,14 @@ without repository changes. A quick check is:
57
75
  aws sts get-caller-identity
58
76
  ```
59
77
 
78
+ If the renewable AWS sign-in has ended, this command explains that AWS must be
79
+ reconnected and includes a boxes.dev link that opens the desktop app's AWS
80
+ integration page. The desktop and mobile apps also show an **AWS sign-in
81
+ expired.** banner with a **Reconnect AWS** action. Its X dismisses the local
82
+ warning without changing the AWS connection, and the warning can return in a
83
+ new app session while AWS still needs to be reconnected. On mobile, the action
84
+ opens the desktop handoff where AWS setup is available.
85
+
60
86
  The managed profile is a default, not a forced override. An explicit AWS CLI
61
87
  `--profile`, a different `AWS_PROFILE`, access-key environment variables, or a
62
88
  provider chosen directly in application code keeps AWS's normal precedence.
@@ -86,12 +112,21 @@ credentials.
86
112
  ## Change, Remove, Or Reconnect
87
113
 
88
114
  Use **Change role** to select another account and role for the current project.
89
- New terminals and agent sessions use the new choice after it reaches their
90
- machine. Existing processes can retain credentials only until AWS's expiration
91
- time.
115
+ New terminals use the new choice after it reaches their machine. Existing
116
+ Codex and Claude sessions preserve current work and pick up the change before
117
+ their next turn at the safe process boundary described above. Existing shells
118
+ and user-managed processes keep their prior environment; credentials already
119
+ held in any process can remain usable only until AWS's expiration time.
92
120
 
93
121
  If AWS asks for sign-in again, choose **Reconnect**. The existing project role
94
- selection is preserved while the new browser sign-in completes.
122
+ selection is preserved while the new browser sign-in completes. Reconnect uses
123
+ the team's current portal and region without asking the member to enter them.
124
+
125
+ Team admins can use **Team setup → Edit** to change the team's access portal or
126
+ Identity Center region. Continuing starts a new AWS sign-in for that admin and
127
+ updates the team settings after AWS accepts the device-authorization request.
128
+ Existing member connections keep their prior settings until those members
129
+ reconnect; an edit does not silently replace an in-use personal sign-in.
95
130
 
96
131
  The AWS options menu has two different removal actions:
97
132
 
@@ -106,6 +141,18 @@ credentials that AWS already issued. Those credentials remain usable only
106
141
  until their AWS expiration. Use the company's AWS administration and security
107
142
  controls when immediate AWS-side revocation is required.
108
143
 
144
+ ## Escalated Admin Access (Advanced)
145
+
146
+ The managed `boxes-dev` profile is the centrally maintained,
147
+ least-ceremony path for everyday project access. A team that occasionally
148
+ needs escalated access can add a separate AWS profile on a box, such as an
149
+ `admin` profile backed by its own `credential_process` command.
150
+
151
+ Keep that profile separate from `boxes-dev` and select it explicitly when
152
+ needed. boxes.dev never manages, refreshes, or overwrites profiles it did not
153
+ create, so the team remains responsible for that profile's command,
154
+ authentication, permissions, and lifecycle.
155
+
109
156
  ## Containers And Current Limits
110
157
 
111
158
  The first AWS integration applies to host-native terminals, Codex, Claude, the
@@ -119,4 +166,5 @@ sign-in or a refresh token out of boxes.dev as a workaround. Automatic
119
166
  container credential delivery is a separate future integration.
120
167
 
121
168
  The initial AWS integration supports one IAM Identity Center organization per
122
- boxes.dev user and one selected account/role per project.
169
+ boxes.dev team, one personal Identity Center sign-in per team member, and one
170
+ selected account/role per project for that member.
@@ -184,6 +184,10 @@ Select a thread in the left pane to open it in the detail pane. Codex threads,
184
184
  Claude Code threads, Claude Code CLI terminal-style threads, new-devbox
185
185
  placeholders, and automation views all use the same detail area.
186
186
 
187
+ To distinguish Claude and Codex threads at a glance, turn on **Show agent
188
+ logos** in **Settings > General > Thread List**. The logos appear at the right
189
+ edge of thread rows and are off by default.
190
+
187
191
  Thread rows can show unread or attention state. When a thread completes, fails,
188
192
  or asks for input while the app is not focused, boxes.dev can request desktop
189
193
  attention and, depending on settings, show a desktop notification.
@@ -75,6 +75,9 @@ Use this terminology consistently:
75
75
  - `aws.md`: central AWS IAM Identity Center sign-in, per-project account and
76
76
  role selection, the managed `boxes-dev` profile, credential precedence,
77
77
  refresh behavior, removal, and container limits.
78
+ - `tailscale.md`: team-managed tailnet setup, Tailscale-policy-based project
79
+ eligibility, tagged ephemeral devboxes, stock CLI behavior, native cleanup,
80
+ incident removal, and version-one limits.
78
81
  - `billing-and-limits.md`: plans, box-hours, awake runtimes, awake devbox
79
82
  limits, project limits, usage, overages, checkout, and billing portal
80
83
  behavior.
@@ -106,6 +106,35 @@ agent to ask before replacing a manual title. The command does not rename a
106
106
  provider-native Codex or Claude session and cannot clear or target another
107
107
  thread title.
108
108
 
109
+ ## Current-Box Public Links
110
+
111
+ An agent or shell script can create and remove an HTTPS public link for an
112
+ eligible HTTP app running on the current Template box or devbox:
113
+
114
+ ```bash
115
+ callback_url="$(dvb-onbox ports share --port 4000)"
116
+ dvb-onbox ports list-public
117
+ dvb-onbox ports stop-sharing --port 4000
118
+ ```
119
+
120
+ These commands take no project or machine selector. They act only on the
121
+ physical box where they run, and `list-public` returns only that box's active
122
+ links. Add `--json` to any command for structured output. A repeated `share`
123
+ returns the same active URL, while a repeated `stop-sharing` succeeds with
124
+ `revoked: false`.
125
+
126
+ Use `share` only after the exact port appears as a detected HTTP app. Prefer a
127
+ high, project-allowed application port. Never expose databases, agent or daemon
128
+ control ports, credential-bearing tools, unauthenticated admin surfaces, or
129
+ another sensitive/internal service. The command rejects excluded, undetected,
130
+ and non-HTTP ports rather than choosing a different port.
131
+
132
+ Anyone with the generated link can reach the app without signing in. Tell the
133
+ user that the URL is public before sharing it, and make sure the app itself is
134
+ appropriate for unauthenticated Internet access. Stopping the app makes the URL
135
+ unavailable but does not revoke it. Run `stop-sharing` as soon as the callback
136
+ or preview is no longer needed; stopping public sharing does not stop the app.
137
+
109
138
  ## Delegated Threads
110
139
 
111
140
  A user can allow agents on one exact Template box or devbox to create delegated
@@ -212,7 +241,8 @@ effort; changed arguments under the same key fail.
212
241
 
213
242
  This permission is deliberately narrow: `dvb-onbox` does not expose project
214
243
  inventory, devbox destruction or archive, generic lifecycle, arbitrary direct
215
- exec, services, or ports.
244
+ exec, services, or generic port and machine management. The current-box public
245
+ link commands above are its only port-control surface.
216
246
 
217
247
  ## Team Template Commands
218
248
 
@@ -117,11 +117,11 @@ a different port.
117
117
  For a detected HTTP port, hover its row and choose the **Share publicly**
118
118
  globe action to create an HTTPS public link for that exact port. Anyone with
119
119
  the link can use the application without signing in. After you confirm, the
120
- dialog shows the new link with a **Copy link** button. Public links do not depend on local forwarding, remain active
121
- when you select another devbox or close the desktop app, and stay in place
122
- until you stop sharing them. They do not wake a sleeping devbox: while the
123
- devbox sleeps, visitors see an unavailable page and the Ports menu marks the
124
- link as paused.
120
+ dialog shows the new link with a **Copy link** button. Public links do not
121
+ depend on local forwarding, remain active when you select another devbox or
122
+ close the desktop app, and stay in place until you stop sharing them. They do
123
+ not wake a sleeping devbox: while the devbox sleeps, visitors see an
124
+ unavailable page and the Ports menu marks the link as paused.
125
125
 
126
126
  The Ports button shows an active-link count. Open the Ports menu to copy,
127
127
  open, or stop sharing links from the selected port row. The **Public links**
@@ -131,6 +131,28 @@ stops that boxes.dev public URL and sharing the port again later creates a new
131
131
  URL. It does not stop the application or change another network path the
132
132
  application may expose.
133
133
 
134
+ Inside a managed Template box or devbox, a shell script or coding agent can
135
+ control the same public links for the physical current box:
136
+
137
+ ```bash
138
+ callback_url="$(dvb-onbox ports share --port 4000)"
139
+ dvb-onbox ports list-public
140
+ dvb-onbox ports stop-sharing --port 4000
141
+ ```
142
+
143
+ Each command also accepts `--json`. `share` prints only the HTTPS URL in plain
144
+ mode so scripts can capture it directly; `list-public` prints one tab-delimited
145
+ port and URL per line. There is no project or machine selector. The app must
146
+ already be detected as HTTP on that exact eligible port, and the commands do
147
+ not expose generic port forwarding or choose a replacement port.
148
+
149
+ The desktop and `dvb-onbox` use the same publication state. A link created in
150
+ either surface appears in the other, and either surface can stop sharing it.
151
+ Anyone with a public link can reach the app without signing in. Stop sharing
152
+ temporary links when they are no longer needed; stopping the app alone leaves
153
+ the link allocated and visible, although requests are unavailable until the app
154
+ returns.
155
+
134
156
  Choose **Configure port forwarding…** for project-level rules. The same
135
157
  configuration applies to the project's Template box and every devbox, while
136
158
  ordinary localhost forwarding follows the selected machine. Stable local URLs
@@ -85,6 +85,11 @@ boxes.dev account sign-in uses user-authorized sign-in services. The CLI and
85
85
  desktop app may keep local session credentials on the user's machine so they
86
86
  can connect to boxes.dev without signing in every time.
87
87
 
88
+ When signing up with Google, boxes.dev may send a six-digit code to the Google
89
+ account's email address before creating team or project access. This confirms
90
+ that the person signing in still controls an address that Google does not
91
+ authoritatively manage as Gmail or a managed Google Workspace account.
92
+
88
93
  Codex and Claude Code are connected by the user through browser login or API
89
94
  key, depending on the agent. boxes.dev runs the real agent tools the user
90
95
  authorizes; it does not replace them with a separate model account. If an agent
@@ -0,0 +1,120 @@
1
+ # Tailscale Integration
2
+
3
+ The Tailscale integration connects a project's devboxes to a team's tailnet as
4
+ tagged, ephemeral Tailscale devices. A team admin connects the tailnet once,
5
+ and each project owner verifies their own access before enabling the
6
+ integration for that project. No one signs in to Tailscale separately on each
7
+ devbox.
8
+
9
+ Tailscale is installed only on ordinary devboxes in enabled projects. It is not
10
+ installed on the project's Template box, so Template snapshots never contain a
11
+ Tailscale device identity.
12
+
13
+ ## Team Setup
14
+
15
+ A Tailscale admin first creates a tag for boxes.dev devices, commonly
16
+ `tag:boxes-dev`, and grants the intended users or groups access to that tag in
17
+ Tailscale policy. For example, a policy can let `group:engineering` access the
18
+ tag while leaving Marketing without access. Tailscale remains the source of
19
+ truth for these permissions; boxes.dev does not have a separate user allowlist.
20
+
21
+ The admin then creates a tag-scoped Tailscale OAuth client with these scopes:
22
+
23
+ - Auth Keys
24
+ - Devices Core
25
+ - Users read
26
+ - Policy File read
27
+ - Device Posture Attributes read
28
+
29
+ In boxes.dev Team Settings, the admin enters the Tailnet ID, OAuth client ID,
30
+ one-time-displayed client secret, and tag. boxes.dev validates the credential
31
+ before storing it. The OAuth secret is encrypted and never sent to a devbox.
32
+ For each enrollment, boxes.dev creates a short-lived, one-time, preauthorized
33
+ auth key for that exact attested devbox. The renewable OAuth credential stays
34
+ central.
35
+
36
+ The required read scopes let boxes.dev read the tailnet's full device and user
37
+ directories, access policy, and device posture attributes. Device mutations
38
+ and auth-key creation are restricted to the configured tag. Team Settings
39
+ discloses this access before the connection is saved.
40
+
41
+ ## Who Can Enable It
42
+
43
+ A project owner chooses **Verify Tailscale access** from the project's
44
+ Tailscale integration page. boxes.dev uses the team connection to confirm that:
45
+
46
+ - the user's verified boxes.dev email exactly matches an active, approved
47
+ email-based Tailscale login; and
48
+ - Tailscale policy gives that user, directly or through a group, effective
49
+ access to the configured tag.
50
+
51
+ This verification uses Tailscale's policy engine, so direct users, groups,
52
+ SCIM-synced groups, wildcards, and autogroups continue to be managed in
53
+ Tailscale. GitHub-only and passkey-only Tailscale login names are not supported
54
+ in version one because they do not expose an email that boxes.dev can match.
55
+
56
+ Posture-conditioned-only access fails closed. boxes.dev does not pretend that
57
+ a tagged devbox has the posture attributes of the user's personal device. The
58
+ admin must provide an unconditional effective path from that user or group to
59
+ the boxes.dev tag.
60
+
61
+ Access to the tag controls who can enable Tailscale for a project. Once it is
62
+ enabled, the tag's network access is available to anyone or any automation that
63
+ can run commands on that project's devboxes. Admins should separately control
64
+ who can use the project, its devboxes, and its automations.
65
+
66
+ Rules whose source is the boxes.dev tag control what connected devboxes can
67
+ reach inside the tailnet. This is separate from the user-or-group rule that
68
+ controls who may enable the integration.
69
+
70
+ ## Devbox Experience
71
+
72
+ After the project owner enables Tailscale, boxes.dev installs the pinned
73
+ official Tailscale client on its devboxes and enrolls them automatically when
74
+ they want to run. The ordinary `tailscale` CLI is available on the standard
75
+ socket. Users and scripts can use stock commands such as `tailscale status`,
76
+ `tailscale ping`, `tailscale down`, `tailscale up`, and `tailscale logout`.
77
+
78
+ `tailscale down` keeps the local device identity while disconnecting it.
79
+ `tailscale up` reconnects it. `tailscale logout` intentionally removes the
80
+ local identity and its ephemeral tailnet device; when the user later runs
81
+ `tailscale up`, boxes.dev automatically provisions a fresh identity without a
82
+ per-devbox login. A tightly chained `tailscale logout && tailscale up` can
83
+ briefly print Tailscale's normal login URL before managed enrollment catches
84
+ up. No one should visit that URL.
85
+
86
+ Devices are ephemeral. Sleeping a devbox does not immediately delete its
87
+ Tailscale device. Tailscale normally removes an inactive ephemeral device after
88
+ roughly 30 to 60 minutes, although the timing is provider-controlled and can be
89
+ longer. Waking before cleanup reconnects the same identity. Waking after cleanup
90
+ creates a fresh device, so its Tailscale IP and device identity can change.
91
+ boxes.dev does not maintain a node-slot pool or its own idle cleanup timer.
92
+
93
+ Disabling Tailscale for a project deletes its recorded Tailscale devices and
94
+ purges their local identities without waking sleeping devboxes. Destroying a
95
+ devbox also attempts exact cleanup but never blocks the devbox destroy if the
96
+ Tailscale API is temporarily unavailable. Native ephemeral cleanup remains the
97
+ backstop.
98
+
99
+ ## Removing Access in an Incident
100
+
101
+ Deleting an active boxes.dev device from Tailscale's Machines page disconnects
102
+ it immediately. boxes.dev does not silently recreate that active device. The
103
+ project's Tailscale row shows a red attention mark, and the project owner must
104
+ explicitly reconnect the affected devbox.
105
+
106
+ To prevent reconnect, disable Tailscale for the project or remove the project
107
+ owner's access to the configured tag. To stop every boxes.dev project, remove
108
+ the tag's network grants and disconnect the team integration or revoke its
109
+ OAuth client.
110
+
111
+ A sleeping device can disappear through normal ephemeral cleanup. That is not
112
+ treated as an incident deletion; it enrolls automatically with a fresh identity
113
+ when the devbox wakes.
114
+
115
+ ## Unsupported Tailnets
116
+
117
+ Tailnet Lock is not supported in version one. If boxes.dev detects it, the
118
+ integration fails closed, removes the attempted device, and displays:
119
+ **Tailnet Lock is enabled; contact boxes.dev for help finishing your setup.**
120
+ It does not keep retrying enrollment.
@@ -48,9 +48,10 @@ Admins create a Team Template from this collection. The default flow starts
48
48
  from GitHub: choose one or several existing repositories, or create a new
49
49
  repository on GitHub, then review their direct-child paths under
50
50
  `/home/boxes`. **Start empty** keeps the clean-machine flow available. GitHub
51
- setup requires the current desktop app because it securely copies this desktop
52
- account's reusable SSH key into the editing session. An interrupted setup can
53
- be continued from the template's card or detail page.
51
+ setup uses temporary boxes.dev GitHub App access limited to the selected
52
+ repositories while cloning them. It does not require SSH-key registration or a
53
+ desktop private-key transfer. An interrupted setup can be continued from the
54
+ template's card or detail page.
54
55
 
55
56
  The template's name and description can change later, but its machine size is
56
57
  fixed after creation and is inherited by projects made from it. Creating and
@@ -124,20 +125,20 @@ setup** in the creation flow; that failure does not block **Open project**.
124
125
 
125
126
  ## Git Access
126
127
 
127
- While an admin edits a Team Template in the desktop app, boxes.dev installs
128
- this desktop account's reusable GitHub SSH key into the editing session and
129
- verifies each detected GitHub remote with that exact key. If GitHub does not
130
- know the key yet, the setup flow shows its public key for manual
131
- registration. The same desktop key is reused across later editing sessions,
132
- so it normally needs to be registered only once, not once per checkout.
133
-
134
- The private key remains local to that desktop account and in the current
135
- editing session. Another admin uses their own desktop key; they never receive
136
- the template creator's private key. Browser editing remains available, but
137
- managed Git pull and push requires opening the template in a current desktop
138
- app. Before a Team Template release is captured, boxes.dev removes its managed
139
- key copy, host configuration, and credential-transfer staging from the editing
140
- session.
128
+ During GitHub-first creation, boxes.dev installs a short-lived GitHub App token
129
+ limited to the repositories selected in the review step, clones them over
130
+ token-free HTTPS remotes, and removes the token before the editor opens. No
131
+ admin SSH key is copied to the Team Template.
132
+
133
+ While an admin actively edits the Team Template, boxes.dev installs fresh
134
+ short-lived GitHub App access for those same selected repositories and refreshes
135
+ it before expiry. This supports authenticated fetch, pull, and push from
136
+ Terminal or the Git pane without exposing an admin's broader GitHub identity.
137
+ The App token is removed when editing pauses and restored after the admin wakes
138
+ the session; saving removes and verifies all managed Git access before release
139
+ capture. GitHub attributes remote operations to the boxes.dev App while Git
140
+ commit author metadata remains unchanged. Pushes that modify GitHub Actions
141
+ workflow files are not supported by this managed access.
141
142
 
142
143
  Existing repositories, remotes, multiple-repository layouts, and submodules
143
144
  are copied with the release. The destination project receives fresh boxes.dev
@@ -161,9 +162,10 @@ in the environment—including `.env` files, databases, shell history, or
161
162
  custom SSH and cloud credentials—are copied into every project created from
162
163
  the release.
163
164
 
164
- The desktop SSH key that boxes.dev manages for Team Template Git access is
165
- removed automatically before release capture. This does not cover SSH keys or
166
- credentials that an admin installs manually outside that managed path.
165
+ The short-lived GitHub App token used during setup is removed after cloning.
166
+ The separate short-lived token used during editing is removed on pause and
167
+ before release capture. This does not cover SSH keys or credentials that an
168
+ admin installs manually.
167
169
 
168
170
  Review the editing session and the save warning before publishing. Configure a
169
171
  release cleanup script in the template's settings when the team intentionally
@@ -315,6 +315,26 @@ confirmed settings follow the thread when it is reopened or resumed on desktop
315
315
  or mobile. Changing one thread does not change another existing thread; the
316
316
  last-used selection can still become the starting default for a new thread.
317
317
 
318
+ On a connected managed Claude Code thread, the desktop and mobile composers
319
+ also offer these modes when the runtime supports switching them:
320
+
321
+ - **Full-access** is the standard boxes.dev mode and the default for every new
322
+ thread. Claude works in the isolated Template box or devbox without ordinary
323
+ edit and command approval prompts.
324
+ - **Auto** uses Claude's safety checks and may still block an operation or ask
325
+ for permission. It appears only for models that report Auto support, and
326
+ Claude can return the thread to Manual if Auto becomes unavailable.
327
+ - **Manual** allows reads normally while edits and commands use Claude's
328
+ ordinary permission prompts.
329
+ - **Plan** lets Claude inspect and propose changes without editing project files
330
+ until the user approves leaving plan mode.
331
+
332
+ The last confirmed Full-access, Auto, or Manual choice belongs to that thread
333
+ and survives reconnects and agent restarts. Plan temporarily overlays that base
334
+ choice, so leaving Plan restores the prior mode. While a mode change is being
335
+ confirmed, the selector and Send action stay disabled so a prompt cannot run
336
+ under the previous mode.
337
+
318
338
  Claude Code can switch a Fable thread to Opus when Fable's safeguards decline
319
339
  part of the conversation and Claude retries it with a fallback model. The
320
340
  transcript shows a **Switched to Opus 4.8** notice with a link to Anthropic's
@@ -333,11 +353,12 @@ Native Claude Code transcripts do not expire after 30 days on managed Template
333
353
  boxes and devboxes. They remain on the owning machine until boxes.dev
334
354
  intentionally moves them to cold storage or that machine is destroyed.
335
355
 
336
- When Claude Code enters plan mode, the desktop and mobile composers show
337
- **Plan mode** while Claude is planning without changing project files. When
338
- Claude is ready to leave plan mode, its **Exit plan mode** approval offers
339
- **Allow** or **Deny**; denying keeps the thread in plan mode, while allowing
340
- lets Claude return to implementation work.
356
+ When Claude Code enters plan mode, the desktop and mobile mode control shows
357
+ **Plan** while Claude is planning without changing project files. An older
358
+ connected runtime can show the passive label **Plan mode** instead. When Claude
359
+ is ready to leave plan mode, its **Exit plan mode** approval offers **Allow** or
360
+ **Deny**; denying keeps the thread in plan mode, while allowing lets Claude
361
+ return to implementation work.
341
362
 
342
363
  Claude Code may ask the user structured questions. The question card can show
343
364
  choice answers, multi-select answers, and skip options. Every Claude-authored
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.916",
3
+ "version": "1.0.917",
4
4
  "type": "module",
5
5
  "license": "UNLICENSED",
6
6
  "imports": {
@@ -79,5 +79,5 @@
79
79
  "e2b": "^2.18.0",
80
80
  "ink-testing-library": "^4.0.0"
81
81
  },
82
- "devboxReleasedAt": "2026-08-08T01:28:38Z"
82
+ "devboxReleasedAt": "2026-08-09T17:49:03Z"
83
83
  }