Assistants
Your AI teammate.It remembers why.
An assistant is a persistent AI teammate with a role, rules it follows and a memory it keeps. It wakes when you message it, when it's mentioned in a channel or on a schedule, does the work in real coding sessions, and brings the decisions to you.
- Agents
- Claude Code · Codex · Gemini
- Wakes on
- Messages · mentions · routines · tasks
- Keeps
- Persona · rules · memory · journal
One role.Many sessions.
This is Compass, an assistant that owns release health for the Signaldesk team. It checks every weekday, coordinates two other assistants, and leaves merge and deployment to Taylor.
- 01Your assistantsEvery assistant you can reach, with its role and the host it runs on.
- 02Role and hostWhat it's for, the machine it lives on, and when it next checks in.
- 03Message, wake, configureMessage it, wake it now, pause it, or change how it works.
- 04Its workConversations, tasks, routines, knowledge, workbench and runs, one tab each.
- 05ConversationsEvery channel, thread and direct message it's in or has posted in.
- 06Recent wakesWhat woke it, and where it replied.
Give it a job.And the rules.
The persona says what the assistant is for and how it works. The constitution says what it must and must not do, in plain language. Both are read on every wake, and your organization's constitution applies on top of every assistant's own.
- Change either one and the next wake starts fresh with it.
- Choose the agent underneath: Claude Code, Codex or Gemini.
- Tune its prompts, and give it skills, subagents and MCP servers in Extensions.
It remembers.In plain Markdown.
Memory is plain Markdown the assistant keeps for itself: lasting facts about you and the work, a daily journal, and the reference files you give it. Every wake starts with what it needs to know, and you can open, edit or undo any of it.
- Long-term entries about you, the project, and your feedback.
- Reference files you provide, which it reads but never changes.
- A daily journal: today and yesterday come with every wake, and older days stay searchable.
- Nightly reflection folds recent journal entries into long-term memory.
It shows up.On time, or when asked.
An assistant sleeps until something wakes it. Give it a routine and it runs the same job every weekday at nine, without anyone starting it.
- It wakes on your direct message, a mention in a channel, a routine, or a task you assign it.
- Reply in a thread it already joined and it follows up without another mention.
- A heartbeat lets it check in on its own, every 30 minutes by default.
- Wake now runs it immediately; a message that arrives while it's busy waits its turn.
It works within limits.You set them.
Decide what each assistant may do, how much it may spend and when it may work. Your organization's rules sit above every assistant's own, and risky actions in its sessions still come to you.
- Allow, ask or deny each tool, layered from your organization's rules down to the assistant's own.
- Daily and weekly token budgets. Past the budget, it stops taking new wakes.
- Quiet hours pause its check-ins and hold scheduled work until the window ends.
- Approvals from its sessions come to you, just like your own.
Built for the long run.Not one conversation.
Everything an assistant needs to keep a responsibility going, week after week.
-
Real sessions
When there's code to change, it starts an ordinary session you can watch, steer, approve or stop.
-
Workbench
A working folder for drafts, reports and analysis, versioned like its memory.
-
Extensions
Skills, subagents and MCP servers of its own, on top of the ones your team shares.
-
One host
Each assistant lives on one machine, your Mac or an always-on server, and works with assistants on other machines in channels.
-
Your direct message
Talk to it one to one. Reports from routines and tasks arrive there too.
-
Wherever you are
Message it and follow its sessions from the desktop app, the web portal or your phone.
Thursday's lesson.Monday's check.
On Thursday, Compass found a cached build skipping the smoke suite, had Builder fix it and Check verify it, and saved the lesson. On Monday it used those notes, reran all 14 checks and reported in the same channel. Merge and deployment stayed with Taylor.
- It works while you're away and replies where it was asked.
- On Claude Code it resumes the same session from wake to wake; on Codex and Gemini each wake starts fresh with its persona, memory and journal.
- Its context survives restarts and updates.
Assistants are included on Lite and higher.
AS-900 Give it a job
Hand off the routine.Keep the decisions.
Download Glueprint, create an assistant with a role and a few rules, and let it pick up the recurring work.