Practical guide

Set up Codex in the desktop app

The objective is to connect the Codex app to a repository safely. The review baseline covers sign-in, workspace, repository rules, sandbox, tests and review.

LOL.MARKETING / CONNECTING INTELLIGENCE

The essential answer

Codex is used through the Codex area in the current desktop interface. Select the right account and a clearly bounded project. Setup is accepted when a small task with suitable permissions produces a reviewable diff and relevant test results.

01 / FIT

A good fit when

  • A concrete assignment and an accountable domain owner are defined.
  • Reviewable setup evidence includes the selected repository, effective boundaries, the diff for a small task and relevant test results. Review confirms that unrelated files were not changed.

02 / LIMITS

Not the first choice when

  • Avoid: production secrets in the repository or unrestricted write access. Production secrets or unrestricted write access in the first workspace prevent a sufficiently isolated setup trial.

Choose the workspace and model deliberately

The desktop interface connects ChatGPT and Codex while retaining distinct working areas. For repository work, select Codex and the intended project folder. GPT-6 Sol and Luna are available according to access in the September update; a manual model choice can be retained. Check the setting actually in use before comparing results. A file project is also not automatically a Git repository. Working location, model and version control belong together in the setup evidence.

Choose a small project with a known starting state

An initial trial needs only a bounded issue and a reproducible test. Record the starting state and supply expected behaviour, test commands and constraints. An isolated branch or worktree makes review easier when the project uses Git. Production credentials are normally unnecessary for this setup test.

Review permissions and output together

Before the task, review effective file, command and network permissions. Afterwards, inspect the diff, relevant tests and application behaviour. Assess additional apps or MCP tools individually. Sign-in proves access; the reviewed task proves whether this setup is useful for your team.

Decision matrix

Decision pointProceed whenStop when
Working environmentDocumented: sign-in, workspace, repository rules, sandbox, tests and review.Scope, data or accountability remains unresolved.
Isolated functional testReviewable setup evidence includes the selected repository, effective boundaries, the diff for a small task and relevant test results. Review confirms that unrelated files were not changed.There is only an unevaluated demo without acceptance evidence.
Operational readinessOwner, approval, fallback and next review date are defined.Avoid: production secrets in the repository or unrestricted write access. Production secrets or unrestricted write access in the first workspace prevent a sufficiently isolated setup trial.

Keep it verifiable

Primary sources

The next sensible step

Which AI system fits your business?

Eight steps from a general interest in AI to a clearer decision for your business.

Start AI System Check
FreeProvider-neutralNo credentials