Projects
Attach a folder from the chat header, or by creating a chat from a project. The header shows the folder and its git branch — the first thing you want to know before a model writes SQL or renames a file.
The sidebar groups chats by project: click a project to open or close it; the project holding the open chat opens by itself. Chats without a project sit below under CHATS, grouped by day. The project's ⋯ menu offers New chat in this project, Reveal in Finder and Remove project (which asks whether to keep or delete the chats). Chats can be moved between projects from their ⋯ menu.
What the model can do
The model gets list_files, search_files, read_file, write_file, edit_file, delete_path and run_command, all scoped to the folder:
.gitignoreis honoured, and size limits stop a generated artifact from eating the window,run_commandrefuses destructive commands outright — recursive deletes outside the project, disk and system changes, git history rewriting, piping downloads into a shell — and asks before risky ones,- the write tools ask before touching sensitive files.
The project profile
A project profile goes into the system prompt: the framework, migrations, models folder, the compose file, the .env database, and the test runner — plus the rule to read the migrations before writing SQL.
Memory notes for the project live in <project>/.trailsail/notes. See Notes & memory.
Found a problem, or is something here unclear? Report it.