$ the-wire · showcase
codex exec goes remote, opencode answers crashes with readable 500s
By RepoJournal · Filed · About Agentic Coding · Composed from the cited sources · methodology
Codex and opencode both shipped operator-visible changes today: remote app servers in `codex exec`, and a server that explains its 500s instead of returning an empty body.
Support remote app servers in `codex exec` openai/codex
`codex exec --remote <ADDR>` now runs a noninteractive turn against an existing app server's configuration and credentials, starting a new thread or resuming one by UUID, with human-readable or JSON output and optional bearer-token auth via `--remote-auth-token-env`. Remote options are accepted before or after `exec`, and conflicting endpoints are rejected, so CI jobs can share one running serv...
fix(server): answer handler defects with a readable 500 instead of an empty one anomalyco/opencode
A request that crashes in a handler used to return a 500 with an empty body; it now carries JSON naming storage as the cause when that is the problem, and otherwise a ref to find the crash in the server log. Client code that branched on an empty 500 body needs to read the JSON instead, and messages never name the database engine.
feat(ai): scope HTTP middleware to any call, for every modality anomalyco/opencode
Plugin HTTP hooks previously ran only on chat calls; the `@opencode/ai` half of the change scopes middleware to image, video, decisions, embeddings, speech and transcription calls plus polling and downloads. Core wiring comes in a follow-up, so hooks that gate non-chat model traffic will not fully take effect until that lands.
fix(oi-kit): bound empty response retries aaif-goose/goose
Empty provider responses now recover through a bounded state-machine transition, with agent-only retry messages capping recovery at three retries, and retry counting ignores request-preparation context messages so each attempt still passes preparation and turn-budget checks. The point for operators is that a silently empty response no longer hangs or loops the turn.
fix(databricks): drop thinking blocks bound to a different prefix aaif-goose/goose
A Claude Fable 5.2 session on the Databricks AI Gateway used to fail permanently with a 400 signature error once its system prompt changed; thinking blocks bound to a different prefix are now dropped. That removes the dead end for anyone editing a system prompt mid-session against that gateway. Elsewhere, OpenHands synced `agent_settings.agent_kind` with the active profile on cloud and retained...