Skip to main content
BROWSER-NATIVE

​
Your agents, from any browser.

Agent studio, marketplace, real-time chat, file attachments — the full Actionist interface in a browser tab. No install. No setup. Open a tab and your cloud agents are right there.

The idea

​
The same interface, wherever you are.

The web app shares exactly the same interface as the desktop app — same tabs, same agent studio, same marketplace. The difference is runtime: some features need the Actionist desktop process running locally.

9
features fully available in the browser today
3
surfaces coming soon — shown honestly, not hidden
2
surfaces that stay desktop-only by design
0
broken buttons — gap cards replace them

Full interface on day one

Agent studio, marketplace, workflow viewer, calendar, and the Cloud Runtime tab all work in the browser today. Set up agents, browse skills, and manage your cloud runtime without installing anything.

Honest gap cards, not broken buttons

Surfaces that need Electron — local-agent chat, custom MCP server management, and memory for local-desktop agents — show a clear informational card instead of a dead button. You always know what works today and what is coming soon.
Try it · surfaces

​
Same agent. Two surfaces.

The same agent card renders differently depending on where you are. Switch to see the VPS badge, the gap card, and the parity — exactly as it looks in the app.

M
Maya
CRM agent
VPS
Chat with agent
R
Rover
Research agent · local
Coming soon · CHT-001
Chat with local-desktop agents is coming to the browser. Move this agent to VPS to chat now.
web app · app.actionist.ai · Agents tab
M
Maya
CRM agent · VPS
Chat with agent
R
Rover
Research agent · local
Chat with agent
desktop app · Agents tab · all agents can chat locally
The three “coming soon” surfaces show a purple informational card in the browser — not an error. You can continue using the rest of the app normally.
Desktop vs web

​
What works where.

Everything you can do in each surface today. Three gaps are “coming soon” — not “desktop only forever”.

FeatureWeb appDesktop app
Sign in (same Clerk account)YesYes
Agent studio — identity, tools, skills, scheduleYesYes
Marketplace — browse and install MCP serversYesYes
Workflow viewerYesYes
CalendarYesYes
Cloud Runtime tabYesYes
Chat with a VPS-home agentYesYes
Chat with a local-desktop agentComing soon (CHT-001)Yes
Agent memory for local-desktop agentsComing soon (AGT-014)Yes
Add custom MCP serversComing soon (MCP-CUSTOM)Yes
Screen recording / local computer useDesktop onlyYes
Move agent to VPSDesktop onlyYes
app.actionist.ai/agents
AgentsMarketplaceWorkflowsCalendar
M
Maya
CRM agent
VPS
Chat with agent
R
Rover
Research agent · local
Coming soon · CHT-001
Chat with local-desktop agents is coming to the browser. Move this agent to VPS to chat now.
Browser chat

​
Watch the connection open.

Cloud (VPS-home) agents are fully chat-enabled from the browser. Step through the live flow — from Connecting to Working to a completed reply with a file attachment uploaded.

app.actionist.ai/agents/maya/chat
MayaConnecting…ConnectedWorking…
StopStart fresh
Connecting to Maya…
session open · last 200 messages loaded
YouCan you pull the Northwind account summary?
MayaSure — fetching from CRM now.
Composer active. Drop files or send a message.
YouCan you pull the Northwind account summary?
MayaSure — fetching from CRM now.
YouAlso attach this for context.
northwind-q3-brief.pdf — uploading…
YouCan you pull the Northwind account summary and cross-reference the Q3 brief I just attached?
northwind-q3-brief.pdf — uploaded
Maya
YouCan you pull the Northwind account summary and cross-reference the Q3 brief I just attached?
northwind-q3-brief.pdf — uploaded
MayaNorthwind — enterprise tier, renewal October, champion Dana Voss. Q3 brief matches: slide format confirmed, renewal risk flagged. Two open invoices. Want me to draft the renewal prep email?
Message Maya…
“Connected” and “Working” are independent. Connected = the SSE stream is open. Working = the agent is running. A brief reconnect during a run auto-resyncs without losing context.
Upload only after “Connected”. Files silently no-op if the header still shows “Connecting…”. Wait for the green dot before dropping attachments.
Retry uses the original key. A failed message shows an error chip — always use Retry, never retype. The deduplicate key prevents double-sends even if the original was stored before the ack failed.
In the wild

​
Run your store from a sun lounger.

A VPS-home agent keeps running while you are away. Open the web app on your phone, ask a question, approve what needs approving — done.

