Automations

Every operation Kai runs for you shows up here as a task. Examples from a real workspace:

• "Update the study review dashboard". Kai edited a MiniApp for you.
• "Add a benchmark field to the hypothesis intake". Kai changed code in your connected repo.
• "The return series shifts around DST". Kai diagnosed the issue from your chat.

Each task carries:

• Status, Active, Done, Failed, or Cancelled.
• Origin, Chat (you asked Kai for it) or Workflow (a pipeline scheduled it).
• What Kai did (e.g. "edited the review dashboard", "opened a pull request", "sent a reviewer notification").
• Elapsed time, the conversation link, and an expandable activity log.

When a task fails, you'll see the actual error message inline, not a generic "something went wrong." Click Open conversation to jump to the chat that produced it and ask Kai to retry or change approach.

Workflows are the recurring or event-triggered pipelines that produce tasks. Examples:

• New form submission in MiniApp → send a welcome email and book a Calendar slot.
• Email matches support pattern → draft a reply and notify the owner.
• Every Monday at 7am → post a database digest into Messaging.

Build a workflow either visually in the Workflows tab, or just ask Kai: "when a new lead fills the intake form, send me a DM and book them on my calendar." Kai turns the sentence into a workflow, shows you the steps, and runs it.