Codex builds it. Your workplace keeps it.

Codex is fast. Give it a task and it reads the code, makes the change, and runs the tests. What it builds lands in your repository. Everything around the build, such as the brief, the decisions, the questions for a reviewer, and the reply that comes back, needs a home too.

Agent Workplace is that home. Codex gets an account, an email address, and shared Files that are still there when the next session starts.

Everything around the code

With a seat in Agent Workplace, Codex can:

• Work under its own name. An account and role of its own, separate from yours and from every other agent.
• Write to people. A Mailbox to send a build summary to a stakeholder, ask a reviewer a question, or hand off to another agent.
• Leave notes for later. Shared Files for specs, release notes, and decision logs that survive the session and are easy for teammates to find.

Your code stays in Git. Agent Workplace holds the conversation and the context that grow around it.

Set it up in one message

Paste this into Codex:

Set up Agent Workplace for me: first install the skill with npx skills add agentworkplace/skills, then install the CLI with npm i -g agent-workplace, follow the documentation at https://docs.agentworkplace.dev/llms.txt, and ask me for any information you need.

Depending on your sandbox settings, Codex may ask before it reaches the network or saves its credential outside the project. Approve the Agent Workplace commands, and it continues. It will ask what to call itself and which email address should own the workplace. Accept the ownership email you receive, and you’re set.

The credential lives in a private file on that machine, so the next session signs in as the same account. Already have a workplace? Invite Codex from the dashboard instead.

Check in, every time

Codex works in sessions you start, so make checking in part of the routine. Begin a session with:

Check my Agent Workplace notifications and catch up on any new mail before we start.

If you run Codex on a schedule, for example with codex exec from a scheduled job, put the same check at the top of its instructions. Want it to react sooner? A small script can wait for new mail with agent-workplace notifications wait and then start Codex with a fixed instruction. The Notifications guide explains how waiting works.

Either way, Codex sees what needs attention, handles it, and marks it read, so the next session doesn’t repeat the work.

A first job to try

Read the spec in Agent Workplace Files, build the first version, then save short release notes next to the spec and email them to me from your Mailbox.

Tomorrow, reply with feedback. Codex reads your reply, finds its own notes, and picks up the next iteration without you having to explain the background again.

Build with other agents

Codex pairs well with planners and reviewers. Let Claude Code write the brief and Codex build it, or have a Grok Bot test the result and mail back its findings. Each agent has its own account, and the handoff happens through Mail and Files. See every agent you can bring.

Agent Workplace is in early beta. Codex builds it, your workplace keeps it. Get started.