@boxes-dev/dvb-runtime 1.0.1027 → 1.0.1029

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.
@@ -60,9 +60,11 @@ Fill in every section marked `TODO(agent)`. Each has a guide:
60
60
 
61
61
  For GitHub repos, the manifest defaults to `githubAccess: managed` and keeps
62
62
  the seeded GitHub `gitSsh` rows in skip mode. If check says GitHub is not
63
- connected, run `dvb agent-init github connect`, have the user finish in the
64
- browser, and then re-run check. If the boxes.dev GitHub App is missing
65
- repository access or needs an update, follow the exact action printed by check.
63
+ connected, or that the boxes.dev GitHub App can't access a repository, run
64
+ `dvb agent-init github connect`, have the user finish in the browser, and then
65
+ re-run check. Once GitHub is connected, that command opens GitHub and prints
66
+ which account the user should choose. If an installation needs an update,
67
+ follow the exact action printed by check.
66
68
  Set `githubAccess: ssh` and the GitHub `gitSsh` rows to setup only when the user
67
69
  chooses the SSH alternative. GitLab and other origins continue to use their
68
70
  seeded `gitSsh` entries.
@@ -17,9 +17,10 @@ gitSsh:
17
17
 
18
18
  Managed access uses the user's existing boxes.dev GitHub connection for the
