Folders and sessions
Every conversation belongs to a folder. The sidebar lists your folders, each with its own conversations (in the app, also called sessions). Add folder puts another one on the list. General Chats is for conversations that are not about a folder. Each folder keeps its own records: its conversations, schedules and notes stay with it.Starting a session
/new NAME creates a session with that name in the open folder. /fork [NAME] starts a new session that picks up from this conversation. The original stays as it is.
In this folder, or in a copy
If the folder is a Git repository with at least one commit, + asks Work where?:- In this folder: the session works on your files as they are.
- In a copy: the session works in its own Git worktree, which stays apart until you bring the work back. The worktree has its own branch,
archetype/<session>, made from the newest commit on the repository’s default branch. Only committed work comes along.
node_modules, so a session that builds there installs them first.
When you archive a session that worked in a copy, the app shows what the copy has that the folder doesn’t:
- Merge into <branch> commits what’s left and merges it into the folder’s branch.
- Delete it removes the worktree and its branch. Anything uncommitted is lost.
- Keep for later archives the session and leaves the worktree on disk.
Continuing
Open any conversation in the sidebar and keep writing. Each conversation keeps its own engine and model (Engines). In the terminal,archetype -c reopens the conversation you used last.
The message field
Enter sends your message. Shift+Enter starts a new line.
Attachments
Press Attach files, or paste or drop files into the field. One request can carry:- up to 8 files, 30 MiB in total
- images (PNG, JPEG, GIF or WebP) up to 5 MiB each
- other files up to 25 MiB each