Connect Codex to a shared workflow.

How it connects

Arenor uses the Codex app-server interface for sessions, model listings, streamed events and approval requests. Model execution uses your provider account. A listed model does not independently prove that your account can access it.

Connect for the first time

1. Install the official Codex CLI and complete sign-in.
2. Check its path and sign-in status in Arenor → Settings → Accounts.
3. Assign Codex, a role and an appropriate model to a team member.
4. Start with a small task. Review the plan, approval mode and file scope, and require test output as part of the result.

codex --version
codex login status

Example: assign tests to another member

One member can change behavior while a Codex member handles tests. Test writing may run in parallel when it owns a separate file; if execution depends on the implementation, add that dependency to the plan.

Check that the new button label is displayed correctly.
Write only to the test file.
Run the test after implementation is complete.
Report the pass/fail result and the command you ran.

Choose the right tool for the job

Codex has its own official app and CLI workflows. OpenAI also provides a Codex plugin for reviews and task delegation from inside Claude Code. Arenor is useful when you want different providers coordinated through persistent teams, tasks, history and approvals.

Access and permission boundaries

• The Arenor license does not include Codex usage or a provider plan.
• Planning sessions start with read-only Codex settings; implementation sessions allow workspace writing. Additional permissions may still be requested.
• Roles and task scopes are not guarantees of file isolation. Review plans, permissions and diffs.
• Your account and provider data terms apply to the context sent to the model.

Sources

• Codex app-server
• OpenAI Codex plugin for Claude Code