AN OPERATING SYSTEM FOR AI EMPLOYEES
Describe the outcome. Actionist ships it.
Give an agent a role, the tools, and a sentence describing what you want. It plans the steps, does the work across your real apps, and reports back, then keeps doing it on a schedule. No node graphs, no cron syntax, no glue code.
One sentence in, a standing automation out
Watch a request become a recurring job.
This is the whole product in one exchange: you describe the result, Actionist drafts a plan, runs it across your tools, and (because you asked for “every weekday”) turns it into a schedule that fires without you.
youEvery weekday at 9am, pull yesterday’s closed Linear tickets and post a digest to #engineering.
plan drafted · 4 steps · agent: Ops
opsPulled 12 closed tickets from Linear and grouped them by project.
opsDrafted the digest in your voice and posted to #engineering. Reactions already coming in.
schedule created · weekdays 09:00
opsDone. Next digest posts tomorrow at 09:00. I’ll take it from here.
Why it’s different
Three things most automation tools can’t do.
Local-first by design
Agents run on your own machine or a private cloud runtime you control. Your files, your credentials, your hardware, not a black box in someone else’s data center.
Any app, even without an API
When there’s no integration, Computer Use sees the screen and clicks. Actionist operates legacy portals, internal dashboards, and desktop apps the way a person would.
Works while you sleep
Schedules, event triggers, and Telegram or Slack bots keep agents running when the app is closed and your laptop is shut. Headless Runtime never clocks off.
The shift
Not a chatbot. A workforce.
A chatbot waits for you to ask, then forgets. An Actionist agent owns a role, remembers across sessions, uses your real tools, and shows up to work on its own.
A chatbot
Answers only when you type, then the thread goes cold.
Forgets everything the moment you close the tab.
Can’t touch your tools, files, or customers, it just talks.
Every task starts from zero context.
An Actionist agent
Owns a role and a routine. It knows what it’s responsible for.
Remembers decisions, preferences, and context across every run.
Acts through your real apps over MCP: Slack, Notion, Linear, Stripe.
Runs on a schedule, reacts to events, and escalates only when genuinely stuck.
Stop prompting a tool. Start delegating to an employee.
the difference Actionist is built aroundReal work, handled
What people hand to Actionist.
Four teams, four recurring headaches, one operating system. Each recipe runs on a schedule, fires from a webhook, or wakes up as a Telegram bot, no manual trigger needed.
Dario · Sales
Every evening, pull new CRM contacts added that day, score them by fit, and draft a personalised first-touch email for each. Strong matches auto-enqueue; borderline leads land in a Slack digest for a quick approve-or-skip.
saves ~3 hrs/day
June · E-commerce founder
Watch the orders inbox. Any refund or “where is my order” message gets triaged instantly, shipping status looked up, a reply drafted, the ticket closed or escalated. A nightly summary of open disputes lands in Telegram at 21:00.
saves ~2 hrs/day
Felix · Finance and Ops
Every Monday at 08:00, pull the prior week’s expenses, match each line to a budget category, flag anything over threshold, and post the reconciliation report to Notion, ready for finance review before standup.
saves ~4 hrs/wk
Lena · Recruiter
When a new applicant hits the ATS, read the CV, score it against the job spec, and draft a structured interview invite or a polite decline. Within ten minutes of submission. Shortlisted candidates get a calendar link pulled from the hiring manager’s live availability.
live in 10 min
A typical week, reclaimed
Actionist · illustrative totals across the recipes above
Dario · pipeline outreach + digest~15 hrs
June · order triage + dispute summary~10 hrs
Felix · expense reconciliation report~4 hrs
Lena · CV screening + calendar invites~6 hrs
Reclaimed per week~35 hrs
ILLUSTRATIVE, BASED ON THE RECIPES ON THIS PAGE
The platform
Six ideas. One operating system.
Everything in Actionist is built from six native concepts. Learn one and the rest fall into place, each links to its full guide.
Agents
The “who”. AI employees with their own role, instructions, tools, and memory. One agent per job, no sprawling generalists.
Workflows
The “how”. Multi-step processes you design and schedule through conversation, from a single task to a recurring pipeline with approval gates.
Skills
Reusable, tested playbooks an agent loads at runtime. Author once, enable on any agent, publish to the marketplace.
Memory
Permissioned, plain-Markdown recall: company context, agent-private knowledge, uploaded documents. The agent sharpens over time instead of forgetting.
Computer Use
Vision-driven screen automation. When there’s no API, Actionist sees and clicks, driving any desktop or browser app on your behalf.
Integrations
Anything that speaks MCP: Slack, Notion, Linear, Stripe, and a growing catalogue. Bring your own server with one line of config.
From sentence to ship
What happens when you press run.
Every trigger (a chat message, a schedule, an incoming webhook) flows through the same five stops.
YouDescribe the outcome in plain language, or let a schedule or webhook fire it.
PlanActionist drafts the steps, picks the agent, and gates anything destructive for approval.
ActThe agent executes through Skills, MCP servers, and Computer Use, streaming live.
ReportOutputs, artifacts, and a full audit trail of every tool call.
RepeatWhat worked once goes on a schedule, behind a webhook, or into the marketplace.
Executes throughSkillsMCP serversComputer Use
Who it’s for
A solo operator, a whole team, or a reseller’s book of clients.
- Solo operator
- Team
- Reseller
Reclaim the busywork
Triage your inbox, draft replies, file receipts, summarize PDFs. Hand off the repetitive 30% of the day that pays nothing.
One laptop, a full bench
Spin up a research agent, a CRM agent, an inbox agent. They share your context and run from the same chat, and keep going from the cloud when you close the lid.
Quickstart
Your first agent, before your coffee’s cold.
Four moves from download to a working, scheduled agent. The full walkthrough lives in Getting started.
Install and sign in
Download for Mac or Windows from the dashboard and sign in through your browser, no new password. Full setup in Getting started.
Describe a task
Open the composer on Home and say what you want: for example, “Every weekday at 9am, post yesterday’s closed Linear tickets to #engineering as a digest.”
Approve the plan
Actionist drafts the steps and waits for your go-ahead. Edit any step, swap the agent, or pin a model before it runs.
Let it run on its own
Because you said “every weekday”, it becomes a schedule. Cloud and VPS keep it firing while your laptop is closed.
Ready when you are
Hire your first AI employee today.
Open the dashboard, describe a task, and watch Actionist do the rest.