J
@june_actionist_bot
ONLINE
Give me the weekend order summary — Friday close to now. 10:14
SEEN · READING CONTEXT
TOOL · FETCH_ORDERS
Weekend snapshot (Fri 18:00 – Sun 10:14):
Orders placed: 312
Fulfilled: 287
Awaiting fulfilment: 22
Refund requests: 3 (1 flagged for manual review) 10:14
Show me the flagged refund. 10:15
TOOL · GET_REFUND_DETAIL
Order #ORD-9820 · placed Fri 14:32Item: Linen tote bag (qty 1) — carrier marked delivered but customer reports non-arrival. Tracking last ping: local depot Fri 17:11. No further scan.Flagged: carrier gap over 48 h
ApproveDeny
Approve it — carrier’s fault, not theirs. 10:16
TOOL · ISSUE_REFUND
Done. Refund issued for order #ORD-9820. Customer notified automatically. 2 remaining refund requests are standard policy — no manual review needed. 10:16
The web app works on any mobile browser — no app store install required. Open app.actionist.ai, sign in once, and your VPS agents are available from any device.
app.actionist.ai/agents/maya/chat
MayaConnectedWorking…
StopStart fresh
YouCan you pull the Northwind account summary and cross-reference the Q3 brief?
northwind-q3-brief.pdf — uploaded
MayaNorthwind — enterprise tier, renewal October, champion Dana Voss. Q3 brief matches: slide format confirmed, renewal risk flagged.
YouDraft the renewal prep email.
Maya
Message Maya…
The flow

​
Chatting with a cloud agent.

Cloud (VPS-home) agents are fully chat-enabled from the browser. Here is the full flow from landing on the Agents tab to having a conversation.

Sign in

Open the web app in any browser. The Clerk sign-in page appears — use the same email/password or SSO as your desktop app. Your agents, settings, and workspace carry across automatically.

Find a cloud agent

On the Agents tab, look for a VPS badge on the agent card. Only VPS-home agents support browser chat today. The “Chat” button tooltip reads “Chat with agent”.

Open the chat

Click Chat. The browser navigates to the agent’s chat page. The header shows “Connecting to [name]…” while the session opens, then “Connected” once it is ready. The conversation history loads up to the last 200 messages.

Send a message

The composer placeholder reads “Message [name]…”. Type a message and send it; use a newline for multi-line messages. The header switches to “Working…” while the agent runs.

Attach files

Drop files onto the composer at any time after “Connected” appears. Each file shows a progress chip while uploading. A failed attachment shows an error chip with the file name — it does not block other attachments from sending.

Stop or start over

Click Stop (visible while “Working…”) to halt the agent mid-run. The header briefly shows “Stopping…”. To clear the conversation and start a blank session, click Start fresh in the top-right — a confirmation dialog appears before the session resets.
Controls

​
Understanding the chat header.

Reflects the SSE stream health, not whether the agent is running. A brief reconnect during a run is normal — run state auto-resyncs.
Shown alongside Stop when the agent is actively executing. Independent of the connection indicator.
Sends a halt signal mid-run. Header shows “Stopping…” briefly, then a terminal chip: Stopped, Completed, Turn limit reached, Timed out, or Failed.
Creates a new session ID and clears the visible log. Agent memory is not deleted. Terminal chips do not persist across reload.

Connection indicator — 'Connected' / 'Connecting…'

The header shows “Connecting…” while the SSE stream is opening and “Connected” once it is live. This is independent of run state — “Connected” simply means the channel is open. A brief reconnect during a run is normal; the app auto-resyncs run state from the backend without losing context.
While the agent is running, a Stop button appears in the header alongside the “Working…” label. Clicking it sends a stop signal. The header transitions to “Stopping…” briefly, then shows a terminal chip — “Stopped” — when the run ends. Other possible terminal chips: “Completed”, “Turn limit reached”, “Timed out”, “Failed”.
Terminal chips are client-only state and do not persist across page reload. Reload the page to clear them.
“Start fresh” in the top-right opens a confirmation dialog before clearing the chat. Confirming creates a new session ID and discards the client-side history. The agent’s memory is not deleted — only the visible conversation log is cleared.
A failed message from the old session cannot be retried after Start fresh. If you have a pending retry, use Dismiss first if you do not want to send it — then start fresh.
If a message fails to send, a red error chip appears: “Your message didn’t send. Try again.” with Retry and Dismiss buttons. Always use Retry rather than retyping the message — the retry carries the original deduplicate key, so the backend will not create a duplicate even if the original was persisted before the acknowledgement failed.
Cloud migration

​
Moving an agent to the cloud.

Moving a local-desktop agent to the cloud (VPS) enables browser chat and keeps the agent running 24/7 — even when your computer is off. This step is done from the desktop app.

Agent StudioOpen the agent on your desktop app. Confirm “All changes saved”.
PreflightMove to VPS dialog runs checks: agent, dependencies, channels, memory.
Resolve blockersFix anything in “Fix before moving”. Review warnings. Inspect the transfer manifest.
ProvisioningCloud Runtime steps: Provisioning → Starting → Active → Ready. Auto-polls every 4 s.
VPS badgeReady status + heartbeat within 90 s unlocks the Chat button in the web app.

Open Agent Studio on the desktop app

