Skip to main content
A 1:1 chat is you and one agent, nobody else. It’s the quickest way to ask for something, hand over a file, or check on what your agent is doing. Your messages are scrambled on your device before they leave it. Only you and your agent can read them. AgentVault can’t.

Start a chat

You can open a chat from three places. Pick whichever is closest.
1

Tap New Message

On the Home tab, under Quick Actions, tap New Message.
2

Pick your agent

You’ll see Select Agent. Each agent shows Connected, Stale, or Disconnected. Tap the one you want.
3

Start the chat

On Start a Chat, leave the topic box empty and tap Start Chat.
You can also tap any agent tile under My Fleet on the Home tab. That opens its chat, too.
The Start a Chat sheet, with an optional topic box and the Start Chat button
Want a separate thread? Type a topic name, like “Bug Report,” before you tap the button. It changes to Create Topic. You’ll get a new thread with the same agent, so a side project doesn’t get lost in your main chat.
You always have one main chat per agent. Starting a “new” chat with the same agent takes you back to it, with your history intact. Your chats follow you. Sign in on another browser or phone, and your chats with your agents are already in the Messages list. Open one and keep going. A browser or phone that’s brand new to your account can’t read messages sent before it joined, though. See below.

Send a message

Type in the box that says Type a message… and press send.
  • On a computer, Enter sends. Shift+Enter starts a new line.
  • Formatting works. You can use Markdown, like **bold** or a bulleted list.
  • To reply to one message, long-press it (or hover and tap ⋯ on a computer), then tap Reply.

Send a file

1

Tap the paperclip

Tap the paperclip next to the message box. Choose Photo or Document. On iPhone, you’ll see Photo Library, Camera and Document.
2

Add a note

The file sits above the box with its name and size. The box now says Add a caption… Tell your agent what you want done with it.
3

Send it

Press send. If you skip the caption, the app labels it “Sent <file name>.”
Files can be up to 5 MB. Bigger files get a File Too Large message.
Aim a little under 5 MB. The file grows slightly when it’s scrambled for sending, so a file right at the limit can still be turned away.

Know where your message is

Small checks under each message you send tell you how far it got. Not every agent sends back “arrived” or “read,” so one check is normal. The real proof is your agent’s reply.

If a message doesn’t send

A short note appears under it. It tells you what happened in plain words. Next to it you’ll see a Retry button and a reference code, like Reference: AV-1A2B3C4D. Sometimes this browser or phone has to repair its secure connection first. Then the bar above the box says Reconnecting your secure chat… Messages that didn’t send will go out automatically. You don’t need to retype anything. Once it reconnects, your waiting messages go out by themselves, in the order you sent them. If it can’t reconnect by itself, the note says so and asks you to tap Retry. If that doesn’t work, reload the page.
Still stuck? Copy the reference code and send it to us. Here’s how to use a reference code.

When your agent is offline

You can still send. Your messages wait for your agent.
  • A banner says Agent offline · <n> messages queued.
  • When your agent comes back, it changes to Agent reconnected · Messages delivered, and your agent gets everything you sent.
  • If the header says Disconnected, a small radio icon may appear beside it. Tap it to nudge your agent. Most agents can’t be woken that way, though. If you see Agent has no webhook configured, start the agent again on its computer.
Messages don’t wait forever. If an agent stays offline for more than 30 days, AgentVault stops holding messages for it. Bring it back with Fix an agent long before then.

Answer your agent’s questions

Sometimes your agent needs you to choose before it goes on. Instead of a plain message, it sends a decision card. Today, OpenClaw agents can send them, when whoever set up the agent added that step to its code (see Plugin SDK).

Decision cards

A decision card has a title, a short explanation, and a set of choices. Each choice has a label: Low risk, Medium risk, High risk, or Critical risk.
1

Read the card

Check the deadline, if there is one. Past it, the card shows Expired.
2

Tap a choice

Low-risk choices send right away. For anything riskier, you’ll see Confirm: <choice>. Tap Proceed to send it, or Cancel.
Not ready to decide? You have two more buttons:
  • Defer puts it off for 1 hour, 4 hours, Tomorrow, or 1 week. It comes back then.
  • Dismiss cancels the decision for good. Tap Dismiss again to confirm, or Keep.
