Chats and attachments#
A chat is one conversation with VOOL. Each chat can be bound to a project folder (see Workspaces), keeps its own history on your machine, and can carry files as attachments.
What is this for?#
Everything you ask VOOL happens in a chat. Attachments are how you bring a specific file into a conversation without widening VOOL's access to your whole disk.
How do I use it?#
- Start a chat from the Home screen or the sidebar. Chats are listed and searchable.
- Bind a project folder when a chat should work inside a project — the tools in that chat read and write inside the bound folder (see Workspaces).
- Attach a file with the attachment button before sending a message. The file is staged, shown as a chip, and sent with the message it is attached to.
- Drafts are preserved. When a send fails or you fix a problem, what you typed is still in the composer. Recovery never discards your draft.
What permission or connection does it require?#
Chats are local and need nothing. Attachments are staged inside the app's own storage and are subject to up-front limits (size, count, and total bytes per turn), which the composer shows before you hit them.
What can go wrong?#
An attachment can be refused — never silently dropped. A refused chip keeps its reason and blocks the send, so a message cannot go out missing a file you believe you attached. The typed reasons:
| Reason | Meaning | What to do next |
|---|---|---|
too_large / too_many / turn_bytes_exceeded | Over a size or count limit | Split the message or remove items |
unsupported_type / not_text / image_unparseable | The kind of file a chat turn cannot carry | Convert it, or work with it from a bound folder |
content_mismatch / declared_type_mismatch | The staged file changed or is not what it claims | Re-attach the file |
symlink_refused / executable_masquerade | The staging rules refused a substitute or disguised file | Attach the real file directly |
empty_file / invalid_id / missing_session / name_rejected | The file or chat identity is not usable | Re-attach or reopen the chat |
A chat whose project folder is missing or unreadable is told to you with a reason (unbound, project_missing, unreadable), and pending requests wait rather than being cancelled — see Workspaces.
What do I do next?#
Fix what the chip or reason names, then send again. For everything else, the typed failure reasons above are stable codes you can look up in the Error Book.