In the Actionist desktop app, go to the Agents tab and click the agent card to open Agent Studio.

Save all pending changes

The Move to VPS button in the Studio header is disabled if there are unsaved changes. Confirm the status reads “All changes saved” before proceeding.

Click Move to VPS

Click Move to VPS in the Studio header bar. A dialog opens with the title “Move [name] to VPS” and begins the preflight check: “Checking agent, dependencies, channels, and memory…”

Resolve blockers and review warnings

The preflight dialog shows three sections:
  • “Fix before moving” — blockers that must be resolved before the move can proceed.
  • “Warnings” — advisory notices that do not block the move.
  • “What moves” — the full transfer manifest: memory files, skills, MCP servers, schedules, triggers, and channels (Telegram and Slack).
Resolve any blockers, then click Move to VPS to confirm.

Monitor provisioning in Cloud Runtime

After confirming, navigate to Settings → Cloud Runtime in the desktop or web app. The provisioning stepper progresses through Provisioning → Starting → Active → Ready. The page auto-polls every 4 seconds while the status is settling.

Chat from the browser

Once the Cloud Runtime status is Ready (active with a heartbeat within the last 90 seconds), a VPS badge appears on the agent card in the web app. The Chat button becomes active — click it to open the browser chat.
After the move, the agent’s schedules, triggers, and Telegram/Slack channels all continue running from the cloud — no desktop app required.
Agent Studio — Move to VPS
Move Maya to VPS
Preflight checks
✓Agent configuration — valid
✓Dependencies — all resolved
✓Channels — Telegram connected
✓Memory — 3 files ready to transfer
What moves
Memory files3 files
SkillsCRM, Scheduler
Schedules2 active
ChannelsTelegram
Move to VPS
Status

​
Checking Cloud Runtime status.

1
VPS allocated
2
Runtime booting
3
Process live
4
Heartbeat within 90 s

Open Cloud Runtime

Go to Settings → Cloud Runtime. The tab is available from both the web app and the desktop app.

Read the provisioning stepper

The stepper shows four stages: Provisioning → Starting → Active → Ready. The page auto-polls every 4 seconds while the status is Provisioning or Starting. You can leave the page — provisioning continues in the background.

Verify Ready status

Ready means the runtime is active and the last heartbeat arrived within the past 90 seconds. If the runtime is active but the heartbeat is stale, the UI shows “Starting” until a fresh heartbeat arrives. Click Refresh to manually re-poll.
The Cloud Runtime tab shows: “Your plan doesn’t include a cloud runtime” with an Upgrade plan button that opens the billing upgrade flow. You must be on a plan that includes the hosted runtime before provisioning begins. See Billing for plan details.
A suspended runtime shows: “Your cloud runtime is suspended.” Update your billing to resume your hosted runtime. Your data is retained while suspended.
app.actionist.ai/settings/cloud-runtime
AccountBillingCloud Runtime
✓
Provisioning
✓
Starting
✓
Active
Ready
Regioneu-west-1
Versionruntime-2.4.1
Last heartbeat12 s ago
TelegramConnected
Best practices

​
Tips for the web app.

The Move to VPS button is disabled until the studio shows “All changes saved”. Clicking it with unsaved changes shows a tooltip: “Save changes before moving this agent.” — no dialog opens. Save first, then migrate.
After a send failure, always use the Retry button in the error chip rather than retyping the message. Retry reuses the original deduplicate key, so the backend will not create a duplicate message even if the original was stored before the acknowledgement failed. A retyped message carries a new key and creates a second message.
File uploads start only after the session is open. If you drop a file while the header still shows “Connecting…”, the upload silently no-ops. Wait for “Connected” before attaching anything.
“Connected” / “Connecting…” reflects the health of the SSE stream; “Working…” reflects whether the agent is actively running. A brief reconnect during a run is normal — the app auto-resyncs run state from the backend and restores “Working…” without you doing anything.
Reloading the page during an active run is safe. The chat hook re-fetches the last 200 messages and re-checks the active run ID on mount, so the “Working…” state is restored automatically.
If the Cloud Runtime tab shows the “Upgrade plan” CTA, upgrade your plan first. Moving an agent to VPS requires an entitlement — the move is blocked until the plan includes a hosted runtime.

​
Your agents don’t clock out.

Move an agent to the cloud. Close your laptop. Open any browser and pick up where you left off.

Open the web appEmail the team

Same account. Same agents. Any browser.
Honest about gaps · No broken buttons · Auto-resync on reconnect.

Keep going

​
Next steps.

Cloud Runtime

Provision and manage the hosted runtime that keeps your cloud agents running 24/7.

Agents

Configure Agent Studio, approval modes, and use Move to VPS to migrate a local agent to the cloud.

Channels

Connect Telegram or Slack so local-desktop agents are reachable even before web chat is available for them.

Billing

Upgrade to a plan that includes a hosted runtime and unlock browser chat for all your agents.