Sessions and projects

A session is one conversation with the agent, working in one folder. A project is a folder you work in; its sessions are listed under its name in the sidebar. AgenC Core keeps every session, so you can close the app and come back to the same conversation later.

The sidebar

From top to bottom, the sidebar holds:

• Search sessions and Activity, at the top;
• New session, Routines and Plugins;
• your sessions, in four groups: Pinned, your projects, Recents and Archived;
• your name and picture, with the account menu, the Connect from phone button and, when there is one, the update indicator.

Hide the sidebar collapses it, and Show the sidebar brings it back.

Start a session

Click New session, or press Ctrl/Cmd+N. The welcome screen opens with an empty composer. Pick the folder with the workspace chip above the composer, then send your first message: that creates the session. See Writing messages.

To start a session directly in a project, click the + that appears on the project's row ("New session in" and the project's name).

Settings > General > Sessions sets what a new session starts with:

• New sessions: "With or without a project folder." Choose Project folder or No project.
• Default project folder: "Working directory for new project sessions." Type a path or click Browse….
• Permission mode: the default for new sessions. It does not change existing sessions.

The default provider and model are in Settings > Providers; see Providers and models.

Projects, recents and groups

• A folder becomes a project when you pick it for a session. Each project row lists its sessions, five at first, then "show N more". Click the project's name to fold or unfold it; the app remembers what you folded. Opening a project also makes it the folder for your next new session.
• Recents holds chats without a project, and sessions in folders that are not projects, the most recently opened first. It is folded until you open it.
• Move to group… in a session's menu files it under a group name of your choice, which then appears like a project. An empty name removes the group.

Right-click a project for New session, Show in file manager and Copy path.

Sessions started with "Don't work in a project" run in a folder named agenc in your home folder. They appear in Recents.

Session menu

Each session row has a menu button (Session options). The same menu opens from the button next to the project name at the top of a chat.

• Pin session or Unpin session: pinned sessions sit at the top, in Pinned.
• Rename…: a session is named after your first message until you rename it. Saving an empty name shows the folder's name instead.
• Open in file manager: shows the session's folder.
• Move up and Move down: reorder the session within its group.
• Move to group…
• New session: starts a fresh session in the same folder, with your defaults. It does not copy the conversation.
• Archive or Unarchive: moves the session to Archived, at the bottom of the sidebar. Archiving hides the session; it does not stop its agent or delete files.
• Delete: ends the session, including a running turn, and removes it from the sidebar. Its queued messages are dropped. There is no confirmation.

Know what each session is doing

A dot on a session row shows its state:

• "Running": the agent is working.
• "Waiting for your input": it needs an approval or an answer.
• "Finished while you were away": it finished while you were looking at something else.

When a session's branch has a pull request, the row shows a branch mark instead once the session is idle; hover it for the pull request's state. See Git and pull requests.

Activity, the bell at the top of the sidebar, collects this in one list. Sessions that need you, are running, or finished while you were away come first under Priority; the rest are grouped by day. A number on the bell counts the sessions that need attention. With nothing to show it says "No new activity. Sessions waiting for you will appear here."

Search

Search sessions (Ctrl/Cmd+K) opens a search box. Type to filter by title or folder, move with the arrow keys, press Enter to open, Escape to close. It shows the first eight matches. Archived sessions are included after the others and marked "Archived".

Move around

• The back and forward arrows next to the sidebar button, Go back and Go forward, step through the chats you opened.
• The name at the top of a chat opens the project details: the number of tasks in the project and how many are active, its path, Session context, Show in file manager and Copy path.

Sessions survive restarts

Sessions belong to AgenC Core, not to the window. When you quit and open the app again, or when Core restarts, your sessions come back in the sidebar, and opening one continues the same conversation with its model and settings.

If a turn was running when Core stopped, the chat shows one notice for it: "The daemon stopped during this turn." If nothing has been sent in that chat since, the notice offers Continue. Continue asks the agent to review the transcript and the folder, and to finish the unfinished work without repeating what was done. A message that never reached Core says "The daemon stopped before the message was sent." and offers Retry. Queued messages are kept, and a message is never sent twice.

A goal run belongs to Core, not to the window. If Core stops, for example when you quit AgenC, it resumes the run when it starts again, and the app reports on it again. See Goal, Swarm and Plan.

When the agent of a session ends

Sometimes the agent behind a session ends and cannot take new messages. If you send one, the app carries the conversation into a fresh session and says "Continued from" with the old title. If that cannot work, your message comes back to the composer with the reason.

When a tool call needs review

After a crash, Core may not know whether a tool call finished, for example a command that was running when the power went out. The session then pauses anything that would change something, and Continue names the call to review. Check what happened, then record it with /resolve, typed alone in the composer:

/resolve <tool-call-id> confirmed_committed
/resolve <tool-call-id> confirmed_no_effect
/resolve <tool-call-id> remains_unknown

• confirmed_committed: it completed. AgenC treats its effect as done and will not repeat it.
• confirmed_no_effect: it did nothing. AgenC allows a new attempt, so the agent may run it again. If it did change something, that change may happen twice.
• remains_unknown: you do not know. AgenC keeps the outcome marked unknown, abandons that step without retrying it, and lets the session continue.

You can add an evidence reference and its SHA-256 digest after the disposition. Without them, your word is the only evidence recorded, so the app first asks "Record your own answer?" and explains what your answer makes Core do. Click Record my answer to send it.