Skip to main content
A session is where you work with Runner. Brief the job, answer questions, check the evidence, make the call, and improve the result. Runner can find, compare, organize, and draft across the sources you give it. You keep the judgment, relationships, creativity, and leadership that need a person.
Writes follow your tool permissions. Ask stages an Action Card for review. Allow acts without asking. Off blocks the tool unless a user-created Runner has its own override.

​
Work together in a session

No special syntax. Say it like you’d say it to a capable colleague, then make the decisions that need you.

​
Give the job the right sources

Gmail

Calendar

Slack

Linear

Notion

Drive

Connect only what the job needs. Gmail and Calendar are enough for a Personal Assistant. Add Slack, Linear, or Notion when a different job needs them. Connect your apps →

​
Save what should carry forward

Want a preference available in future sessions? Ask Runner to remember it:
  • “When you draft emails for me, keep them short. Three sentences max.”
  • “Always check my calendar before suggesting meeting times.”
  • “Emails from Sarah and James are always high priority.”
Then open Memory and make sure it was saved. Future sessions can use saved facts and preferences. The transcript itself doesn’t become Memory. See and edit Personal Memory →

​
Voice and files

Voice input. Click the mic icon to talk instead of type. Dictate a task from your phone on the way to the gate, close it, and check the result when you land. Runner on your phone → Attach files. Drag a PDF, spreadsheet, or image into the conversation. “Review this proposal and give me the three biggest concerns.”

​
Sessions follow you

Every session syncs across your devices. Start on your laptop, continue on your phone. Need context from another session? Ask Runner to read another active session you own and use it here. It can’t send a message into or resume that other session.

​
Give Runner a clear brief

  • Give one clear outcome. “Check the email from Sarah about the Q2 budget” beats “check my email.”
  • Name the sources. Say which inbox, Project, folder, record, or site holds the truth.
  • Set the review point. Say what should stay a draft. Use Ask or Off for hard action boundaries.
  • Correct the work. Tell Runner what was wrong and what good looks like.
Feedback in one session doesn’t rewrite a scheduled Runner. For a lasting job change, update its saved prompt. Put durable personal facts and preferences in Personal Memory.

​
When to use a session, Workflow, or Runner

  • Use a session to work through something once.
  • Save a Workflow when the procedure is useful again and you want to start it with /slug.
  • Create a Runner when one AI employee should own the job on a schedule.
Test the work in a session first. Save the procedure as a Workflow when you want it again. Create a Runner when the result is useful, repeatable, and ready for a schedule.

​
What’s next?

Workflows

Save a useful procedure and invoke it with /slug.

Runners

Put one valuable job on a schedule with rules and tool permissions.