Manage Sessions

A session is one continuous conversation with Amara, including every message, file edit, and command in it. Syntic Code records sessions so that work is never lost when you close your terminal, and so you can pick up exactly where you left off. Managing sessions well means you can step away from a long task and return without re-explaining the context.

Continuing and resuming

Two flags cover most of what you need.

• syntic --continue reopens your most recent session in the current project and restores its full context, so you can keep going as if you never left. Use it when you closed the terminal mid-task and want to carry straight on.
• syntic --resume lets you choose from a list of earlier sessions rather than assuming the last one. This is the right choice when you have several threads of work in a repository and want to return to a specific one.

Both flags rebuild the conversation history, so Amara remembers the decisions and files from that session.

Session history

Syntic Code keeps a history of your sessions per project. Each entry records when the session ran and a summary of what it covered, which makes it easy to find the thread you want when resuming. History is stored locally under your .syntic/ data, so it stays on your machine and travels with the project checkout on that machine.

Working across sessions

Long tasks often outlive a single sitting. A good pattern is to end a session at a natural checkpoint — after tests pass, or once a plan is agreed — so that resuming later starts from solid ground. Because your SYNTIC.md memory is reloaded on every session, durable facts survive even if you start fresh instead of resuming. Reserve resume for the conversational context; keep anything you never want to lose in your memory file.