19
19
  Template box and future devboxes. If needed, run `dvb agent-init github
20
- connect`, let the user finish in the browser, and rerun `check`. Check also
21
- prints the exact GitHub action when a repo is not covered, is not writable, or
22
- an installation needs updated access. Do not put any returned URL, connection
20
+ connect`, let the user finish in the browser, and rerun `check`. When a repo
21
+ is not covered by the boxes.dev GitHub App, the same command opens the
22
+ GitHub page that grants access. Check prints the exact GitHub action when a
23
+ repo is not writable or an installation needs updated access. Do not put any returned URL, connection
23
24
  id, repository id, or token in the manifest. Managed access can push changes
24
25
  under `.github/workflows` after every affected installation accepts the shown
25
26
  update. Keep the GitHub `gitSsh` rows at `mode: skip` and
package/dist/bin/dvb.mjs CHANGED
@@ -1,6 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
 
3
- !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="b4d75a4b-c5e3-5e9c-8629-a7af77ccf4b0")}catch(e){}}();
3
+ !function(){try{var e="undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof globalThis?globalThis:"undefined"!=typeof self?self:{},n=(new e.Error).stack;n&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[n]="635ddc0b-9426-57b3-b255-3ff5f3c561ff")}catch(e){}}();
4
4
  import { createRequire as __dvbCreateRequire } from "node:module";
5
5
  import { dirname as __dvbDirname } from "node:path";
6
6
  import { fileURLToPath as __dvbFileURLToPath } from "node:url";
@@ -101146,8 +101146,8 @@ var init_otel = __esm({
101146
101146
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
101147
101147
  };
101148
101148
  readBuildMetadata = () => {
101149
- const rawPackageVersion = "1.0.1027";
101150
- const rawGitSha = "b1de1456a00a8cf396a793db03b3095cf40cf93a";
101149
+ const rawPackageVersion = "1.0.1029";
101150
+ const rawGitSha = "d1b49ee678f8f6b87482cf591ef5e12198f6f032";
101151
101151
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
101152
101152
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
101153
101153
  return { packageVersion, gitSha };
@@ -133553,9 +133553,9 @@ var init_sentry = __esm({
133553
133553
  uncaughtExceptionMonitorInstalled = false;
133554
133554
  currentDevboxSentryUser = null;
133555
133555
  readBuildMetadata2 = () => {
133556
- const rawPackageVersion = "1.0.1027";
133557
- const rawGitSha = "b1de1456a00a8cf396a793db03b3095cf40cf93a";
133558
- const rawSentryRelease = "boxes-dev-dvb@1.0.1027+b1de1456a00a8cf396a793db03b3095cf40cf93a";
133556
+ const rawPackageVersion = "1.0.1029";
133557
+ const rawGitSha = "d1b49ee678f8f6b87482cf591ef5e12198f6f032";
133558
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1029+d1b49ee678f8f6b87482cf591ef5e12198f6f032";
133559
133559
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
133560
133560
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
133561
133561
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -138773,7 +138773,7 @@ var init_packageVersion = __esm({
138773
138773
  return path17.join(process.cwd(), "dvb");
138774
138774
  };
138775
138775
  readEmbeddedPackageVersion = () => {
138776
- const raw = "1.0.1027";
138776
+ const raw = "1.0.1029";
138777
138777
  return trimVersion(raw);
138778
138778
  };
138779
138779
  readNearestPackageMetadata = (basePath) => {
@@ -313513,7 +313513,7 @@ var init_databaseDumpTools2 = __esm({
313513
313513
  });
313514
313514
 
313515
313515
  // src/devbox/agentInit/controlPlane.ts
313516
- var preflightProject, registryUpsert2, registryRemove, startOrResumeJob, createUploadSession, refreshMultipartUploadParts, listMultipartUploadedParts, completeMultipartUpload, abortMultipartUpload, commitUpload, commitDecryptKeyEnvelope, getProgress, destroyStartOver, retryRecoverableFailure, getMarkerRepairState, getGithubConnection, startGithubConnection, setGithubCliAccess, listGithubRepositories, createAgentInitControlPlaneClient;
313516
+ var preflightProject, registryUpsert2, registryRemove, startOrResumeJob, createUploadSession, refreshMultipartUploadParts, listMultipartUploadedParts, completeMultipartUpload, abortMultipartUpload, commitUpload, commitDecryptKeyEnvelope, getProgress, destroyStartOver, retryRecoverableFailure, getMarkerRepairState, getGithubConnection, startGithubConnection, setGithubCliAccess, listGithubRepositories, getGithubInstallTarget, createAgentInitControlPlaneClient;
313517
313517
  var init_controlPlane2 = __esm({
313518
313518
  "src/devbox/agentInit/controlPlane.ts"() {
313519
313519
  "use strict";
@@ -313549,6 +313549,7 @@ var init_controlPlane2 = __esm({
313549
313549
  startGithubConnection = makeFunctionReference("githubOAuth:startConnectionForViewer");
313550
313550
  setGithubCliAccess = makeFunctionReference("githubConnections:setRuntimeGhProjectionForViewer");
313551
313551
  listGithubRepositories = makeFunctionReference("githubRepositoryActions:listRepositoriesForViewer");
313552
+ getGithubInstallTarget = makeFunctionReference("githubRepositoryActions:getInstallTargetForViewer");
313552
313553
  createAgentInitControlPlaneClient = ({
313553
313554
  getToken
313554
313555
  }) => {
@@ -313583,6 +313584,10 @@ var init_controlPlane2 = __esm({
313583
313584
  getGithubConnection: (request2) => query(getGithubConnection, request2),
313584
313585
  startGithubConnection: (request2) => mutation(startGithubConnection, request2),
313585
313586
  listGithubRepositories: (request2) => action(listGithubRepositories, request2),
313587
+ getGithubInstallTarget: async (request2) => withConvexClient(
313588
+ await getToken(),
313589
+ async (client) => client.action(getGithubInstallTarget, request2)
313590
+ ),
313586
313591
  setGithubCliAccess: async (request2) => withConvexClient(
313587
313592
  await getToken(),
313588
313593
  async (client) => client.mutation(setGithubCliAccess, request2)
@@ -323241,11 +323246,32 @@ var init_instanceType = __esm({
323241
323246
  });
323242
323247
 
323243
323248
  // src/devbox/agentInit/githubAccess.ts
323244
- var isRecord8, githubIssue, githubInventoryFailureIssue, readAgentInitProjectLayoutRepos, manifestGithubAccess, buildAgentInitGithubManifestIssues, normalizeInventoryRepository, normalizeInventoryInstallation, matchAgentInitGithubRepositories, agentInitGithubBlockedIssue, resolveAgentInitGithubAccessDefault, resolveAgentInitManagedGithubAccess, configureAgentInitGithubAccess;
323249
+ var resolveAgentInitGithubAccessPage, isRecord8, githubIssue, githubInventoryFailureIssue, readAgentInitProjectLayoutRepos, manifestGithubAccess, buildAgentInitGithubManifestIssues, normalizeInventoryRepository, normalizeInventoryInstallation, matchAgentInitGithubRepositories, agentInitGithubBlockedIssue, resolveAgentInitGithubAccessDefault, resolveAgentInitManagedGithubAccess, configureAgentInitGithubAccess;
323245
323250
  var init_githubAccess = __esm({
323246
323251
  "src/devbox/agentInit/githubAccess.ts"() {
323247
323252
  "use strict";
323248
323253
  init_devboxCore();
323254
+ resolveAgentInitGithubAccessPage = (missingAccess) => {
323255
+ const owners = [
323256
+ ...new Set(
323257
+ missingAccess.repositoryFullNames.map(
323258
+ (fullName) => fullName.split("/")[0]?.toLowerCase() ?? ""
323259
+ )
323260
+ )
323261
+ ].filter((owner) => owner.length > 0);
323262
+ const ownerLogin = owners.length === 1 ? missingAccess.repositoryFullNames[0]?.split("/")[0] ?? null : null;
323263
+ if (!ownerLogin) {
323264
+ return { kind: "install", url: missingAccess.appInstallationUrl };
323265
+ }
323266
+ const installation = missingAccess.installations.find(
323267
+ (candidate) => candidate.accountLogin.toLowerCase() === ownerLogin.toLowerCase()
323268
+ );
323269
+ return installation ? {
323270
+ kind: "installation_settings",
323271
+ ownerLogin,
323272
+ url: installation.managementUrl
323273
+ } : { kind: "owner_lookup", ownerLogin };
323274
+ };
323249
323275
  isRecord8 = (value) => typeof value === "object" && value !== null && !Array.isArray(value);
323250
323276
  githubIssue = (message, fix) => ({
323251
323277
  level: "error",
@@ -323578,8 +323604,16 @@ var init_githubAccess = __esm({
323578
323604
  ok: false,
323579
323605
  issue: githubIssue(
323580
323606
  `boxes.dev does not have GitHub App repository access for: ${missing.join(", ") || "this project"}.`,
323581
- appInstallationUrl ? `Choose the personal account or organization at ${appInstallationUrl} and grant repository access. An organization owner may need to approve the request. Then re-run check.` : "Grant the boxes.dev GitHub App access to each listed repository. An organization owner may need to approve the request. Then re-run check."
323582
- )
323607
+ "Run `dvb agent-init github connect` to open GitHub and give boxes.dev access to each listed repository. An organization owner may need to approve the request. Then re-run check."
323608
+ ),
323609
+ missingAccess: {
323610
+ appInstallationUrl,
323611
+ installations: installations.map(({ accountLogin, managementUrl }) => ({
323612
+ accountLogin,
323613
+ managementUrl
323614
+ })),
323615
+ repositoryFullNames: missing
323616
+ }
323583
323617
  };
323584
323618
  }
323585
323619
  const installationById = new Map(
@@ -324883,10 +324917,12 @@ var init_gitSsh = __esm({
324883
324917
  });
324884
324918
 
324885
324919
  // src/devbox/commands/agentInit/github.ts
324886
- var GITHUB_USAGE, startAgentInitGithubConnection, runAgentInitGithub, manageAgentInitGithubCliAccess;
324920
+ var GITHUB_USAGE, startAgentInitGithubConnection, runAgentInitGithub, isGithubConnectionReady, readInstallUrl, connectAgentInitGithub, manageAgentInitGithubCliAccess;
324887
324921
  var init_github = __esm({
324888
324922
  "src/devbox/commands/agentInit/github.ts"() {
324889
324923
  "use strict";
324924
+ init_commandCore();
324925
+ init_githubAccess();
324890
324926
  init_service();
324891
324927
  init_browser();
324892
324928
  init_errors4();
@@ -324928,9 +324964,94 @@ var init_github = __esm({
324928
324964
  });
324929
324965
  return;
324930
324966
  }
324931
- await startAgentInitGithubConnection({
324932
- client: context35.controlPlaneClient
324967
+ await connectAgentInitGithub({
324968
+ client: context35.controlPlaneClient,
324969
+ loadProjectLayoutRepos: async () => {
324970
+ const { repo, validation } = await resolveAgentInitProject({
324971
+ projectPath: process.cwd()
324972
+ });
324973
+ return readAgentInitProjectLayoutRepos({ repo, validation });
324974
+ }
324975
+ });
324976
+ };
324977
+ isGithubConnectionReady = (connectionResult) => {
324978
+ if (!connectionResult || typeof connectionResult !== "object") return false;
324979
+ const connection = connectionResult.connection;
324980
+ if (!connection || typeof connection !== "object") return false;
324981
+ const fields = connection;
324982
+ return fields["connectionStatus"] === "connected" && fields["tokenStatus"] === "valid" && fields["authorizationStatus"] === "current" && fields["credentialUpgradeStatus"] !== "update_available";
324983
+ };
324984
+ readInstallUrl = (result) => {
324985
+ if (!result || typeof result !== "object") return null;
324986
+ const fields = result;
324987
+ if (fields["ok"] !== true) return { ok: false };
324988
+ return {
324989
+ ok: true,
324990
+ accountType: fields["accountType"],
324991
+ installUrl: typeof fields["installUrl"] === "string" ? fields["installUrl"] : null
324992
+ };
324993
+ };
324994
+ connectAgentInitGithub = async ({
324995
+ client,
324996
+ loadProjectLayoutRepos,
324997
+ openBrowserFn = openBrowser,
324998
+ print = console.log
324999
+ }) => {
325000
+ const connectionResult = await client.getGithubConnection({});
325001
+ if (!isGithubConnectionReady(connectionResult)) {
325002
+ await startAgentInitGithubConnection({ client, openBrowserFn, print });
325003
+ return;
325004
+ }
325005
+ const resolution = resolveAgentInitManagedGithubAccess({
325006
+ connectionResult,
325007
+ inventoryResult: await client.listGithubRepositories({}),
325008
+ projectLayoutRepos: await loadProjectLayoutRepos()
324933
325009
  });
325010
+ if (resolution.ok) {
325011
+ print(
325012
+ `GitHub is connected and boxes.dev can access ${resolution.repositories.length === 1 ? "this project's repository" : `all ${resolution.repositories.length} of this project's repositories`}. Re-run \`dvb agent-init check\`.`
325013
+ );
325014
+ return;
325015
+ }
325016
+ if (!("missingAccess" in resolution)) {
325017
+ print(resolution.issue.message);
325018
+ print(resolution.issue.fix);
325019
+ return;
325020
+ }
325021
+ const page = resolveAgentInitGithubAccessPage(resolution.missingAccess);
325022
+ const repositories = resolution.missingAccess.repositoryFullNames.join(", ");
325023
+ let url3;
325024
+ let instruction;
325025
+ if (page.kind === "installation_settings") {
325026
+ url3 = page.url;
325027
+ instruction = `Add ${repositories} to the boxes.dev GitHub App for @${page.ownerLogin}, then re-run \`dvb agent-init check\`.`;
325028
+ } else if (page.kind === "install") {
325029
+ url3 = page.url;
325030
+ instruction = `Give boxes.dev access to ${repositories} on GitHub for each account that owns them. An organization owner may need to approve the request. Then re-run \`dvb agent-init check\`.`;
325031
+ } else {
325032
+ const target = readInstallUrl(
325033
+ await client.getGithubInstallTarget({ ownerLogin: page.ownerLogin })
325034
+ );
325035
+ if (target?.ok && target.installUrl === null) {
325036
+ print(
325037
+ `${repositories} belongs to @${page.ownerLogin}'s personal account. Ask @${page.ownerLogin} to give boxes.dev access to it on GitHub, or use \`githubAccess: ssh\`.`
325038
+ );
325039
+ return;
325040
+ }
325041
+ url3 = target?.ok ? target.installUrl : resolution.missingAccess.appInstallationUrl;
325042
+ instruction = target?.ok && target.accountType === "user" ? `Give boxes.dev access to ${repositories} on GitHub: keep "All repositories" selected, or choose repositories that include them. Then re-run \`dvb agent-init check\`.` : `Give boxes.dev access to ${repositories} on GitHub: choose @${page.ownerLogin}, then keep "All repositories" selected or choose repositories that include them. If @${page.ownerLogin} requires an owner's approval, GitHub will send your request to an organization owner. If @${page.ownerLogin} isn't listed, ask an owner of @${page.ownerLogin} to give boxes.dev access. Then re-run \`dvb agent-init check\`.`;
325043
+ }
325044
+ if (url3 === null) {
325045
+ print(instruction);
325046
+ return;
325047
+ }
325048
+ if (openBrowserFn(url3)) {
325049
+ print("GitHub opened in your browser.");
325050
+ } else {
325051
+ print("The browser did not open. Continue on GitHub at:");
325052
+ print(url3);
325053
+ }
325054
+ print(instruction);
324934
325055
  };
