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.
Actionist is a web app. The browser gives you the whole interface: agent studio, marketplace, workflow viewer, calendar, and chat. A short list of features still needs the desktop build, and that list is below.
7
features fully available in the browser today
3
surfaces coming soon, shown rather than hidden
1
surface that needs a local machine
0
broken buttons, because 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
Where a surface is not ready in the browser yet, you get a card explaining why instead of a button that does nothing. You can always tell what works today and what is still coming.
Try it · surfaces
Same agent. Two surfaces.
The same agent card renders differently depending on where you are. Switch between the two to compare.
M
VPSR
Coming soon
Browser chat for agents running on your own machine is coming. Cloud agents can chat here today.
web app · app.actionist.ai · Agents tab
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 of these gaps are being closed, so treat them as temporary rather than permanent.
AgentsMarketplaceWorkflowsCalendar
M
VPSR
Coming soon
Browser chat for agents running on your own machine is coming. Cloud agents can chat here today.
Browser chat
Watch the connection open.
Cloud 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.
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 cloud 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
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.
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 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 cloud badge on the agent card. Only cloud agents support browser chat today. If the Chat button is inactive, the agent is not running in the cloud.
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…'
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.
Stop — halt a run mid-flight
Stop — halt a run mid-flight
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 — reset to a new session
Start fresh — reset to a new session
“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.
Retry — recover from a send failure
Retry — recover from a send failure
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 placement
Where an agent runs.
An agent placed in the cloud keeps running when your computer is off, so its schedules, triggers, and channel bots carry on without you. Placement is handled for you. There is no Move to VPS button in Agent Studio and no migration dialog to work through.
If you are looking for a control to move an agent to the cloud, there is not one. Check the agent’s current placement in Settings → Cloud Runtime, which is available in the web app.
Cloud runtime in depth
Placement, status, and what changes when an agent runs in the cloud.
Status
Checking Cloud Runtime status.
1
VPS allocated2
Runtime booting3
Process live4
Heartbeat within 90 sOpen 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.
Plan does not include a cloud runtime
Plan does not include a cloud runtime
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.
Runtime is suspended
Runtime is suspended
A suspended runtime shows: “Your cloud runtime is suspended.” Update your billing to resume your hosted runtime. Your data is retained while suspended.
AccountBillingCloud Runtime
✓
Provisioning✓
Starting✓
ActiveReady
Regioneu-west-1
Versionruntime-2.4.1
Last heartbeat12 s ago
TelegramConnected
Best practices
Tips for the web app.
Retry is safe; retyping is not
Retry is safe; retyping is not
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.
Wait for 'Connected' before attaching files
Wait for 'Connected' before attaching files
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.
Connection and run indicators are independent
Connection and run indicators are independent
“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.
Reload is safe during a run
Reload is safe during a run
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.
Upgrade before moving if your plan does not include a runtime
Upgrade before moving if your plan does not include a runtime
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.
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, pick the tools an agent can use, and set its approval mode.
Channels
Connect Telegram or Slack so an agent is reachable from your phone.
Billing
Upgrade to a plan that includes a hosted runtime and unlock browser chat for all your agents.