coilyco-flight-deck/ward

Archived

Watch

goose has no model provider in the container - seed config/auth so ward agent goose can run #186

Closed

opened 2026-06-18 09:50:32 +00:00 by coilysiren · 4 comments

coilysiren commented

2026-06-18 09:50:32 +00:00

Owner

ward agent goose work|headless|task|reply is now fully unblocked on the image side: the dev-base image ships the pinned goose CLI as of coilyco-flight-deck/agentic-os#258, and the container entrypoint already builds the goose argv (goose run -t <seed> headless, goose session interactive) and mirrors composed doctrine into ~/.config/goose/.goosehints.

What is still missing for goose to actually do work in a container: a model provider. The agent-adapter manifest lists goose as auth: none, and the entrypoint has no write_goose_creds / compose_goose_config step (unlike claude creds and codex auth.json + config.toml). So a launched goose has no provider/model bound and cannot run.

Scope: wire goose's provider/auth into the container the same way codex was (ward#178), i.e. seed ~/.config/goose/config.yaml (provider + model) and any provider key the chosen model needs, and flip the manifest auth slot off none. Decide the default provider/model for the ephemeral container (a cloud peer for reliability, or the tower Ollama quant over tailnet if reachable).

Follow-up to coilyco-flight-deck/agentic-os#258 (install goose CLI). Filed by ward agent claude while carrying #258.

`ward agent goose work|headless|task|reply` is now fully unblocked on the image side: the dev-base image ships the pinned `goose` CLI as of coilyco-flight-deck/agentic-os#258, and the container entrypoint already builds the goose argv (`goose run -t <seed>` headless, `goose session` interactive) and mirrors composed doctrine into `~/.config/goose/.goosehints`. What is still missing for goose to actually do work in a container: a **model provider**. The agent-adapter manifest lists goose as `auth: none`, and the entrypoint has no `write_goose_creds` / `compose_goose_config` step (unlike claude creds and codex `auth.json` + `config.toml`). So a launched goose has no provider/model bound and cannot run. Scope: wire goose's provider/auth into the container the same way codex was (ward#178), i.e. seed `~/.config/goose/config.yaml` (provider + model) and any provider key the chosen model needs, and flip the manifest `auth` slot off `none`. Decide the default provider/model for the ephemeral container (a cloud peer for reliability, or the tower Ollama quant over tailnet if reachable). Follow-up to coilyco-flight-deck/agentic-os#258 (install goose CLI). Filed by `ward agent claude` while carrying #258.

coilyco-ops commented

2026-06-18 09:52:28 +00:00

Owner

🔒 Reserved by ward agent claude — container ward-ward-issue-186-claude-fe3ac665 on host kais-macbook-pro.local is carrying this issue (reserved 2026-06-18T09:52:27Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent claude` — container `ward-ward-issue-186-claude-fe3ac665` on host `kais-macbook-pro.local` is carrying this issue (reserved 2026-06-18T09:52:27Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilyco-ops added the

priority

autonomy

live-collab

labels

2026-06-24 04:15:23 +00:00

coilyco-ops commented

2026-06-24 17:26:39 +00:00

Owner

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P2 - Seed goose provider/auth so ward agent goose can run, concrete and unblocked on the image side.
interactive - Needs a provider/model choice for the ephemeral container, agent wires it and pauses at that pick.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P2** - Seed goose provider/auth so ward agent goose can run, concrete and unblocked on the image side. - **interactive** - Needs a provider/model choice for the ephemeral container, agent wires it and pauses at that pick.

coilyco-ops commented

2026-06-24 17:28:57 +00:00

Owner

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P2 - Seed goose provider/auth so ward agent goose can run, concrete and unblocked on the image side.
interactive - Needs a provider/model choice for the ephemeral container, agent wires it and pauses at that pick.

coilysiren commented

2026-07-06 18:57:52 +00:00

Author

Owner

Closing: landed. goose model-provider seeding shipped - entrypoint.sh compose_goose_config() (ward#186 marker) seeds ~/.config/goose/config.yaml + an Ollama smoke test. The 'goose has no provider' premise is void. Re-triage 2026-07-06.

coilysiren closed this issue

2026-07-06 18:57:52 +00:00

Commenting is not possible because the repository is archived.

No milestone

No project

No assignees

2 participants

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/ward#186

No description provided.

Rows
Columns