Create your first agent
Create a small interactive agent, give it access to a disposable folder, and verify that it can resume with its conversation intact.
Prepare a working folder
On the machine where the agent will run:
mkdir -p /tmp/codity-resume-demo
cd /tmp/codity-resume-demo
node --version
Node.js must be version 18 or newer. Keep this terminal in the working folder when you run the install command.
Fill the dashboard form
Open Agents in the dashboard and fill these fields:
| Field | Example |
|---|---|
| Name | resume-demo, or keep the generated name. |
| Provider | OpenAI. |
| Model | GPT-5.6 Luna, if available in your provider account and the model picker. |
| API key | Your OpenAI API key. |
| Run mode | Interactive (TUI). |
| When something is not allowed | Refuse. |
| Runs on | Linux (bash), or macOS (zsh) on a Mac. |
| Where is it? | Local laptop, optional. |
| Team | No team for this standalone example. Organization policies still apply. |
| Paths | /tmp/codity-resume-demo/**, with Write access. |
| Commands and URLs | Leave empty. File tools handle this example. |
| Secrets and existing environment variables | Leave empty. |
| Enable recovery | Checked. |
Write access includes reading the matching files. If your organization denies this folder, ask an administrator for an approved test location and update every path in this guide to match it.
Task is optional in Interactive mode. For this test, enter:
Remember the code MANGO_93 in our conversation. Write ONE to /tmp/codity-resume-demo/step1.txt. Do not write the code to a file. Reply READY and wait for my next message.
For Headless mode, provide a nonempty task before deploying. Required fields have an asterisk, and the form explains what remains missing if Deploy agent is disabled.
Install and start
Click Deploy agent, copy the generated install command and execute it in the terminal you prepared. Use the command exactly as generated, including its API URL. It installs the runner and the codity-agent command, then starts the session.
The One machine command expires after five minutes and works once. If it expires or has already been used, generate a fresh install command. For multiple machines, use Many machines; its reusable token defaults to seven days and each installation creates a separate run.
The agent should create step1.txt and reply READY. Open its dashboard page to see the transcript, permissions and run activity. A rejected attempt to run an unlisted command is expected; the agent may continue with an allowed file tool.
Pause and resume
After the first file has been written, press Ctrl+C in the agent terminal. Wait for the session to stop and print its resume instructions. The dashboard should show Paused when a resumable checkpoint was saved.
From the same folder, run:
codity-agent resume --last
Ask the resumed agent:
What code did I ask you to remember? Write it to /tmp/codity-resume-demo/step2.txt. Leave step1.txt unchanged.
Verify the files in your own terminal:
cat step1.txt step2.txt
Expected contents:
ONE
MANGO_93
The code was stored only in the conversation before resume, so this also checks that history was restored. Your terminal commands do not need to be added to the agent's command permissions.
Continue or stop permanently
Use codity-agent resume to choose a saved session, or follow Session recovery for interrupted actions and another machine. To permanently disable the configuration and stop its live runs, use Revoke on the agent page. Revocation prevents later recovery.

