@boxes-dev/dvb-runtime 1.0.1056 → 1.0.1057

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.
@@ -78,6 +78,12 @@ Fill in every section marked `TODO(agent)`. Each has a guide:
78
78
  `env-files`, `external`, `artifacts`, `databases`, `app`, `untracked`,
79
79
  `git-ssh`, `git-signing`, `agent-config`.
80
80
 
81
+ Also record your current agent and exact model in `agents.setup` if you can
82
+ verify them from current-session metadata or explicit session controls; see
83
+ `guide manifest`. Leave it null if unknown and tell the user during review.
84
+ The remote thread will use that choice when available on the connected
85
+ account, with high reasoning where supported.
86
+
81
87
  For GitHub repos, the manifest defaults to `githubAccess: managed` and keeps
82
88
  the seeded GitHub `gitSsh` rows in skip mode. If check says GitHub is not
83
89
  connected, or that the boxes.dev GitHub App can't access a repository, run
@@ -52,6 +52,7 @@ Sections (each has its own guide topic):
52
52
  | --- | --- | --- |
53
53
  | `project` | Root, repository/root-entry selections, name, and user-approved instance type | (seeded catalog; agent asks user) |
54
54
  | `agents.runtime` | Coding agents configured on the Template box | (seeded) |
55
+ | `agents.setup` | Optional current local agent and model to prefer for remote setup | (see below) |
55
56
  | `files.env` / `files.other` | Explicit environment/secret file copies | env-files |
56
57
  | `external.dependencies` / `.configs` | Outside tools/services + their config files | external |
57
58
  | `artifacts` | Other untracked files worth copying | artifacts |
@@ -67,6 +68,25 @@ Sections (each has its own guide topic):
67
68
  | `templateMaintenance` | Optional Template box upkeep script and the GitHub paths that should trigger it | (compose script and watches together) |
68
69
  | `setupNotes` | Free-form guidance for the remote setup agent | running |
69
70
 
71
+ Record your current agent and exact model in `agents.setup` when you can verify
72
+ them from current-session metadata or explicit session controls. For example:
73
+
74
+ ```yaml
75
+ agents:
76
+ runtime: [codex, claude]
77
+ setup: { backend: codex, model: gpt-6.1-sol }
78
+ ```
79
+
80
+ Use `backend: claude` for Claude Code. Do not infer the model from your name,
81
+ an old conversation, or a configured default that may have been overridden.
82
+ Leave `setup: null` (or omit it) if the active model is unknown. Tell the user
83
+ what you recorded during review. Remote setup will prefer that agent when it
84
+ is selected and connected, and use that model when its runtime advertises it.
85
+ Otherwise it will use the selected connected agent's account default. Setup
86
+ will request high reasoning when the model supports it, or its advertised
87
+ reasoning default otherwise. Once the remote thread starts, retries will keep
88
+ the same thread and model.
89
+
70
90
  `project.instanceType` is seeded to the team's default, but it is not
71
91
  implicitly approved. Present every live option listed in the seeded comments,
72
92
  ask the user which one they want, and keep the chosen key. `check` and `run`