Sessions, memory and schedules
Every use of a crew member starts a fresh session with its charter, memory and handoff notes, from you, a chat, an approved batch or a schedule.
Where in StudioStudio → a crew member → Sessions
Updated View as markdown
On this page
A crew member never resumes an old chat to remember its job. Each use is a new session, and Studio hands that session what the member knows before your first word.
What a session starts with
| Part | Content |
|---|---|
| Charter | The current charter and its revision. |
| Memory | The member's own memory notes. |
| Handoff notes | The notes of its three latest sessions. |
| Notices | Unread notices from its inbox. |
| Project | The project's guidelines and memory, for a member bound to a project. |
If these parts change during a session, the next turn gets the new version; after a compaction they are sent again.
Inside a session, your own message comes first, then the repository's instructions (such as AGENTS.md), then the project guidelines, then the charter. The member's memory, notes, requests and earlier sessions are information for it, never instructions with your authority.
Memory and handoff notes
The member writes memory notes when it learns something worth keeping, such as "never deploy the API while a database migration is pending". They belong to the member and reach every later session.
At the end of a turn that changed something, the session writes a handoff note of up to 1,200 characters for the next session. When it writes none, Studio keeps the start of its last reply instead. The member's Memory page shows its memory, the project part, the crew it can reach, unread notices and the latest handoff notes.
Start a session
A session starts in one of four ways:
- You: open the member and write, or choose New session.
- A chat: a chat can start a session of a member in its list with a first message. It cannot give the session more access than the chat has.
- An approved batch: approving requests delivers them to the running session, or starts one. See Requests and approval.
- A schedule: an automation that runs as the member, below.
A finished session reads Done, and you can continue it: open it from the session list or Recent sessions and write. With One at a time, a second session waits while one runs; Studio offers the running one instead.
Run a member on a schedule
An automation can run as a crew member, so a job such as a nightly disk cleanup runs with the member's charter, memory and model:
- Create an automation and set Runs as to A crew member. See Automated and Workflows.
- Pick the member. Its project, device, model and checkout come from the member and show read-only.
- Under Access for these runs, keep Same as the member, or pick a lower access level for these runs.
Each run starts a session of the member and opens in Crew. You approved the automation, so its runs start without a batch. A run that finds the member already in a session with One at a time is skipped and reads Skipped on the Automated page, with a way to open the running session. The member's space lists its automations on an Automations card.