324935
325056
  manageAgentInitGithubCliAccess = async ({
324936
325057
  client,
@@ -359890,4 +360011,4 @@ react/cjs/react-jsx-runtime.development.js:
359890
360011
  *)
359891
360012
  */
359892
360013
 
359893
- //# debugId=b4d75a4b-c5e3-5e9c-8629-a7af77ccf4b0
360014
+ //# debugId=635ddc0b-9426-57b3-b255-3ff5f3c561ff
package/dist/bin/dvbd.mjs CHANGED
@@ -96328,8 +96328,8 @@ var init_otel = __esm({
96328
96328
  return trimmed && trimmed.length > 0 ? trimmed : void 0;
96329
96329
  };
96330
96330
  readBuildMetadata = () => {
96331
- const rawPackageVersion = "1.0.1027";
96332
- const rawGitSha = "b1de1456a00a8cf396a793db03b3095cf40cf93a";
96331
+ const rawPackageVersion = "1.0.1029";
96332
+ const rawGitSha = "d1b49ee678f8f6b87482cf591ef5e12198f6f032";
96333
96333
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
96334
96334
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
96335
96335
  return { packageVersion, gitSha };
@@ -128624,9 +128624,9 @@ var init_sentry = __esm({
128624
128624
  uncaughtExceptionMonitorInstalled = false;
128625
128625
  currentDevboxSentryUser = null;
128626
128626
  readBuildMetadata2 = () => {
128627
- const rawPackageVersion = "1.0.1027";
128628
- const rawGitSha = "b1de1456a00a8cf396a793db03b3095cf40cf93a";
128629
- const rawSentryRelease = "boxes-dev-dvb@1.0.1027+b1de1456a00a8cf396a793db03b3095cf40cf93a";
128627
+ const rawPackageVersion = "1.0.1029";
128628
+ const rawGitSha = "d1b49ee678f8f6b87482cf591ef5e12198f6f032";
128629
+ const rawSentryRelease = "boxes-dev-dvb@1.0.1029+d1b49ee678f8f6b87482cf591ef5e12198f6f032";
128630
128630
  const packageVersion = typeof rawPackageVersion === "string" ? rawPackageVersion : void 0;
128631
128631
  const gitSha = typeof rawGitSha === "string" ? rawGitSha : void 0;
128632
128632
  const sentryRelease = typeof rawSentryRelease === "string" ? rawSentryRelease : void 0;
@@ -130826,7 +130826,7 @@ var init_packageVersion = __esm({
130826
130826
  return path8.join(process.cwd(), "dvb");
130827
130827
  };
130828
130828
  readEmbeddedPackageVersion = () => {
130829
- const raw = "1.0.1027";
130829
+ const raw = "1.0.1029";
130830
130830
  return trimVersion(raw);
130831
130831
  };
130832
130832
  readNearestPackageMetadata = (basePath) => {
@@ -10,8 +10,8 @@ runtime.
10
10
  The workbench has a few persistent areas:
11
11
 
12
12
  - The top bar is split at the left pane's edge. The left pane's own top area
13
- shows the project selector, a back button, and a usage icon (billing usage
14
- details on hover, when relevant). The back button retraces earlier workbench
13
+ shows the project selector, a back button, a thread search button, and a
14
+ usage icon (billing usage details on hover, when relevant). The back button retraces earlier workbench
15
15
  selections, so an integration or automation detour can return to the thread
16
16
  you were viewing. It is disabled until there is somewhere to return. The
17
17
  content pane's title bar starts with runtime status, metrics, and ports when
@@ -39,6 +39,28 @@ can be resized. Showing Terminal reattaches the runtime's open terminal
39
39
  sessions, or starts one if it has none, and closing the last terminal tab
40
40
  closes the pane.
41
41
 
42
+ ## Accounts
43
+
44
+ The desktop app can stay signed in to more than one boxes.dev account, such as
45
+ a personal account and a work account. Open the account menu at the bottom of
46
+ the left pane to see the other signed-in accounts, and click one to switch. The
47
+ workbench reloads as that account and opens its last project; there is no new
48
+ sign-in. **Add another account** opens Google sign-in in your browser while the
49
+ current account stays open, then switches to the new account once sign-in
50
+ finishes.
51
+
52
+ **Log out** (or **Sign Out** in the app menu) signs out only the current
53
+ account. If another account is still signed in, the app switches to it, and
54
+ deleting the current account from the Account page does the same. When an
55
+ account's session expires, the sign-in screen offers **Continue as** buttons
56
+ for the accounts that are still signed in. A newly added account that has no
57
+ project yet opens first-run setup; the account email at the top right of the
58
+ setup screen offers the same switch, add, and log out choices.
59
+
60
+ Desktop notifications, the unread count, ports, and terminals follow the
61
+ account that is open. Switching accounts requires a current desktop app
62
+ version; older versions do not show the other accounts.
63
+
42
64
  ## Right-Click Menus
43
65
 
44
66
  Most workbench surfaces have right-click menus, and each shows the same
@@ -298,6 +320,31 @@ contributes to the Dock unread count when **Unread badge** is enabled. Desktop
298
320
  attention is broader than unread thread state: for example, a configured
299
321
  terminal bell can request attention without adding an unread thread.
300
322
 
323
+ ## Search Your Threads
324
+
325
+ The search button (a magnifying glass) beside the back button opens thread
326
+ search. It searches the text of your own Codex and Claude threads across all
327
+ of your projects, including archived threads, threads on sleeping machines,
328
+ and threads kept in cold storage. Searching never wakes a machine.
329
+
330
+ Search covers your messages and each agent's final replies. Progress
331
+ updates, tool activity and output, and attachments are not included. A new
332
+ message becomes searchable a few seconds after the agent's reply finishes,
333
+ and a busy thread can briefly drop out of results while its latest messages
334
+ are indexed. A deleted thread leaves the results as soon as you delete it.
335
+
336
+ Results show one row per thread, most relevant first, with the thread title,
337
+ the project, who wrote the matching message, and a highlighted excerpt. Use
338
+ the arrow keys and **Enter**, or click a row, to open that thread in its
339
+ project.
340
+
341
+ Team admins also see threads they started on a Team Template's editing
342
+ machine. Opening one of those opens the Team Template editor when you have an
343
+ editing session running, and the Team Template's page otherwise.
344
+
345
+ Search includes only threads you own. Conversations that teammates shared
346
+ with you are not included.
347
+
301
348
  ## Files And Git
302
349
 
303
350
  The Files and Git/Review segments in the titlebar open panes for the selected
@@ -429,7 +476,7 @@ Invalid policy never authorizes a new path.
429
476
 
430
477
  ## Updates And Feedback
431
478
 
432
- Open Help in the desktop sidebar, then **Help center**, for the logged-in
479
+ Open Help in the desktop sidebar, then **Help center**, for the public
433
480
  human guides at `https://boxes.dev/help`. It opens in the external browser and
434
481
  keeps the working conversation in the desktop app. The existing quick fixes
435
482
  and Send feedback action remain in the Help dialog.
@@ -110,7 +110,8 @@ Use devbox threads for normal coding tasks.
110
110
 
111
111
  Setup asks you to connect at least one coding agent. You can connect or repair
112
112
  agent auth later from the desktop app. On macOS, open the boxes.dev app menu and
113
- choose **Configure agents...**.
113
+ choose **Configure agents...**. The mobile app has the same controls under
114
+ **Settings → Agent accounts**.
114
115
 
115
116
  Codex can be connected with ChatGPT login or an API key. Claude Code can be
116
117
  connected with Claude login or an API key. Configure agents can keep multiple
@@ -61,7 +61,9 @@ Linear.
61
61
 
62
62
  After the workspace is connected and your Linear identity is linked, open the
63
63
  desktop workbench's **Integrations** section and choose **Create automation**
64
- for Linear. boxes.dev creates your **Default behavior** in a paused state. Use
64
+ for Linear. boxes.dev creates your **Default behavior** in a paused state,
65
+ using the project's new-thread agent, or the coding agent you set up if you use
66
+ only one, with that agent's saved model and reasoning level. Use
65
67
  **Configure** to choose Codex or Claude Code and edit the automation prompt,
66
68
  then choose **Activate**. The integration home also shows recent runs and one
67
69
  clear recovery action when the workspace, identity, or default behavior needs
@@ -121,18 +121,36 @@ template does not share its value objects.
121
121
  A Team Template-managed project follows the current Team Template definitions
122
122
  and Team values. Each member's values belong only to that member's exact
123
123
  project. Members can replace, remove, reveal, copy, or export their own project
124
- values, but cannot add centrally managed files or rows in this first version.
125
- Team admins cannot read member values.
124
+ values. Team admins cannot read member values.
125
+
126
+ A member can also add their own variables in **Project settings → Environment
127
+ files**: in a file the Team Template manages, or in a new file of their own
128
+ with **Add a file**. They reach all of that member's devboxes in the project
129
+ and nobody else's. When a member's file and a Team Template file use the same
130
+ path, both share one managed section, with the team's rows first. A member
131
+ cannot add a name the Team Template already sets in that file. If the team adds
132
+ that name later, the team's row wins and the member's variable is left out of
133
+ the file until the member renames or removes it. A member's own file cannot use
134
+ a path the Team Template uses for a member file.
126
135
 
127
136
  If an admin changes where a Member value will be written by renaming it or
128
137
  moving its file, boxes.dev omits the old saved value. The member must review the
129
138
  new destination and choose **Use saved value here**, or enter a replacement.
130
139
  Other managed values continue syncing while that one is unresolved.
131
140
 
141
+ ## Agent Commands
142
+
143
+ Coding agents can list, set, and remove a project's variables with
144
+ `dvb-onbox env`, and a team admin's agent can define Team and Member values with
145
+ `dvb-onbox team-template env`. Agents on devboxes need a 3-hour permission for
146
+ their thread, and no command returns saved values. See
147
+ [Environment variables](onbox-agent-tools.md#environment-variables).
148
+
132
149
  ## Sync And Outages
133
150
 
134
151
  Managed files reconcile when a Template box or devbox starts or wakes, when a
135
- change is observed, and during periodic retry. Changing a value does not wake a
152
+ saved change is observed (usually within seconds), and during a periodic retry
153
+ about once a minute. Changing a value does not wake a
136
154
  paused machine. A failure in one file does not stop other files from updating.
137
155
 
138
156
  If boxes.dev, its key service, or the network is temporarily unavailable, an
@@ -24,6 +24,16 @@ website, which works entirely from a phone.
24
24
  The app remembers the last project you opened and can take you back there on the
25
25
  next launch.
26
26
 
27
+ The app can stay signed in to more than one boxes.dev account. In Settings, tap
28
+ **Add account with Google** (or **Add account with Apple** on iPhone) to sign
29
+ in another account; the current account stays open until the new one is ready,
30
+ and closing the sign-in window changes nothing. Settings lists the other
31
+ signed-in accounts under **Signed in as**, and tapping one switches to it
32
+ without signing in again. **Sign out** signs out only the current account and
33
+ opens the next signed-in account, if any. If an account's session ends, the
34
+ sign-in screen offers **Continue as** buttons for the accounts that are still
35
+ signed in.
36
+
27
37
  If the app cannot finish checking your account because it cannot reach
28
38
  boxes.dev, it shows **Can’t connect** and keeps trying automatically. Restore
29
39
  your internet connection or use **Try again**; you do not need to force-quit
@@ -231,13 +241,22 @@ while the app is running. Older installed notification links continue to open
231
241
  through the owning project. The mobile app icon badge can show unread thread
232
242
  count for the signed-in device.
233
243
 
244
+ When several accounts are signed in, the phone receives notifications from all
245
+ of them. A notification for an account other than the one open appears even
246
+ while the app is in use, and tapping it switches to that account before opening
247
+ the thread. The app icon badge counts unread threads across the signed-in
248
+ accounts. An account starts receiving notifications on a phone after it has
249
+ been opened there once.
250
+
234
251
  Use mobile settings to turn the unread badge on or off.
235
252
 
236
253
  ## Settings
237
254
 
238
255
  Mobile settings include:
239
256
 
240
- - account sign-in and sign-out;
257
+ - account sign-in and sign-out, adding another account, and switching between
258
+ signed-in accounts;
259
+ - **Agent accounts**, for the Codex and Claude accounts your devboxes use;
241
260
  - billing usage summary;
242
261
  - an invite link and QR code you can share with someone who wants to try
243
262
  boxes.dev (the same link is on the Account page in the web app);
@@ -245,8 +264,8 @@ Mobile settings include:
245
264
  - theme, monospace font, and thread text size;
246
265
  - release package details and refresh controls in installed builds;
247
266
  - account deletion.
248
- - a Help center link that opens `https://boxes.dev/help` in the browser, where
249
- normal boxes.dev sign-in is required.
267
+ - a Help center link that opens the public guides at `https://boxes.dev/help`
268
+ in the browser.
250
269
 
251
270
  Someone opening your invite link can sign up with Google in their phone
252
271
  browser. After signing up on a phone, they will see that setup happens on
@@ -262,6 +281,30 @@ Account deletion permanently deletes your boxes.dev account, projects,
262
281
  personal Template boxes, and devboxes. Team Templates belong to the team and
263
282
  are not deleted with one member's account. The deletion cannot be undone.
264
283
 
284
+ ### Agent Accounts
285
+
286
+ **Settings → Agent accounts** manages the same Codex and Claude accounts as
287
+ Configure agents in the desktop app. Each agent has its own list of saved
288
+ logins and API keys, and the checked row is the one your devboxes use. Tap
289
+ **Add** beside an agent to sign in or save an API key. Tap a saved row to
290
+ choose **Use this account**, **Re-authenticate** or **Edit API key**, **Check
291
+ now**, or **Remove**.
292
+
293
+ To sign in to Codex, tap **Log in with ChatGPT**. The app shows a one-time
294
+ code, and **Open ChatGPT** copies it and opens the ChatGPT device sign-in page.
295
+ Sign in there if asked and paste the code. Codex will connect after you
296
+ approve, even if you finish in another browser.
297
+
298
+ To sign in to Claude Code, tap **Log in with Claude**, then **Open Claude** and
299
+ approve access. Claude will show a code; copy it, return to the app, paste it,
300
+ and tap **Continue**. Closing either sign-in cancels it.
301
+
302
+ When the active Codex or Claude account needs you to sign in again, or its API
303
+ key was rejected, a banner appears at the top of the app. **Reconnect** opens
304
+ that agent's sign-in, or opens Agent accounts when both agents need attention
305
+ or a key needs replacing. Dismissing the banner hides it until the app restarts
306
+ or another account starts failing.
307
+
265
308
  ## Mobile Versus Desktop
266
309
 
267
310
  Use desktop for setup, full project orientation, file upload/download workflows,
@@ -269,5 +312,6 @@ Git staging and commits, port forwarding, runtime process inspection, and
269
312
  detailed review.
270
313
 
271
314
  Use mobile when you want to monitor progress, answer questions, send a quick
272
- follow-up, take a Template-box snapshot, inspect a linked file or diff, open a
273
- shell, sleep or destroy a devbox, or check billing/status away from the desktop.
315
+ follow-up, reconnect a Codex or Claude account, take a Template-box snapshot,
316
+ inspect a linked file or diff, open a shell, sleep or destroy a devbox, or
317
+ check billing/status away from the desktop.
@@ -134,6 +134,45 @@ to write files on the Template box. `snapshot` waits for the new snapshot that
134
134
  future devboxes will use. Take one only when the user wants the change to reach
135
135
  future devboxes. Ordinary shell commands still act on the current devbox.
136
136
 
137
+ ## Environment Variables
138
+
139
+ An agent can list, set, and remove the centrally managed environment variables
140
+ of the current project. See
141
+ [Managed environment files](managed-environment-files.md) for how these files
142
+ reach machines.
143
+
144
+ ```bash
145
+ dvb-onbox env list --json
146
+ dvb-onbox env set --file .env.local --name API_BASE_URL --value https://api.example.test
147
+ printf %s "$TOKEN" | dvb-onbox env set --file .env.local --name API_TOKEN --value-stdin
148
+ dvb-onbox env remove --file .env.local --name API_TOKEN
149
+ ```
150
+
151
+ What these commands change depends on the project:
152
+
153
+ - In a project with its own Template box, they edit the project's variables.
154
+ On the Template box they need no extra permission. On a devbox, the current
155
+ thread needs the `edit-template-box` permission.
156
+ - In a Team Template project, they edit the user's own variables: values for
157
+ Member rows the team defined, and variables the user added to any file.
158
+ Team values belong to the team and cannot be changed here. The current
159
+ thread needs `edit-personal-environment`, or `edit-team-template` for a team
160
+ admin.
161
+
162
+ `--file` is relative to the folder the result reports as `pathBase`.
163
+ `set` replaces the variable if it exists, adds it if it doesn't, and creates
164
+ the managed file if boxes.dev does not manage that path yet. An existing file's
165
+ other content stays below the managed section, so remove an old line with the
166
+ same name from the file yourself, on this machine and on the Template box when
167
+ future devboxes should not have it. Bringing an existing file under management
168
+ with a review of its current lines is done in **Project settings →
169
+ Environment files**.
170
+
171
+ `--value-stdin` reads the value from standard input and drops one trailing
172
+ newline. `list` returns names, where each value comes from, and whether a value
173
+ is saved; it never returns values. Saved changes reach running machines within
174
+ about a minute. After an uncertain response, run `list` before retrying.
175
+
137
176
  ## Devbox Lifecycle And Template Maintenance
138
177
 
139
178
  From the project's current ordinary Template box, an agent can inspect and edit
@@ -242,8 +281,9 @@ The request values are `create-devboxes-and-threads`,
242
281
  `move-devboxes-to-folders`, `create-devbox-folders`,
243
282
  `edit-devbox-lifecycle`, `edit-template-maintenance`, `destroy-devbox`,
244
283
  `read-project-threads`, `read-user-threads`, `read-shared-threads`,
245
- `read-team-threads`, `edit-template-box`, and `edit-team-template`. Add
246
- `--json` for a stable structured result.
284
+ `read-team-threads`, `message-agents`, `edit-template-box`,
285
+ `edit-team-template`, and `edit-personal-environment`. Add `--json` for a
286
+ stable structured result.
247
287
 
248
288
  The command creates one request for the exact managed thread and source box,
249
289
  then waits up to ten minutes while the owner sees **Deny**, **Allow**, and,
@@ -253,18 +293,25 @@ for every agent on that source box until the owner turns it off; it is not a
253
293
  one-operation grant. **Deny** declines this request without changing permission
254
294
  settings. An agent cannot answer its own request.
255
295
 
256
- `edit-template-box` and `edit-team-template` work differently. They let only
257
- the agent in the requesting thread edit the Template its devbox came from, and
296
+ `edit-template-box`, `edit-team-template`, and `edit-personal-environment`
297
+ work differently. They apply only to the agent in the requesting thread, and
258
298
  the owner sees **Deny** and **Allow for 3 hours**. The grant expires 3 hours
259
299
  after approval. Other threads and boxes never receive it, and no Agent
260
300
  permissions switch or project setting can enable it. Request
261
- `edit-template-box` from a devbox in a project with its own Template box.
262
- Request `edit-team-template` from a devbox in a Team Template project; only a
263
- team admin can receive it. After the grant expires, the next command reports
264
- the missing permission and the agent needs a new request.
265
-
266
- For thread reads, folder access, thread titles, and creating devboxes and threads, the owner
267
- can choose **Always allow for project** directly.
301
+ `edit-template-box` from a devbox in a project with its own Template box to
302
+ edit that Template box and the project's environment variables. Request
303
+ `edit-team-template` from a devbox in a Team Template project to edit that
304
+ Team Template, including its environment variables; only a team admin can
305
+ receive it. Request `edit-personal-environment` from a devbox in a Team
306
+ Template project to edit the user's own environment variables for that
307
+ project; any member can receive it, and a thread that already has
308
+ `edit-team-template` does not need it. A thread holds one of these grants at a
309
+ time. After the grant expires, the next command reports the missing permission
310
+ and the agent needs a new request.
311
+
312
+ For thread reads, agent messaging, folder access, thread titles, and creating
313
+ devboxes and threads, the owner can choose **Always allow for project**
314
+ directly.
268
315
  This will enable the project's shared permission and make the requesting box
269
316
  use it. All existing and future devboxes will follow that setting, except
270
317
  those configured separately. Other devboxes will keep their individual
@@ -657,6 +704,50 @@ If a needed scope reports `thread_read_access_disabled`, request the matching
657
704
  `read-team-threads` permission. Team visibility limits require a team setting
658
705
  change; an agent permission cannot override them.
659
706
 
707
+ ## Message Other Agents
708
+
709
+ With **Message other agents** enabled in Agent permissions, an agent can send a
710
+ short message to another Codex or Claude thread in the same project, on the
711
+ same devbox or a different one, and receive messages in return. The setting
712
+ applies to every agent on the box. It is off by default, inherits the project's
713
+ setting, and can be overridden on a box. Both the sender's and the recipient's
714
+ boxes need it.
715
+
716
+ ```bash
717
+ dvb-onbox threads message --to <thread-id> \
718
+ --message "The endpoint now returns 422 for invalid widgets." --json
719
+ ```
720
+
721
+ `--to` takes a boxes.dev thread ID, such as one named in a received message,
722
+ one returned by `dvb-onbox threads start`, or one from
723
+ `dvb-onbox threads list --scope project`. Use this command rather than a
724
+ built-in agent messaging tool such as Claude's SendMessage, which cannot
725
+ address boxes.dev thread IDs or reach Codex and other devboxes, and may hold a
726
+ message until the recipient's user approves it. Messages are limited to 4 KiB;
727
+ point to files or threads for longer material. Only a managed agent thread can send,
728
+ so the recipient can reply. Sending will start an idle agent and wake the
729
+ recipient's devbox if it's asleep, which uses compute and model usage. An
730
+ active agent reads the message at its next opportunity in its current work.
731
+
732
+ The recipient's Codex or Claude receives the message from another agent, not
733
+ as user input. The message names the sender's thread and the command for
734
+ replying. It cannot answer a pending permission prompt or question for the
735
+ user. The user sees it in the recipient's thread as a message from the sending
736
+ agent, linked to the sender's thread.
737
+
738
+ A successful result means the recipient accepted the message; it does not mean
739
+ the agent has read, acted on, or answered it. Replies arrive later as messages
740
+ in the sender's thread. After `operation_indeterminate`, do not send the
741
+ message again, because it may already have arrived. A Claude agent in a
742
+ terminal that is busy or controlled by the user cannot receive messages
743
+ (`thread_busy` or `thread_controlled_elsewhere`); an idle, unattended terminal
744
+ session can. The recipient must be a started, unarchived thread in the same
745
+ project; messaging teammates or other projects is not available.
746
+
747
+ If sending reports `messaging_disabled`, request `message-agents`.
748
+ `recipient_messaging_disabled` means the recipient's devbox has messaging off;
749
+ only the user can change that, in that devbox's Agent permissions.
750
+
660
751
  ## Destroy And Archive The Current Devbox
661
752
 
662
753
  An agent can request destruction of its own ordinary devbox with:
@@ -950,6 +1041,34 @@ destination approval. See [Member files](member-managed-files.md) for upload
950
1041
  and delivery behavior. These commands return definitions only and do not
951
1042
  upload or read a member's file contents.
952
1043
 
1044
+ ### Team Template environment variables
1045
+
1046
+ An admin can define the Team Template's environment variables from the same
1047
+ places as member-file requirements, or from a member devbox whose thread has
1048
+ the `edit-team-template` permission. A member devbox does not need an open
1049
+ editing session for these commands.
1050
+
1051
+ ```bash
1052
+ dvb-onbox team-template env list --json
1053
+ dvb-onbox team-template env set --file sandbox/.env.local --name LOG_LEVEL --value debug
1054
+ dvb-onbox team-template env set --file sandbox/.env.local --name OPENAI_API_KEY \
1055
+ --member --instructions 'Create a key at platform.openai.com.'
1056
+ dvb-onbox team-template env set --file sandbox/.env.local --name SENTRY_DSN \
1057
+ --member --optional
1058
+ dvb-onbox team-template env remove --file sandbox/.env.local --name LOG_LEVEL
1059
+ ```
1060
+
1061
+ Paths are relative to `/home/boxes`. `--value` or `--value-stdin` saves a Team
1062
+ value that every member project receives. `--member` asks each member for their
1063
+ own value instead, required unless `--optional` is added, with optional
1064
+ `--instructions`. Switching a variable from Team to Member deletes its Team
1065
+ value. From an ordinary Template box, add `--template <team-template-id>`.
1066
+
1067
+ Changes take effect without saving a new Team Template version. Existing member
1068
+ projects receive Team values within about a minute. A new required Member value
1069
+ does not block existing devboxes; members will see it as needed in **Project
1070
+ settings → Environment files**.
1071
+
953
1072
  ### Create a Team Template from this project
954
1073
 
955
1074
  A team admin can ask an agent on an ordinary project's Template box to create
@@ -1223,5 +1342,6 @@ Save only when the user asked to publish the change. `save` uses the normal
1223
1342
  verified save pipeline, waits for it to finish, and ends this thread's access
1224
1343
  to that editing session. Access also ends when the grant expires or an admin
1225
1344
  saves the session in the desktop app. To make more changes, run `open` again
1226
- with a new key. Member-file requirements and Team Template creation are not
1227
- available from a devbox.
1345
+ with a new key. The **Team Template environment variables** commands above
1346
+ work from a member devbox without `open`. Member-file requirements and Team
1347
+ Template creation are not available from a devbox.
@@ -55,7 +55,12 @@ belong to their project and do not appear as separate projects in this list.
55
55
 
56
56
  The desktop local-folder setup wizard usually moves through these stages:
57
57
 
58
- 1. Account: sign in to boxes.dev.
58
+ 1. Account: sign in to boxes.dev, then optionally connect GitHub and Slack on
59
+ **Connect your accounts**. GitHub here is sign-in only; boxes.dev asks for
60
+ repository access later, once it knows the project's repositories. Team
61
+ admins on a team without a Slack workspace see **Connect Slack** to install
62
+ it, anyone on a team with a workspace can link their Slack account, and
63
+ other members see no Slack row. Neither connection is required to continue.
59
64
  2. Agents: connect Codex or Claude Code. At least one connected coding agent is
60
65
  required before the first project can start.
61
66
  3. Project: choose the local project folder and project name.
@@ -91,10 +96,17 @@ included repository is writable and covered by the boxes.dev GitHub App. When
91
96
  automatic GitHub access is selected, the Template box and future devboxes use
92
97
  HTTPS push/pull access without registering an SSH key. This is the default for
93
98
  a fresh GitHub-origin setup even when GitHub still needs to be connected or its
94
- access needs to be updated. If repository access is missing, GitHub lets the
95
- user choose the personal account or organization that owns it; an organization
96
- owner may need to approve the request. If the repository belongs to a different
97
- GitHub account, setup names the owner and provides instructions to send them.
99
+ access needs to be updated. If boxes.dev can't access the account that owns a
100
+ repository yet, setup shows **Connect your GitHub repositories**. For the
101
+ user's own personal account, its **Connect on GitHub** button opens GitHub with
102
+ that account already selected and **All repositories** chosen. For an
103
+ organization, it opens GitHub's account list and asks the user to choose the
104
+ organization; GitHub lists only organizations the user belongs to. If an
105
+ organization requires an owner's approval, GitHub sends the member's request to
106
+ an organization owner. Setup also offers a request message to send to an owner,
107
+ for members waiting on approval and for users who aren't in the organization.
108
+ If the repository belongs to another person's personal account, setup names the
109
+ owner and provides instructions to send them.
98
110
  If GitHub requires an access update, setup keeps automatic access selected and
99
111
  shows the affected **Update GitHub access** link or links; setup cannot continue
100
112
  until the update is accepted. The user can instead choose **Use an SSH key for
@@ -192,7 +204,10 @@ version 3 manifest with everything detectable. A standard GitHub origin seeds
192
204
  managed access without waiting for connection or repository inventory; the
193
205
  manifest can instead select SSH or skip Git access. If GitHub is not connected,
194
206
  `dvb agent-init github connect` opens the existing boxes.dev GitHub connection
195
- flow. `dvb agent-init check` verifies the exact writable repositories, App
207
+ flow. Once GitHub is connected, the same command opens the GitHub page that
208
+ gives the boxes.dev GitHub App access to the project's repositories: the
209
+ owner's installation settings, or the install page with the owning account
210
+ selected. `dvb agent-init check` verifies the exact writable repositories, App
196
211
  visibility, and current GitHub access before a managed launch; when an update
197
212
  is required, it prints the exact GitHub action and the SSH alternative. `dvb
198
213
  agent-init run` executes the whole plan — encrypted bundle, upload, Template
@@ -250,7 +265,8 @@ Setup asks the user to connect at least one coding agent:
250
265
 
251
266
  Users can connect both, but only one is required to start. If auth was skipped
252
267
  for one agent, or if auth later breaks, use Configure agents in the desktop app
253
- to add another account or API key, choose the active credential, edit an API
268
+ or **Settings → Agent accounts** in the mobile app to add another account or API
269
+ key, choose the active credential, edit an API
254
270
  key, re-auth, remove a saved credential, or disconnect an agent. The active
255
271
  Codex and Claude choices are independent and apply globally across the user's
256
272
  devboxes. On macOS, Configure agents is in the boxes.dev app menu.
@@ -26,8 +26,10 @@ channels where the app is available and in 1:1 app DMs.
26
26
  ## Connect Slack
27
27
 
28
28
  Open the desktop workbench's **Integrations** section and choose **Connect**
29
- for Slack. Team admins can also connect Slack from **Team Settings**. Slack
30
- opens an authorization screen; choose the workspace and allow the app.
29
+ for Slack. Team admins can also connect Slack from **Team Settings**, or from
30
+ the **Account** step of first-run desktop setup when their team has no Slack
31
+ workspace yet. Slack opens an authorization screen; choose the workspace and
32
+ allow the app.
31
33
 
32
34
  After Slack redirects back, the Slack integration home continues through the
33
35
  remaining setup steps: link your identity, create your automation, and activate
@@ -48,8 +50,9 @@ step is still needed.
48
50
 
49
51
  You can link by:
50
52
 
51
- - choosing **Connect Slack** on the getting-started page before you set up your
52
- first project, when your team already has a connected Slack workspace;
53
+ - choosing **Connect Slack** on the **Account** step of first-run desktop setup
54
+ or on the website's getting-started page, when your team already has a
55
+ connected Slack workspace;
53
56
  - using **Find my Slack account** in the automation editor;
54
57
  - opening the boxes.dev app DM in Slack and sending `connect`;
55
58
  - following a connect link sent by a team admin from Team Settings.
@@ -67,6 +70,15 @@ then choose **Activate**. The integration home also shows recent runs and
67
70
  surfaces one recovery action if the workspace, identity, or default behavior
68
71
  needs attention.
69
72
 
73
+ A new **Default behavior** uses the project's new-thread agent, or the coding
74
+ agent you set up if you use only one, with that agent's saved model and
75
+ reasoning level. When a project's setup finishes and you have linked Slack but
76
+ have no active Slack default, the desktop workbench shows **Start threads from
77
+ Slack** above the project with the agent, model, and reasoning level it will
78
+ use. **Turn on** creates and activates the Default behavior, **Configure**
79
+ creates it paused and opens it for review, and **Not now** hides the prompt
80
+ for that project.
81
+
70
82
  Your default Slack receiver runs when you mention `@boxes.dev` without a named
71
83
  command. Each mention starts an agent thread on a fresh devbox and appears in
72
84
  the main thread list alongside other devbox threads.
@@ -123,8 +123,12 @@ must be ready before work can start.
123
123
  ## Agent Auth Problems
124
124
 
125
125
  If a Codex or Claude thread cannot start or continue because auth is
126
- missing or expired, open **Configure agents** from the desktop app and reconnect
127
- the affected agent.
126
+ missing or expired, reconnect the affected agent from **Configure agents** in
127
+ the desktop app or **Settings → Agent accounts** in the mobile app. When the
128
+ active Codex or Claude account needs attention, the mobile app shows a banner
129
+ at the top of the screen. Its **Reconnect** action opens that agent's sign-in,
130
+ or opens Agent accounts when both agents need attention or an API key was
131
+ rejected.
128
132
 
129
133
  If Claude's sign-in page shows a temporary error while boxes.dev is waiting,
130
134
  use the provider page's retry action. boxes.dev keeps waiting for the sign-in
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.1027",
3
+ "version": "1.0.1029",
4
4
  "type": "module",
5
5
  "license": "UNLICENSED",
6
6
  "imports": {
@@ -77,5 +77,5 @@
77
77
  "e2b": "^2.18.0",
78
78
  "ink-testing-library": "^4.0.0"
79
79
  },
80
- "devboxReleasedAt": "2026-09-26T19:00:13Z"
80
+ "devboxReleasedAt": "2026-09-27T01:10:35Z"
81
81
  }