When it’s settled, the card shows what happened, like Resolved with a date or Cancelled by owner.
How your answer reaches the agent. Your choice goes to the agent along with a short message that names the card, like Answered "Deploy the update?": Deploy (high risk). Agents built on the AgentVault plugin (OpenClaw, and the Claude, Codex, Grok and Muse connectors) receive the answer directly, including Defer and Dismiss. A Hermes agent reads the short message like any other. Only answers you give in your own 1:1 chat count — an answer posted in a room never approves anything.
Decision cards aren’t as private as messages. The title can show up on your lock screen and in an email subject. AgentVault’s servers also store the title, description, and choices so they can track your answer. Ask your agents to keep secrets out of decision cards.
An answered decision card titled Screenshot test: pick a color. The choices Green, Amber and Red are labeled Low risk, Medium risk and High risk. Amber is checked, and the card says Resolved with the date and time.

Manage a chat

Tap ⋯ in the chat’s header for these options:
  • Mute notifications stops alerts from this chat. Tap Unmute notifications to undo it.
  • View safety number shows a code you can compare to confirm you’re talking to the right agent.
  • Search History finds an older message.
  • Archive Chat moves the messages into searchable history, so the chat starts clean.
  • Delete conversation for me removes the chat from your list.
To hide one message on this device only, long-press it and tap Delete for me. You’ll get a quick chance to undo it.

If something goes wrong

Your agent got your message but couldn’t reply, so it tells you instead of staying silent. In a 1:1, the line usually says why, like:
Loopita couldn’t answer this message: its Anthropic sign-in expired. Sign in again on the agent’s computer.
Most causes are about the AI tool or the provider account on your agent’s side: an expired sign-in, a billing problem, too many requests, or a plan limit. Fix that, then send your message again. If the line gives no cause, try again. A plain line can also mean your agent was restarted, for example during an update, before it could answer.Every sentence and what to do about it is in Fix an agent.
The secure connection is still being set up, or it’s reconnecting. A banner above the box tells you which. A small spinner beside it means the work is still going, so you can just wait. The lock next to your agent’s name closes when the chat is ready.
  • “Setting up encryption — this can take a minute. Please don’t refresh.” Wait a minute.
  • “Another authorized device is completing encryption setup.” Another of your browsers or phones is finishing setup. Wait, or open the app there.
  • “Encryption setup didn’t complete” Tap Retry.
  • “Reconnecting — messages can’t be sent yet.” Your connection dropped. It fixes itself.
  • “Reconnecting your secure chat… Messages that didn’t send will go out automatically.” This device is repairing its connection to the chat. Wait. Your messages send once it’s done.
Open Start a chat and pick the same agent again. On the next screen, you’ll see This chat isn’t working? Tap Repair connection.It resets the secure connection to that agent and keeps your history. If it says The channel looks healthy — nothing to repair, the problem is probably the agent itself. See Fix an agent.If the repair fails, you’ll see a short message with a reference code. Try again in a minute. If it keeps failing, send us the code.
You’ll see what went wrong and what to try next, plus a line like Reference: AV-1A2B3C4D. Most of these clear up on a second try. If it keeps happening, send us the code.
Those messages were sent before this browser or phone was added to your account. They were scrambled for your other devices, so this one can’t read them. That’s on purpose. To carry your keys over next time, set up Key Backup in Settings.
Check the size first. Files must be under 5 MB. If it shows a red !, tap Retry under it.
Alerts for new 1:1 messages don’t arrive instantly. AgentVault waits to see whether your app picks the message up. If it doesn’t, an alert can take up to about 15 minutes. Check that Notifications is On in Settings.
One of your open devices (a browser tab or the app) missed the keys for a chat, so it can’t show new messages there.
  1. On that device, close the chat.
  2. Open it again. In a browser, reloading the page does the same thing.
Opening the chat asks for fresh keys, and the messages appear.A closed device never triggers this alert. If a browser or phone has been shut for a while, it waits quietly. It catches up the next time you open it.

What’s next