AI agents

rdev comes with a ready AI agent profile, so your agents know how the environment works from the first day.

Supported agents#

Full support means the installer, the profile, managed settings and updates cover the agent. Basic support means the agent gets the shared rules and MCP access, without agent-specific extras.

Shared rules#

The rules every agent follows live in one place, AGENTS.md. Codex, Gemini CLI and opencode read it directly, and Claude Code includes it from its own CLAUDE.md. Agent-specific parts, such as Claude Code skills and hooks, sit on top of these shared rules.

How much of the profile you get depends on your plan:

• Single: base rules.
• Pro: the full profile with skills, agents and model routing.
• Team: the full profile plus shared team rules.

The full profile adds Claude Code skills for Laravel, WordPress, debugging and deploying in this environment; a frontend subagent that does visual work on a faster, cheaper model while the main session keeps the hard parts (that is the model routing); and a reviewer subagent for an independent review before a change is finished. Team rules are written on the Teams page. If you move to Single, the full profile's files are removed unless you changed them.

MCP access#

Agents get MCP access to your sites and databases. That lets an agent create a site, add Redis, a database, search or S3 storage to a project, install a PHP extension such as mongodb when composer asks for it, look up a database or read captured email on its own, instead of asking you to do it.

Your own account#

You connect your own Anthropic or OpenAI account. Agent usage is billed by those providers and is not included in your rdev subscription. We never see your prompts or your usage.

Running agents around the clock#

Agents run on your server, not on your laptop. Start a long task, close the lid, and the agent keeps working.

Agent sessions on the panel#

Agent sessions in the panel lists the Claude Code and Codex sessions on your servers and what each is doing: Working, Waiting for you (a permission prompt or a question), Finished or Stopped on an error. It refreshes every few seconds and works on a phone, so you can check a long task from anywhere. Sessions waiting for you come first.

Only the agent, the session, the project folder's name and the state reach the panel; never your prompts, the agent's answers or your code. Sessions are kept for a week. Codex reports Working and Finished; its approval prompts do not show yet.

Checkpoints: undo what an agent did#

When an agent turn starts in a git project, rdev saves a checkpoint of the project's files first: tracked and new files, not ignored ones. It is a commit outside your branches, so git status, your history and your stash look the same. Each project keeps its last 20 checkpoints; a turn that changed nothing adds none.

To undo, open your server on the panel and pick a checkpoint under Undo and restore, or on the server. List the project's checkpoints:

rdev checkpoint list

Then restore one by its id:

rdev checkpoint restore 1793603600

Restoring puts the files back as they were and deletes files added since; the current state is saved as a new checkpoint first, so a restore can be undone too. rdev checkpoint create saves one by hand. Checkpoints need rdev 0.2.0-beta.16 or later.