@boxes-dev/dvb-runtime 1.0.1104 → 1.0.1106
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/agent-init-guides/app.md +6 -5
- package/dist/agent-init-guides/flow.md +36 -12
- package/dist/agent-init-guides/git-ssh.md +9 -4
- package/dist/agent-init-guides/untracked.md +2 -1
- package/dist/bin/dvb.mjs +1216 -1829
- package/dist/bin/dvbd.mjs +6 -6
- package/dist/product-docs/references/agent-tools.md +32 -5
- package/dist/product-docs/references/cli.md +6 -4
- package/dist/product-docs/references/core-concepts.md +1 -1
- package/dist/product-docs/references/desktop-workbench.md +22 -3
- package/dist/product-docs/references/environment-setup-validation.md +22 -0
- package/dist/product-docs/references/files-git-and-review.md +29 -16
- package/dist/product-docs/references/fork-workflows.md +3 -2
- package/dist/product-docs/references/getting-started.md +2 -1
- package/dist/product-docs/references/index.md +2 -1
- package/dist/product-docs/references/linear.md +15 -0
- package/dist/product-docs/references/mobile.md +6 -1
- package/dist/product-docs/references/onbox-agent-tools.md +221 -61
- package/dist/product-docs/references/ports-terminal-and-runtime.md +5 -3
- package/dist/product-docs/references/project-setup.md +33 -17
- package/dist/product-docs/references/security-and-data.md +3 -2
- package/dist/product-docs/references/threads-and-agents.md +17 -4
- package/dist/product-docs/references/troubleshooting.md +7 -5
- package/dist/prompts/local-services-scan.md +3 -4
- package/package.json +2 -2
|
@@ -423,8 +423,9 @@ project that uses that separate access method.
|
|
|
423
423
|
|
|
424
424
|
If a repository or API request is still rejected while `gh` is enabled, use
|
|
425
425
|
**Manage repository access** to check App access, and reconnect GitHub if the
|
|
426
|
-
page requests it. If your organization cannot approve the App, choose
|
|
427
|
-
personal access**
|
|
426
|
+
page requests it. If your organization cannot approve the App, choose
|
|
427
|
+
**Connect personal access** under **GitHub CLI access** and authorize the
|
|
428
|
+
official GitHub CLI. Personal access is
|
|
428
429
|
also available when App repository access works but a command needs broader
|
|
429
430
|
permissions. Without personal access, boxes.dev checks that the App can reach
|
|
430
431
|
every known project repository before issuing its credential. With personal
|
|
@@ -459,7 +460,7 @@ its original error if the command is denied.
|
|
|
459
460
|
|
|
460
461
|
For issue changes or publishing check results, ask the installation owner to
|
|
461
462
|
approve Issues and Checks read and write, then retry. The App also requests
|
|
462
|
-
read-only access to deployments
|
|
463
|
+
read-only access to deployments. Reading the user's
|
|
463
464
|
account email addresses requires that user's approval of the updated GitHub
|
|
464
465
|
authorization. Choose **Update connection** in **Account** or **Integrations →
|
|
465
466
|
GitHub** to review and approve it.
|
|
@@ -472,8 +473,9 @@ optional personal access may provide the required permission. Do not change
|
|
|
472
473
|
credentials automatically after a command fails.
|
|
473
474
|
|
|
474
475
|
To let `gh` use the user's own GitHub permissions, connect optional personal
|
|
475
|
-
access. In **
|
|
476
|
-
|
|
476
|
+
access. In **Integrations → GitHub**, choose **Connect personal access** under
|
|
477
|
+
**GitHub CLI access**; in **Account** settings, choose **Connect** under
|
|
478
|
+
**Personal GitHub CLI access (optional)**. Alternatively, run `gh auth login`
|
|
477
479
|
on the Template box or devbox. It will print a one-time code and a GitHub
|
|
478
480
|
approval URL, then wait until the user approves with the GitHub account
|
|
479
481
|
connected to boxes.dev. An agent that runs it should give the user the code and
|
|
@@ -29,7 +29,7 @@ Important requirements (read carefully):
|
|
|
29
29
|
What to find:
|
|
30
30
|
|
|
31
31
|
- `appEntrypoints`: the primary command(s) a developer runs from the project root to start the app locally (long-running dev servers, watchers, "run the app" commands). If local dev requires multiple terminals (e.g. "backend" + "frontend"), include each as a separate entry with a clear description.
|
|
32
|
-
- `backgroundServices`: supporting services expected to be running for local dev (database, cache, queue, search, object storage emulator, auth emulator, etc). Prefer the repo's canonical way to start them (compose, just, make, scripts). `httpPort` is
|
|
32
|
+
- `backgroundServices`: supporting services expected to be running for local dev (database, cache, queue, search, object storage emulator, auth emulator, etc). Prefer the repo's canonical way to start them (compose, just, make, scripts). `httpPort` is the port an HTTP service listens on; for non-HTTP services (Postgres/Redis/etc), use `null` even if they expose other ports.
|
|
33
33
|
|
|
34
34
|
Minimum evidence to gather (run these, plus anything else you need):
|
|
35
35
|
|
|
@@ -80,8 +80,7 @@ How to decide what to output (avoid noise):
|
|
|
80
80
|
- Example: if `npm run dev` already starts the backend process, do not also list that backend command as a background service.
|
|
81
81
|
- Every background-service `name` must be a unique machine identifier matching `^[A-Za-z0-9._-]+$`. Use names such as `postgres`, `atlas-local`, or `pubsub_emulator`; do not use spaces, parentheses, or human-readable annotations.
|
|
82
82
|
- Every `command` must contain only the exact executable shell command. Never append explanations or parenthetical notes to the command string.
|
|
83
|
-
- For compose-defined background dependencies,
|
|
84
|
-
- `docker compose up -d <service>` (or `docker-compose up -d <service>` if that's what's documented)
|
|
83
|
+
- For compose-defined background dependencies, use the compose command the repo documents for starting them.
|
|
85
84
|
- Do not invent service names; use names found in compose files / docs.
|
|
86
85
|
- For background services started via just/make/task, use those commands (for example: `just db`, `make redis`, `task up`), but only if present and documented in the repo.
|
|
87
86
|
|
|
@@ -99,6 +98,6 @@ Return JSON with this shape:
|
|
|
99
98
|
- backgroundServices: [{ name, command, httpPort }]
|
|
100
99
|
- name must be a unique machine identifier matching `^[A-Za-z0-9._-]+$` (e.g. "postgres" or "atlas-local")
|
|
101
100
|
- command must be the exact executable command string to start the service, without commentary
|
|
102
|
-
- httpPort is the HTTP port
|
|
101
|
+
- httpPort is the service's HTTP port, or null if not applicable/unknown
|
|
103
102
|
|
|
104
103
|
Return only JSON that matches the provided schema.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@boxes-dev/dvb-runtime",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1106",
|
|
4
4
|
"description": "Runtime for the boxes.dev CLI. Install @boxes-dev/dvb to use the CLI.",
|
|
5
5
|
"homepage": "https://boxes.dev",
|
|
6
6
|
"type": "module",
|
|
@@ -77,5 +77,5 @@
|
|
|
77
77
|
"e2b": "^2.18.0",
|
|
78
78
|
"ink-testing-library": "^4.0.0"
|
|
79
79
|
},
|
|
80
|
-
"devboxReleasedAt": "2026-10-
|
|
80
|
+
"devboxReleasedAt": "2026-10-27T18:50:12Z"
|
|
81
81
|
}
|