Repository navigation
Description
Task
| slice | size | difficulty | model | who | estimated lines |
|---|---|---|---|---|---|
| Start, attach and resume | M | routine | standard | an agent | 400 (220 code, 180 tests) |
A box started with
--network,--ingressor--loadoutstores those values, andmin box show --networkshows them.
Scope narrowed by the owner on 2026-11-09. #3159 (norrietaylor) merges first. It adds --network and the egress flags through a shared EgressArgs / flag_egress, used by min session activate, min box create and min task run. List flags add to the file's list (arch#166), --allow-protocols replaces its list, and --deny-all-egress empties both allow lists. Build on that shared path. Do not add a parallel flag path. This task covers what #3159 does not: --ingress, --loadout (BCLI-073), the egress flags on min box start / min session start, and min box spec <entry> taking the same overrides. No interim hints, fallbacks or compatibility shims: file a residual for anything not built.
Covers:
- BCLI-024
- BCLI-073
- BCLI-025
Layers:
- client:
- crates/minimal/src/cli.rs: the verb's arguments and help in the one command model
- crates/minimal/src/cmd/boxes/create.rs: passes
--network,--ingressand--loadoutto the command-line override layer - crates/minimal/src/cmd/boxes/show.rs:
min box show --networkrenders the stored network section - crates/minimal/src/cmd/boxes/policy.rs: shares the effective-network rendering
- crates/minimal/src/tests.rs: the in-process minimald test harness gains this layer's tests
cargo nextest run -p minimal network_flags_override_stored_spec_and_projectioncargo nextest run -p minimal start_loadout_flag_selects_loadouts_layercargo nextest run -p minimal box_show_network_renders_effective
- docs:
- docs/reference/cli-min.md: documents
--networkand--ingressas overrides of the entry's network keys
- docs/reference/cli-min.md: documents
Waits on:
- T10 — Start a box from its entry #2898
- feat(minimal): take the network and egress flags on min task run and min box run #3159 (shared
EgressArgs/flag_egress; merges first, owner 2026-11-09)
Plan block
### T11 — Override network, ingress and loadouts at start
slice: S3
kind: task
covers: BCLI-024, BCLI-073, BCLI-025
size: M
est: 220 code, 180 tests
executor: agent
difficulty: routine
model: standard
diagnostics: `min box show <box> --network` prints the box's effective network section as it was stored, overrides included, pinned by box_show_network_renders_effective
observability: the command's existing tracing span records the verb, the box id it resolved and the outcome
layers:
- client:
- crates/minimal/src/cli.rs: the verb's arguments and help in the one command model
- crates/minimal/src/cmd/boxes/create.rs: passes `--network`, `--ingress` and `--loadout` to the command-line override layer
- crates/minimal/src/cmd/boxes/show.rs: `min box show --network` renders the stored network section
- crates/minimal/src/cmd/boxes/policy.rs: shares the effective-network rendering
- crates/minimal/src/tests.rs: the in-process minimald test harness gains this layer's tests
test: cargo nextest run -p minimal network_flags_override_stored_spec_and_projection
test: cargo nextest run -p minimal start_loadout_flag_selects_loadouts_layer
test: cargo nextest run -p minimal box_show_network_renders_effective
- docs:
- docs/reference/cli-min.md: documents `--network` and `--ingress` as overrides of the entry's network keys
produces: none
consumes: none
proof: A box started with `--network`, `--ingress` or `--loadout` stores those values, and `min box show --network` shows them.
depends on:
- blocked by #2898
- blocked by #3159
Activity
minimal-foundry commentedon Nov 10, 2026
Done. #3235 merged.
branch
agent/2903-override-network-ingress-and-loadouts-at-start· epic #2879 · PR #32359064715955855df5892b022b366f13fcUpdated 2026-11-10T21:32:14.963Z.