Using Xervente

Xervente works inside your agent's own session. Most of the time there is nothing to do: keep working, and it steps in when the agent stops.

How it switches on

When you start an agent session in a project (a folder with git, package.json or a similar project file), Xervente switches on by itself and says so in one line. It adds nothing to your repository: its record lives in a hidden .servente folder that git is told to ignore.

When you ask the agent to build something ("make a calculator app"), Xervente takes charge of that build: it keeps the agent going until the result works and has been checked.

The free plan covers 3 projects at a time. A fourth one does not switch on, and the session tells you why.

The /xervente command

Type these in your agent's chat (Claude Code). Everything also works from the Xervente app.

Autopilot and Review

Autopilot answers the agent the way you would: it decides between options, tells the agent how to handle a concern, turns down extras you never asked for, and sends it back when a "done" was not really checked.

Review shows you what the agent asked and Xervente's draft side by side, in the app and on your phone. Send it as it is, edit it, or drop it. The agent waits up to ten minutes; if nobody answers, it stops and the draft expires.

You see every answer Xervente gives, in the session and in the app's live feed.

What stays with you

These are never decided for you, in either style:

• Publishing, deploying to production, deleting data, force-pushing, payments. The command is held and waits for Approve once or Deny.
• Passwords, keys, tokens, 2FA codes and sign-ins. You get an alert; what you type goes to the agent once and is never stored.
• Your IDE's own permission prompts. Only you can approve those, in the IDE; Xervente tells you and never answers "yes" for you.

Your phone

On your computer: Xervente app, Hubs, Pair a phone. On the phone: Xervente app, Scan QR code. The phone then shows what waits for you, the live feed and the reports, and you can answer, approve, steer or stop the agent.

The phone talks straight to your computer, on the same network. The first time, Windows may ask to let Node.js through the firewall on private networks: allow it.

How it learns you

Xervente builds a short picture of how you work from the messages you wrote to your agents and from your corrections in the app (an undone decision, an edited draft). It stays on your computer. It never learns from passwords or from answers typed by an agent.

Agents

Turning it off

Per project with /xervente off, everywhere with /xervente off everywhere or the switch at the top of the app's Account card. In VS Code, the Xervente button turns into Stop Xervente while it is on. Your agent then works exactly as before.

Your data

Per project: the hidden .servente folder (goals, decisions, the event log). For you: the .servente folder in your home folder (settings, what Xervente learned about you, paired phones, your licence). Delete them and Xervente forgets. Nothing is kept by Arad Soft. See privacy.

If something is wrong

• Nothing happens in a session: type /xervente. If it says it is off, /xervente on; if the free plan is full, turn another project off.
• "Xervente could not answer the agent for you": it could not reach your AI (not signed in, offline, or out of credit). The agent's message is yours to answer.
• The phone cannot connect: same Wi-Fi as the computer, and allow Node.js through the firewall.
• The desktop app window is blank: its log is %APPDATA%\servente_app.log. Restarting the graphics driver (Win + Ctrl + Shift + B) or the computer usually fixes it.
• Still stuck: [email protected].