Talo Guide

Organize documentation

Drop a pile of mixed documents in a chat and Talo proposes which project each one belongs to; you review and accept before anything gets copied

When documentation from multiple clients arrives mixed together (or unorganized), you don't need to distribute it file by file by hand. Drag it into a chat (to Home before you choose a project, or into any conversation) and Talo analyzes it, proposes which project each file belongs to (or if a new one is needed), and waits for your confirmation before copying anything.

Drop to organize

1. Drag one or more files, a folder, or a .zip onto the chat. If there are multiple items, Talo gives you two options: "Attach to message" (the usual behavior) or "Organize into projects". With two or more files, a folder, or a .zip, "Organize" is recommended.
2. Choose "Organize into projects". A card in the chat itself shows progress. Talo copies the files to its own workspace (your originals are never touched in any way) and extracts their text.
3. In a few seconds the proposal appears: a group for each existing project that has files, a highlighted group if it looks like a new client, and a "Don't know where" drawer for what doesn't have a clear signal. Each row shows the reason, confidence (high/medium/low), and destination (project and folder) that you can change by hand before accepting.

How Talo decides which project each file belongs to

The calculation is deterministic (doesn't depend on a language model): it compares email domain, person and company names, and project objective terms against what that project's memory already knows. A file is only assigned when the signal is strong enough and isn't shared by two projects at once. When in doubt, Talo prefers to leave it in "Don't know where" rather than risk filing it with the wrong client.

• Destination folder: if the project already has its own folders (documents/, emails/…), Talo reuses them. If not, it creates the standard folder needed within Documentation/ (just that one, not all at once) with the name in the language Talo is set to. Changing the language later doesn't duplicate folders. Talo recognizes the one that already exists in any language before creating a new one.
• New client: it takes at least two files with the same strong signal (the same email domain, for example) that no project knows about for Talo to propose "Looks like a new client: shall I create the project?" A single file from an unknown company doesn't open a project by itself. It goes to "General", a common folder that Talo creates the first time it's needed.
• The assistant can refine the proposal. If you have a conversation open with Talo's assistant (Claude or Codex) while you review the card, it can reread the file content and adjust a row with judgment (for example, a namesake or a term shared by two projects). When it does, the card updates itself and shows "Refined by assistant". The assistant never applies the proposal on its own. Only you can click "Accept and copy".

Confirm a new client

When a group of files looks like they're from a client you don't have open, Talo shows a mini dialog with the list of files that signal it and the folder structure that would be created. You have three options: create the project, pick an existing project (in case the new client is really one you already had under a different name), or not now (the file stays in "Don't know where").

After accepting

When you click "Accept and copy", Talo copies each file to its destination. It never overwrites an existing one; it adds a number if needed. Within the same card you see the summary: how many files to how many projects, and a link to open each destination folder. If any file couldn't be copied (for example, because the original changed right after analysis), the card says so with the reason. It never vanishes without explanation.

Newly copied projects are indexed in memory like any other project document, so you can ask the assistant about their content as soon as it's done.

Undo

While the conversation stays open, the "Undo" button deletes exactly the copies that organization created. It never touches the original, which was never moved. If you edited one of the copies after accepting, Talo detects it and keeps it instead of deleting it, warning you how many stayed for that reason. Projects created (the new client or "General") are never deleted, even if you undo all their copies.

Limits and security

• A file is only copied to the destination you confirmed; the assistant can propose, never copy or undo on its own.
• A .zip is extracted to a secure zone of its own. A path that tries to escape it (../, an absolute path, a symlink) is rejected, as is a nested zip or one that exceeds the size limit.
• A file of unrecognized type is never silently discarded. It goes to "Other" with its reason if Talo couldn't read it.

To learn which skill the assistant uses to refine a proposal, see Skills. For the memory that indexes what gets copied, see Memory.