Skip to content

Reuse OpenUI's Codex app-server with smart routing - #552

Draft
andy-xu-db wants to merge 1 commit into
mainfrom
andy/fix-openui-isaac-codex-context
Draft

Reuse OpenUI's Codex app-server with smart routing#552
andy-xu-db wants to merge 1 commit into
mainfrom
andy/fix-openui-isaac-codex-context

Conversation

@andy-xu-db

Copy link
Copy Markdown
Collaborator

What did you change, and why?

Change: Teach Codex smart routing to reuse a caller-provided --remote app-server. Caller-owned app-server launches keep their requested listener and receive ucode's gateway and routing configuration, while the TUI is connected through a single smart-routing interposer.

Why: OpenUI already owns a Codex app-server for session status, context usage, and resume support. Starting a second app-server under smart routing split the TUI and OpenUI observer across different servers, so OpenUI could not reliably observe the active session.

How do you know it works?

Testing:

  • 370 focused unit and lint tests passed.
  • Ruff lint and format checks passed.
  • ty check src/ passed.
  • In an isolated OpenUI browser test, the session used one app-server plus one interposer, completed a GPT-5.6 Terra turn, and restored 19,099 / 258,400 context tokens after an OpenUI restart.

A companion Universe/OpenUI PR handles token-usage refreshes for observer connections.


This PR was created with GitHub MCP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant