Language, billing, encrypted credentials, headless runtime, and your assistant preferences — no hunting across menus. Change anything here, and every agent picks it up immediately.
The Settings page is a single card-grid scroll. Select a section to see its key rows, access badges, and platform notes.
🌐
LanguageAll users
App language
Selects UI locale for the entire app
English (US)
22 locales available
Includes Arabic, Farsi, Urdu (RTL)
desktop + web
No save needed
Changes take effect the moment you select a locale
instant
The Language card is at the top of Settings. Pick any locale from the dropdown — the entire app UI, including Clerk sign-in components and RTL layout direction, switches in a single render cycle. No restart. Saved locally; survives backend outages.
💵
Billingadmin only
Plan
Current subscription tier
Pro
Status
Active, trialing, or past-due
Active
Renewal date
End of current billing period
Jul 11, 2026
Seats
Seats on the plan
5
Credit usage bar
Used + reserved vs ceiling this period
below the grid
Visible only to org admins (and delegated sessions with the billing_summary scope). Non-admin members see no Billing card at all. Two actions: Upgrade to Pro (opens Stripe portal, hidden when already on business plan) and View billing details (navigates to /settings/billing-new).
🔒
Credentials Vaulthidden in delegated sessions
Add credential
Display name, provider, kind, value
API key, Token, Header, OAuth
Test now
Validates against the provider where supported
pass
Rotate
Requires credential to be enabled first
all bindings auto-update
Delete
Gated — blocked until all consumers are unbound
unbind consumers first
Paired runtimes
Cloud + VPS identities authorised for your workspace
sub-panel inside vault
Values are encrypted at rest and never shown after save — no reveal button, no clipboard copy. If a key is lost, rotate rather than recover. The Credentials Vault card is hidden entirely when a delegated session is active.
🖥️
Headless Runtimedesktop only
Run Locally
Runtime on your machine — good for testing
Deploy to VPS
Always-on runtime over SSH — no server scripting
Telegram Bot Token
From @BotFather — the only required field for local mode
required
Clerk M2M secret
Never stored by Actionist — re-enter on every VPS deploy
not stored
Desktop-only — the card does not appear in the web build. Two modes: Run Locally keeps the runtime on your machine (good for testing), Deploy to VPS deploys over SSH for always-on agents. After a successful VPS deploy three buttons appear: Check Status, Logs, and Stop.
⚡
Help Assistant (Pip)All users
Calm mode
Freezes idle animation, silences all contextual tips
Hide for an hour
Removes Pip for exactly 60 minutes — shows resumption time
timed
Proactive nudges
Off by default — fires only for concrete gaps
Tip catalog
Per-tip on/off toggle — disable a tip once, never see it again
fine-grained
Reset Pip’s position
Returns Pip to bottom-right corner
Reset
Four separate dials for Pip — from a full mute to a tip-by-tip opt-out. Calm mode keeps Pip visible but still and silent (good for long focused sessions). Hide for an hour removes Pip entirely for exactly 60 minutes (good for presentations). These two are distinct — use whichever fits the moment.
🖥️
Permissions RequiredmacOS only
Screen Recording
Lets Actionist read on-screen state for Computer Use
Granted
Accessibility
Lets Actionist click, type, and navigate apps on your behalf
Not granted
Grant access
Opens macOS System Settings at the correct pane
opens System Settings
The Permissions Required card only appears on macOS — determined at runtime by the system platform. Not shown on Windows or Linux. Both Screen Recording and Accessibility are required for any agent using Computer Use. Grant them here if you skipped the first-run onboarding prompt.
↑
App Updatessticky footer
Current version
Shown in the sticky footer at the bottom of Settings
v2.4.1
Check for Updates
Shows Checking… while querying the update server
Up to date
Auto-reset
Both pass and fail states reset to idle after 5 seconds
5 s
The version footer is sticky at the bottom of the Settings page — always visible as you scroll. Click Check for Updates to query the update server. If the check fails, an amber Update check failed message appears. Both states auto-reset after 5 seconds — most failures are transient network blips; click again to retry.
Actionist ships with 22 locales out of the box — including three right-to-left languages. Pick one and the entire app UI changes immediately. No save button, no restart.
Select a locale to see the switch behavior
Locale saved locally. The entire app UI switches in one render cycle — no restart required. The setting survives app restarts and backend outages.RTL locale selected. The app layout direction flips to right-to-left immediately, including the sidebar and Clerk sign-in components. Saved locally — survives backend outages and restarts.
1
Open Settings
Click Settings in the sidebar. The Language card is at the top of the page.
2
Open the dropdown
Click the language dropdown. Each locale shows its country flag and name.
3
Pick a locale
Select any of the 22 supported locales. The entire app UI switches instantly — including Clerk sign-in components and layout direction for RTL languages.
The chosen language is saved locally and survives app restarts, even if the backend is unreachable.
Our Tokyo, Berlin, and Cairo teams all use the same workspace. One locale switch and Actionist is native for everyone — no separate instances, no config drift.
The Billing card is only visible to org admins. Non-admin workspace members do not see it. Delegated sessions with the billing_summary scope can also view it.
The card gives a four-column summary of your subscription. Below the grid, a usage bar shows how much of your credit ceiling you have consumed and reserved so far this period.
Plan
Pro
Current subscription tier
Status
Active
Active, trialing, or inactive. A past-due banner shows the grace-period end date when payment is overdue.
Renewal date
Jul 11
End of current period
Seats
5
Seats on the plan
Credit usage this period
42% consumed + reserved
Upgrade to Pro
Opens the Stripe billing portal. Hidden when you are already on the business plan.
View billing details
Navigates to the full billing page at /settings/billing-new inside the app.
API keys, bot tokens, and OAuth credentials live here — encrypted at rest, never revealed after save, and automatically propagated to every bound agent when you rotate them.
Credential values are encrypted in the vault and never shown after save. There is no reveal button and no clipboard copy of secrets. If you lose a key, rotate it — do not try to recover it from Actionist.
Find the Credentials Vault section and click Add credential.
2
Fill the form
Enter a Display name, a Provider identifier (e.g. github), a Kind, and the Value. Use the show/hide toggle while typing to confirm the value.Supported kinds: API key, Token, Header secret, Client credentials.
3
Click Save credential
The value is encrypted immediately. It is never retrievable after this point.
Test a credential
Find the credential card and click Test now. Actionist probes the provider:
Supported providers — validated against the real provider API.
All other providers — structural validation (format and length check).
A badge appears on the card: a green check for a passing test, an amber warning with a reason for a failure.
Rotate a credential
1
Confirm the credential is enabled
The Rotate button is blocked for disabled credentials. If the status shows Disabled, click Enable first. The tooltip reads: “Enable before rotating.”
2
Click Rotate
Paste the new secret value into the form that appears.
3
Confirm
Click to save the new value. All existing bindings — agents, skills, channels, MCP servers — pick up the new value automatically on their next call. No manual re-binding required.
Existing bindings keep working during and after rotation — they pick up the new value on next use.
Disable and enable a credential
Click Disable on a credential card to pause it without deleting it. Disabled credentials show an amber Disabled status badge. Bound consumers will fail until you re-enable.Click Enable to restore it. If you need to rotate a disabled credential, you must enable it first.
Delete a credential
The Delete button is intentionally gated. It stays disabled as long as any consumer references the credential.
1
Remove all bindings
The card lists every consumer under “Used by” — agents, model presets, skills, channels, MCP servers. Remove those references first. The tooltip reads: “Unbind consumers first.”
2
Verify usage is clear
If the Delete button shows “Refresh to verify usage before deleting”, click the vault Refresh button to re-check.
3
Click Delete and confirm
Once all bindings are removed, Delete becomes active. Confirm in the dialog to permanently remove the credential.
The Paired runtimes sub-panel inside the Credentials Vault shows the cloud and VPS machine identities that are authorised to act on behalf of your workspace. Each entry shows a label, a host hint, a last-seen timestamp, and a status badge.
1
Click Pair runtime
A fresh one-time pairing code is generated and displayed.
2
Paste the code into the runtime
Copy the code and paste it into the runtime process immediately.
The pairing code is shown exactly once. Once you close the dialog it is gone — Actionist does not store it. Treat it like a password.
3
Confirm the new identity appears
The runtime entry appears in the Paired runtimes panel with its label, host hint, and last-seen time.
To revoke a runtime, click the revoke action on its entry. Revocation is immediate and permanent — a new pairing code is required to re-authorise.
The Credentials Vault is hidden entirely when a delegated session is active.
Headless Runtime keeps scheduled agents firing and Telegram bots responding around the clock — either on your local machine for testing or deployed directly to a VPS from within the app.
Headless Runtime is a desktop-only feature. The card does not appear in the web build.
👤
You
⇅
Mode
Run Locally / Deploy to VPS
💻
Local Runtime
your machine
💬
Telegram bot
🏢
VPS Runtime
your server
💬
Telegram bot
🔑
SSH deploy
no scripting
Settings — Headless Runtime
Run LocallyDeploy to VPS
Connection
Host
Port: 22
Username
SSH Private Key path
Browse
Authentication
Clerk M2M secret (ms_…)
Test ConnectionDeploy to VPS
Run Locally
Deploy to VPS
Use this mode to run the agent runtime on your own machine. Good for testing before you have a VPS provisioned.
1
Select Run Locally
In the Headless Runtime card, select the Run Locally tab.
2
Enter your Telegram Bot Token
Paste the bot token from @BotFather. This is the only required field.
3
Optionally restrict to specific users
Enter a comma-separated list of Telegram User IDs in the Allowed User IDs field to prevent strangers from messaging your bot.
4
Click Start Runtime
The status badge transitions: Stopped > Starting… > Running. When running, the badge shows the Telegram logo and “Connected.”
5
Stop when done
Click Stop Runtime to halt the local process.
Use this mode for persistent, always-on runtime. Actionist deploys over SSH — no server scripting required.
1
Select Deploy to VPS
In the Headless Runtime card, select the Deploy to VPS tab.
2
Fill in the Connection section
Enter the Host, Port (default 22), and Username for your server. Then enter the path to your SSH Private Key or click Browse to pick the file. Click Test Connection to verify access before deploying.
3
Paste the Clerk M2M machine secret
Under Authentication, paste your Clerk M2M machine secret (format: ms_…). This value is not stored — you will need to enter it again on the next deploy.
Keep the Clerk M2M secret in a password manager. Actionist never stores it locally — you must re-enter it each time you deploy.
4
Set up the Telegram Gateway
Paste your Bot Token and optionally set Allowed User IDs.
5
Click Deploy to VPS
If an existing paired runtime is active, a confirmation dialog lists the existing identity and its last-seen time before you proceed. Confirm to replace it.
6
Monitor the deployment
After a successful deploy, three buttons appear: Check Status, Logs (shows the last 50 lines in a scrollable panel), and Stop.
Advanced port settings: health port defaults to 9090, file-proxy port defaults to 7783. Leave the Base URL and File Proxy Secret blank unless you need the web dashboard file panel — the runtime and Telegram features work without them.
Pip is the always-on Actionist concierge. The Help Assistant section gives you four separate dials — from a full mute to a tip-by-tip opt-out — so Pip is as helpful or as quiet as you want.
Calm mode
Freezes Pip’s idle animation and suppresses all contextual tips. Pip remains visible but completely still. Good for long focused sessions.
Hide for an hour60 min
Removes Pip entirely for exactly 60 minutes. While active, the button label becomes Show Pip again and shows the resumption time. Good for presentations.
Proactive nudges
Off by default. When enabled, Pip surfaces concrete action items inline: an agent missing a model preset, an MCP server waiting for auth, pending marketplace updates. You can also opt in during onboarding.
Tip catalogfine-grained
Lists every registered tip with an individual on/off toggle. Disable a tip to prevent it from ever firing again. Re-enable at any time. Keep the tips you find useful, silence the ones you do not.
If you have dragged Pip to an inconvenient location, click Reset under “Reset Pip’s position.” Pip returns to the default bottom-right corner of the screen.
The Permissions Required card only appears on macOS. It is not shown on Windows or Linux — the gate is determined by the system platform at runtime.
Actionist needs two macOS permissions to observe your screen and control UI elements for Computer Use. Without both, agents that rely on screen automation cannot run.
Screen Recording macOS only
Allows Actionist to see your screen. Required for any agent that uses Computer Use to read on-screen state.
Accessibility macOS only
Allows Actionist to control UI elements. Required for any agent that clicks, types, or navigates apps on your behalf.
1
Click Grant access
For each permission not yet granted, click the Grant access button on its row.
2
Approve in System Settings
macOS System Settings opens at the correct pane. Toggle the permission on for Actionist.
3
Return to Actionist
Switch back to the app. The permission row updates to reflect the granted status.
These permissions are also requested during first-run onboarding. If you skipped them then, grant them here any time — agents will start using Computer Use the next time they run.
Use Test now to confirm the current key is still valid before rotating. If it is already broken, rotating wastes a round-trip of updating every dependent agent — you will know immediately that a fresh key is needed.
The Delete button is an intentional safety gate
The Delete button stays disabled as long as any consumer — agent, model preset, skill, channel, MCP server — references the credential. Read the tooltip: it tells you exactly what is blocking deletion (“Unbind consumers first”). This prevents silent breakage across your workforce.
Language switching is instant and offline-resilient
The chosen locale is saved locally on your device, not to the backend. It survives app restarts and backend outages. There is no separate save step — the change takes effect the moment you select a locale.
VPS Clerk M2M secret: keep it in a password manager
The Clerk M2M machine secret (ms_…) is never stored by Actionist — by design. You re-enter it on every deploy. Store it in a password manager alongside your other deployment secrets.
Calm mode vs Hide for an hour
These two controls are distinct. Calm mode keeps Pip visible but freezes the animation and silences tips — good for long focused sessions. Hide for an hour removes Pip entirely for exactly 60 minutes — good for presentations or calls where you do not want the character visible.
Tip catalog for fine-grained Pip control
If one specific tip fires too often but others are useful, disable only that one in the Tip catalog. It will never fire again unless you re-enable it. You do not have to choose between all tips or no tips.
Proactive nudges are low-noise by default
Nudges are off until you opt in. When enabled, they fire only when Pip detects a concrete gap: an agent without a model preset, an MCP server waiting for auth, or pending marketplace updates. They are not marketing prompts.
Update check errors are usually transient
If Check for Updates returns “Update check failed,” the button auto-resets after 5 seconds. Click it again — most failures are network blips.
Credentials encrypted at rest, never revealed after save.
Language saved locally · Vault-backed secrets · Per-agent scoping · Nothing leaves your workspace.
