I wasn't doing anything too fancy when this happened. All the "authentication" stuff is i believe application-level messages from the software I was building, not any sort of codex auth. i think these are just some process running tool calls not anything fancy.
▼ Out of turn - ACP server bug
This session/update arrived after the turn ended, which
violates the ACP protocol — per-turn updates must arrive while
a `session/prompt' is active.
This is a bug in Codex ACP implementation, not in agent-shell. Please report it to
the maintainer with the payload below:
json ⧉
{
"jsonrpc": "2.0",
"method": "session/update",
"params": {
"sessionId": "019fd0ca-5d74-7ef1-86f5-2899a9fc73cc",
"update": {
"sessionUpdate": "tool_call_update",
"toolCallId": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5",
"_meta": {
"terminal_output_delta": {
"data": "authentication successful, starting...\r\n",
"terminal_id": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5"
}
}
}
}
}
This session/update arrived after the turn ended, which
violates the ACP protocol — per-turn updates must arrive while
a `session/prompt' is active.
This is a bug in Codex ACP implementation, not in agent-shell. Please report it to
the maintainer with the payload below:
json ⧉
{
"jsonrpc": "2.0",
"method": "session/update",
"params": {
"sessionId": "019fd0ca-5d74-7ef1-86f5-2899a9fc73cc",
"update": {
"sessionUpdate": "tool_call_update",
"toolCallId": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5",
"_meta": {
"terminal_output_delta": {
"data": "restarted REDACTED.service\r\n",
"terminal_id": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5"
}
}
}
}
}
This session/update arrived after the turn ended, which
violates the ACP protocol — per-turn updates must arrive while
a `session/prompt' is active.
This is a bug in Codex ACP implementation, not in agent-shell. Please report it to
the maintainer with the payload below:
json ⧉
{
"jsonrpc": "2.0",
"method": "session/update",
"params": {
"sessionId": "019fd0ca-5d74-7ef1-86f5-2899a9fc73cc",
"update": {
"sessionUpdate": "tool_call_update",
"toolCallId": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5",
"_meta": {
"terminal_output_delta": {
"data": "Connection to REDACTED closed.\r\r\n",
"terminal_id": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5"
}
}
}
}
}
This session/update arrived after the turn ended, which
violates the ACP protocol — per-turn updates must arrive while
a `session/prompt' is active.
This is a bug in Codex ACP implementation, not in agent-shell. Please report it to
the maintainer with the payload below:
json ⧉
{
"jsonrpc": "2.0",
"method": "session/update",
"params": {
"sessionId": "019fd0ca-5d74-7ef1-86f5-2899a9fc73cc",
"update": {
"sessionUpdate": "tool_call_update",
"toolCallId": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5",
"status": "completed",
"rawOutput": {
"formatted_output": "started REDACTED.service\r\nexisting auth token was rejected; starting browser authorization\r\nTo authorize this machine, open:\r\n\r\n REDACTED\r\n\r\nWaiting for browser approval...\r\nauthentication successful, starting...\r\nrestarted REDACTED.service\r\nConnection to REDACTED closed.\r\r\n",
"exit_code": 0
},
"_meta": {
"terminal_exit": {
"exit_code": 0,
"signal": {},
"terminal_id": "exec-778a2790-0662-495c-8f3b-3bbfcdf22ce5"
}
}
}
}
}
I wasn't doing anything too fancy when this happened. All the "authentication" stuff is i believe application-level messages from the software I was building, not any sort of codex auth. i think these are just some process running tool calls not anything fancy.