Adapt OpenMaus UI interaction patterns

[Clondin]

What changed

• Directly adapts compatible interaction patterns from OpenMausBot into Kayco chat, model selection, approvals, connected apps, settings, and responsive navigation.
• Preserves Kayco routing, permissions, credential storage, Codex preferences, approvals, branding, and web runtime.
• Adds Apache-2.0 attribution, a pinned source commit, the full license, and a visual QA record.
• Leaves computer/video implementation files untouched.

Validation

• bun run typecheck
• bun test app/src (48 passed)
• changed-file Biome lint and format checks
• bun run --filter app build
• Playwright desktop/mobile interaction and overflow QA (design-qa.md: passed)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openbot	Ready	Preview	Aug 24, 2026 4:19pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3656a068fe

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Gate the Codex picker on the coworker runtime type

For connected Codex users, this also renders the model picker for system-owned remote AG-UI coworkers: systemOwned only means the profile came from a deployment package (profile-store.ts:139), and the shipped risk-analyst is one such remote-ag-ui coworker (examples/fintech/agents.yaml:55-61). The server applies Codex preferences only when agent.type === "built_in" (server/src/copilot.ts:444-452), so selections made in that conversation do not affect its responder despite the header implying they do. Gate this on the actual built-in runtime type, such as an explicit DTO field, rather than package ownership.

Useful? React with 👍 / 👎.