Actions

Memory is how Lucien understands your company. Copilot is how you talk to it. Actions are how Lucien actually does things in the real world.

You can think of an Action as:

A proposed change in one of your tools — drafted by Lucien, approved (or edited) by you.

What counts as an Action?

Examples of Actions Lucien can draft or execute:

Messages
- Draft a Slack message in #sales to follow up on a stalled deal.
- Draft an email to a customer about a renewal, failed payment, or trial.
Tasks
- Create a Linear/issue tracker task for a recurring support issue.
- Add a task to your founder OS in Notion for a key decision or follow‑up.
Updates
- Append a “This Week” or “Risks” section to a Notion page.
- Post a weekly summary into #leadership or #company-updates.

Each Action has:

Lucien’s default lifecycle for Actions is deliberately strict:

Draft – Lucien proposes an Action and shows you exactly what it would do.
Approve or edit – you can accept, tweak, or reject the draft.
Execute – only after approval does Lucien call the underlying integration (Slack, email, Notion, etc.).

This is surfaced in places like:

Unless you later opt into more autonomy for specific flows, nothing happens without an explicit yes from you or someone you designate.

The three concepts fit together like this:

Memory – provides the context: metrics, events, docs, Slack threads, previous decisions.
Copilot – the conversation where you ask for help and review what Lucien proposes.
Actions – the concrete operations Lucien can take once you’re happy with the plan.

A typical loop:

You ask Copilot: “Identify trials idle more than 3 days and draft follow‑ups.”
Lucien queries memory (product usage, trials, past conversations).
It produces a short list of Actions: one per account, each with a drafted message.
You scan the list, approve the ones you like, edit a few, and dismiss the rest.
Lucien executes only the approved Actions.

This keeps Lucien useful and safe.

From your point of view there are two main flavors of Actions:

Inline actions
- Small affordances that show up next to a message or suggestion – for example, a button to “Create task”, “Schedule retries”, or “Draft reply”.
- Designed to let you move quickly while you’re already looking at a specific item.
Queued actions
- A more structured list, often in the Action queue or your daily brief.
- Used for larger sweeps, like “all churn‑risk renewals this month” or “all failed payments in the last 24 hours.”

Under the hood, both go through the same approval and execution logic; the difference is how and where they’re presented to you.

It’s tempting to just treat Lucien as “an AI that writes things.” Actions add:

Auditability – you can see a history of what was proposed, who approved it, and what actually ran.
Permissions – you can decide which people are allowed to approve which kinds of Actions.
Guardrails – instead of letting free‑form prompts directly mutate your tools, everything is wrapped in a structured, reviewable step.

This becomes more important as Lucien starts touching real revenue (renewals, billing), customers (emails, Slack), and product (tasks, specs).

You don’t need full automation on day one. A simple way to start:

Limit scope – pick one or two flows for Actions, like failed‑payment retries or trial follow‑ups.
Keep approvals tight – you (or one other person) approve every Action at first.
Raise the bar over time – once you trust a flow, you can loosen approvals slightly (for example: auto‑execute small retries, require approval for anything touching high‑value accounts).

Over time, Actions are how Lucien stops being “just another dashboard” and becomes a real operator sitting between your tools and your outcomes.