@boxes-dev/dvb-runtime 1.0.1073 → 1.0.1075
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/agent-config.md +10 -2
- package/dist/agent-init-guides/flow.md +52 -14
- package/dist/agent-init-guides/manifest.md +7 -2
- package/dist/bin/dvb.mjs +3608 -2988
- package/dist/bin/dvbd.mjs +6 -6
- package/dist/product-docs/references/agent-tools.md +9 -0
- package/dist/product-docs/references/automations.md +3 -2
- package/dist/product-docs/references/cli.md +16 -0
- package/dist/product-docs/references/desktop-workbench.md +24 -4
- package/dist/product-docs/references/files-git-and-review.md +11 -2
- package/dist/product-docs/references/fork-workflows.md +3 -2
- package/dist/product-docs/references/index.md +2 -1
- package/dist/product-docs/references/managed-environment-files.md +10 -10
- package/dist/product-docs/references/member-managed-files.md +13 -12
- package/dist/product-docs/references/mobile.md +42 -4
- package/dist/product-docs/references/onbox-agent-tools.md +172 -17
- package/dist/product-docs/references/project-setup.md +35 -13
- package/dist/product-docs/references/remote-assistants.md +3 -3
- package/dist/product-docs/references/security-and-data.md +6 -0
- package/dist/product-docs/references/team-template.md +3 -2
- package/dist/product-docs/references/threads-and-agents.md +66 -1
- package/package.json +2 -2
|
@@ -38,8 +38,16 @@ the selected repositories and their Git worktrees. `start` uses that same
|
|
|
38
38
|
scope for the manifest's suggested conversation inventory. Use
|
|
39
39
|
`detect agent-threads --all` to include other projects and conversations whose
|
|
40
40
|
project is unknown; their ids can be selected normally. Add `--json` for the
|
|
41
|
-
complete list when the text display is shortened.
|
|
42
|
-
|
|
41
|
+
complete list when the text display is shortened.
|
|
42
|
+
|
|
43
|
+
When `start` finds local threads, it adds a `TODO(agent)` marker above
|
|
44
|
+
`agentThreads`. Always ask the user whether they want their threads on the
|
|
45
|
+
Template box: say how many were found for this project and in other folders,
|
|
46
|
+
and offer all of the project's threads, a subset you list for them, or none.
|
|
47
|
+
Record their answer, then remove the marker. Leave `import: none` only when
|
|
48
|
+
the user chooses it. Threads can also be imported after setup with
|
|
49
|
+
`dvb threads import --project <project>`, so tell a user who isn't sure that
|
|
50
|
+
they can decide later.
|
|
43
51
|
|
|
44
52
|
Done means: the `include` list reflects the user's choices, and any
|
|
45
53
|
can't-copy items have been mentioned to them.
|
|
@@ -43,10 +43,12 @@ Ground rules:
|
|
|
43
43
|
boxes.dev page where the user can connect Codex, Claude Code, GitHub, and
|
|
44
44
|
Slack, and it waits until they click Done, which can take several minutes.
|
|
45
45
|
Read its first lines, then tell the user what the page is for and give
|
|
46
|
-
them the link it printed in case the browser didn't open.
|
|
47
|
-
|
|
48
|
-
still
|
|
49
|
-
|
|
46
|
+
them the link it printed in case the browser didn't open. If their agent
|
|
47
|
+
is already connected to boxes.dev, explain that they don't need to sign in
|
|
48
|
+
again, but still need to click Done to continue setup. Continue once it
|
|
49
|
+
reports the connected agents. Done also finishes the command when the user
|
|
50
|
+
selects **Use a code instead**. With an older CLI, if the user says they
|
|
51
|
+
clicked Done but the command is still waiting, stop it and run
|
|
50
52
|
`dvb agent-init status`.
|
|
51
53
|
Over SSH it prints a link for the user to open instead and exits without
|
|
52
54
|
waiting; continue when the user says they're done.
|
|
@@ -55,11 +57,46 @@ Ground rules:
|
|
|
55
57
|
|
|
56
58
|
## Phase 2: Start
|
|
57
59
|
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
60
|
+
First choose the project folder. Most projects are a single repository: set
|
|
61
|
+
up the repository you were opened in, or the one the user names, unless
|
|
62
|
+
evidence shows that the user develops several repositories together. Evidence
|
|
63
|
+
includes:
|
|
64
|
+
|
|
65
|
+
- tracked files in one repository that refer to another by relative path,
|
|
66
|
+
such as a `file:../shared` dependency, a Compose build context, a `go.work`
|
|
67
|
+
entry, or a script that runs `cd ../api`
|
|
68
|
+
- a README or setup doc that tells developers to clone the repositories side
|
|
69
|
+
by side
|
|
70
|
+
- other repositories attached to your current session as additional working
|
|
71
|
+
directories, or a tracked editor workspace file that lists them
|
|
72
|
+
- the user saying that they work across them
|
|
73
|
+
|
|
74
|
+
Repositories that only sit in the same folder are not evidence. A folder of
|
|
75
|
+
unrelated repositories, such as `~/code` or `~/projects`, is a workspace
|
|
76
|
+
rather than a project. Check only the paths your evidence points to, and do
|
|
77
|
+
not survey the parent folder.
|
|
78
|
+
|
|
79
|
+
When you find evidence, ask the user once: name the repositories, show what
|
|
80
|
+
connects them, and recommend an answer. Without evidence, do not ask whether
|
|
81
|
+
the project needs other repositories.
|
|
82
|
+
|
|
83
|
+
A multi-repository project's folder must directly contain each of its
|
|
84
|
+
repositories. If you were opened in a folder of repositories, use the same
|
|
85
|
+
evidence to decide which ones belong together, and ask the user which
|
|
86
|
+
repository to set up when none clearly do. When the choice is one repository,
|
|
87
|
+
start from that repository so it becomes a standard single-repository
|
|
88
|
+
project. If related repositories do not share a parent folder, explain that
|
|
89
|
+
to the user and let them decide whether to move or clone them.
|
|
90
|
+
|
|
91
|
+
Run `dvb agent-init start --project <path>` with the folder you chose, and
|
|
92
|
+
run later `dvb agent-init` commands from that folder. `start` validates the
|
|
93
|
+
project, pins its identity, and seeds the manifest with everything detectable
|
|
94
|
+
(agent config, repos, untracked-file defaults), plus the live instance-type
|
|
95
|
+
catalog and the team's current default. It prints the manifest path — that
|
|
96
|
+
file is now the working document. When the folder is not itself a
|
|
97
|
+
repository, every repository and top-level file inside it starts selected;
|
|
98
|
+
keep only what belongs in the project in `project.repositories` and
|
|
99
|
+
`project.rootEntries`.
|
|
63
100
|
|
|
64
101
|
Read any worktree, project-overlap, or skipped-repository explanations printed by `start`.
|
|
65
102
|
Explain them to the user during review and confirm the intended project scope.
|
|
@@ -139,11 +176,12 @@ destination paths and get the user's choice before selecting outside files.
|
|
|
139
176
|
Record unresolved requirements in `setupNotes` for remote setup and validation.
|
|
140
177
|
|
|
141
178
|
Do not silently choose approval-sensitive options. Before `check`, explicitly
|
|
142
|
-
confirm
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
179
|
+
confirm the repositories in a multi-repository project, runtime agents and
|
|
180
|
+
imported agent config/history, dirty and untracked files, databases,
|
|
181
|
+
instance type, GitHub access, Git SSH/signing, devbox lifecycle or Template
|
|
182
|
+
maintenance configuration (including watch paths), and any instruction that
|
|
183
|
+
lets the remote setup agent change tracked project files. It is fine to
|
|
184
|
+
recommend defaults, but the user must make the choice.
|
|
147
185
|
|
|
148
186
|
Git access may need outside action. For managed GitHub, use check to identify
|
|
149
187
|
and complete connection, App repository access, or an account update. If
|
|
@@ -24,8 +24,10 @@ Rules:
|
|
|
24
24
|
ordinary files and folders alongside child repositories. For example,
|
|
25
25
|
`repositories: [api, web]` and `rootEntries: [package.json, scripts]` will
|
|
26
26
|
copy those two repos and those two root entries. Removing a repo from this
|
|
27
|
-
selection excludes it from access setup and general copying.
|
|
28
|
-
|
|
27
|
+
selection excludes it from access setup and general copying. Select several
|
|
28
|
+
repositories only when the user confirmed a multi-repository project (see
|
|
29
|
+
Phase 2 of `guide flow`). Older documents without these fields retain the
|
|
30
|
+
existing project selection.
|
|
29
31
|
Update startup scripts and maintenance watches when changing the selection;
|
|
30
32
|
setup will not rewrite your shell commands.
|
|
31
33
|
- Set `untracked.copy` independently of `localChanges.copyDirty`. Custom
|
|
@@ -112,6 +114,9 @@ path (`.` for the root); each watched path is exact and relative to that
|
|
|
112
114
|
repository. Maintenance watches always require current boxes.dev GitHub App
|
|
113
115
|
read access, even when `githubAccess` uses SSH or skips Git transport.
|
|
114
116
|
|
|
117
|
+
Set `templateMaintenance.timeoutSeconds` to an integer from 1 through 480
|
|
118
|
+
seconds (at most 8 minutes).
|
|
119
|
+
|
|
115
120
|
Setup creates the maintenance policy with its schedule off, records a fresh
|
|
116
121
|
baseline for every watch, and does not run the script. A later watched change
|
|
117
122
|
or a schedule the user enables in Project settings can start the first run.
|