AI sessions
Connect Codex
Updated July 25, 2026
Milestone works with Codex as a second agent alongside Claude Code. Connecting it takes one click, and it reuses the credential Claude Code already set up.
Connect Claude Code first
Codex borrows the Claude Code connection's token, so that one has to read Healthy before the Codex button becomes available. See Connect Claude Code.
Connect Codex
Turn on Codex
Go to Settings → Connections and enable Codex (experimental). A Codex row appears alongside Claude Code.
Connect it
Find the Local Codex CLI row and click Connect. The status changes to Connected.
Turn on team knowledge
Scroll to Team knowledge sync for Codex and turn on Enable on this machine, then Allow & enable. This is what makes Codex sessions start with your team's context.
What gets changed
Connecting edits your Codex configuration to add Milestone as a tool server. Milestone appends its own section and leaves the rest of your file - including your comments and other tools - exactly as it was, and writes a timestamped backup alongside it before making changes.
Chats inside the Milestone app don't depend on this. They attach the connection per session, so your global Codex setup is only used by Codex in your own terminal.
Start a fresh session after connecting
Codex reads its tool list once when it starts. If a session was already running when you connected, quit it and start a new one - otherwise Milestone's tools won't appear.
Verify it worked
Start a new Codex session in a bound repository and ask it something specific to your team. If it answers from your workspace, you're connected. If the tools are there but answers stay generic, knowledge sync is off.
Related
Ready to try Milestone?
Give your team and its AI agents one shared memory.