GMAIL → CODING AGENT

How to email a coding agent from Gmail

To email a coding agent from Gmail, install @gent on the computer that has your project and Codex or Claude Code, configure Gmail access, then send a message from your own Gmail account to your own address with +agents added. @gent reads the authenticated Sent folder, runs the task locally, and replies in the same thread. This procedure reflects the @gent 0.4.0 release checked on October 15, 2026.

1. Install @gent on the computer that will do the work

Install the current PyPI package with the two commands below, then let the guided setup create your local configuration.

uv tool install atgent
atgent init

The current package lists Gmail or Google Workspace with IMAP access, macOS or Linux, Python 3.11 or later, and uv as requirements. Install and sign in to Codex or Claude Code on that same computer before starting the runner.

2. Give the runner a Gmail sign-in

Choose an app password or your own Gmail OAuth desktop client during setup, and keep the credential in your password manager or operating-system keychain. Google’s account help page, fetched October 15, 2026, says an app password is a 16-digit passcode and requires 2-Step Verification; managed accounts and some security settings may not offer the option.

Run the diagnostic before sending the first task:

atgent doctor
atgent run

doctor checks IMAP and SMTP without sending mail. After the first successful poll, send a new message so historical Sent mail is not mistaken for a task.

3. Send a task with a subject that names the agent

Send from the Gmail account you configured to your own address with +agents appended. Start the subject with the agent name; use a project alias after a slash when you need a specific configured project.

To: you+agents@gmail.com
Subject: Codex/website: fix the build

Put the work request in the body. For one task, add a model in square brackets before the colon, for example Claude [opus]: review the auth flow. Add terminal in the same brackets when you want an interactive Terminal window instead of a background run.

4. Continue in the same thread or at the desk

Reply above the quoted conversation to continue the task. Reply status for progress or stop to cancel a queued or running turn. To resume locally, run atgent list and select the task, or open one directly with atgent open TASK_ID.