$ the-wire · showcase
Stop ends the run, plugins get a default policy, and codex honors API-key gates
By RepoJournal · Filed · About Agentic Coding · Composed from the cited sources · methodology
Goose 1.54.0 lands with Stop that actually stops, Codex ships a configurable default plugin activation policy and tightened API-key feature gates, and cost estimates finally apply long-context price tiers.
v1.54.0 aaif-goose/goose
by github-actions[bot]
Goose v1.54.0 prompts for goose mode during first-time configure, adds HTML session export with an interactive viewer, fixes adaptive thinking for Claude Sonnet and Haiku 5.5, treats a client extension selection as the exact session set, and supports hyphenated GPT model names.
Add configurable default plugin activation policy openai/codex
Codex adds plugins._default.enabled with per-plugin enabled overrides, applied to plugin skills, MCP servers, Apps, and hooks. Omitting it preserves existing source and account enablement, and configuration cannot turn on a plugin that is disabled at its source.
Honor API-key feature gates in TUI Daybreak selection openai/codex
API-key accounts that kept a saved Daybreak preference without ApiKeyCyberAccessPrograms enabled will lose it: Codex now requires both CliDaybreak and ApiKeyCyberAccessPrograms, and refreshes state when either flag changes.
agent loop: make Stop end the run promptly and save what it produced aaif-goose/goose
The agent loop's Stop used to depend on every operation checking a cancel token at its own wait points, so runs kept going after Stop and clients killed them by dropping the agent stream, losing streamed output, usage, and tool responses. Stop now ends the run promptly and saves what it produced.
fix(cost): apply long-context price tiers to cost estimates aaif-goose/goose
Cost estimates apply models.dev long-context price tiers to the whole request instead of always using the base rate. In the verification case, gpt-5.5 at 400k input and 2k output now estimates $4.09, up from $2.06, while requests below the threshold are unchanged.
Recover gRPC code-mode sessions after missing-session errors openai/codex
Elsewhere across the desks: Codex now invalidates gRPC code-mode sessions on NOT_FOUND from Execute, Wait, or Terminate so the next execution opens a fresh session, populates the iTerm2 OSC 21337 detail field from the TUI status header, and enforces application.network policy during OAuth discovery in codex mcp add; Gemini CLI cuts false-positive security prompts on flags like ls -ld and git -C...