@boxes-dev/dvb-runtime 1.0.963 → 1.0.965

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.
@@ -89,6 +89,27 @@ project folder but rebuilds the setup state and bundle.
89
89
  If billing failed during setup, open billing, add or update the payment method,
90
90
  then retry setup.
91
91
 
92
+ ## Team Template Member Project Is Not Ready
93
+
94
+ A Team Template member project must confirm required GitHub repository access
95
+ and prepare at least one real devbox before it can open. If it shows **GitHub
96
+ access needs review**, use **Review GitHub access**, reconnect the intended
97
+ GitHub account or grant the boxes.dev App access to every named repository, and
98
+ then retry. boxes.dev does not switch to an older Team Template saved version
99
+ or to SSH for this project type.
100
+
101
+ If **Devbox setup needs attention** appears, ask a team admin to review and save
102
+ the Team Template. A team-owned startup-script failure discards that machine;
103
+ repeated failures pause automatic preparation instead of looping forever.
104
+ Members cannot rerun an administrator-controlled script after automatic
105
+ preparation pauses. Existing devboxes remain usable when preparing new ones has
106
+ a problem.
107
+
108
+ Optional setup such as an MCP connection can warn without blocking the first
109
+ thread. Follow the warning's own sign-in or retry action. GitHub access needed
110
+ for the tracked repositories and the selected coding agent's authentication
111
+ must be ready before work can start.
112
+
92
113
  ## Agent Auth Problems
93
114
 
94
115
  If a Codex or Claude thread cannot start or continue because auth is
@@ -116,10 +137,10 @@ connected through Claude login or an API key. After reconnecting, retry the
116
137
  thread or start a new one.
117
138
 
118
139
  If an MCP server needs auth, open **Integrations → MCPs** and use the agent chip
119
- on that connection. MCP servers installed directly on the Template box are under
120
- **Template-managed MCPs** in the same place, and that list is read from the
121
- current project's Template box. If sign-in fails, follow the recovery message
122
- on that MCP's card.
140
+ on that connection. In a project with a Template box, MCP servers installed
141
+ directly there are under **Template-managed MCPs** in the same place. Team
142
+ Template member projects omit that inventory. If sign-in fails, follow the
143
+ recovery message on that MCP's card.
123
144
 
124
145
  Older desktop app versions may provide a `dvb mcp authorize` command instead of
125
146
  opening sign-in. Run that command in a terminal on your own computer, never in
@@ -152,8 +173,8 @@ continue from the current state instead of replaying the turn automatically.
152
173
  ## Devbox Will Not Start Or Wake
153
174
 
154
175
  Devbox starts can fail because billing blocks compute, the awake devbox limit is
155
- reached, the selected snapshot is unavailable, or the runtime could not be
156
- prepared.
176
+ reached, the selected snapshot or Team Template saved version is unavailable,
177
+ or the runtime could not be prepared.
157
178
 
158
179
  Sometimes a devbox fails to start because the underlying infrastructure provider
159
180
  is temporarily slow or unavailable. This is usually recoverable. Retry
@@ -260,19 +281,21 @@ the switch is unavailable, finish the shown GitHub reconnect step first. An
260
281
  older machine may need to finish its boxes.dev update before managed `gh`
261
282
  commands become available.
262
283
 
263
- When the setting is on, do not repair authentication by running `gh auth
264
- login`, `gh auth logout`, `gh auth refresh`, or `gh auth switch`; manage that
265
- identity from boxes.dev. When the setting is off, or GitHub is not connected to
266
- boxes.dev, `gh` uses its ordinary local configuration and environment instead,
267
- including any user-managed authentication already on the machine. Disabling
268
- GitHub CLI does not disable automatic Git fetch, pull, or push for a project
269
- that uses that separate access method.
284
+ When the setting is on and the current project's repository access is ready,
285
+ do not repair authentication by running `gh auth login`, `gh auth logout`, `gh
286
+ auth refresh`, or `gh auth switch`; manage that identity from boxes.dev. When
287
+ the setting is off, GitHub is not connected to boxes.dev, or the App cannot
288
+ access a known repository in this project, `gh` uses its ordinary local
289
+ configuration and environment instead. In the missing-access case, it is safe
290
+ to run `gh auth login` on that machine. Disabling GitHub CLI does not disable
291
+ automatic Git fetch, pull, or push for a project that uses that separate access
292
+ method.
270
293
 
271
294
  If a repository or API request is still rejected while `gh` is enabled, use
272
295
  **Manage repository access** to confirm that the boxes.dev GitHub App can reach
273
- the repository and reconnect GitHub if its permissions changed. GitHub CLI can
274
- only use repositories and operations available to both the connected user and
275
- the App.
296
+ the repository and reconnect GitHub if its permissions changed. boxes.dev
297
+ issues no managed CLI token to that project until every known repository is
298
+ available to both the connected user and the App.
276
299
 
277
300
  ## Billing Or Limit Blocks
278
301
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boxes-dev/dvb-runtime",
3
- "version": "1.0.963",
3
+ "version": "1.0.965",
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-08-29T21:21:18Z"
80
+ "devboxReleasedAt": "2026-08-30T18:29:00Z"
81
81
  }