Skip to main content

​
Finding and recovering content

The command palette matches document names and where they live. It does not look inside documents, and it does not match tags, descriptions, or a document’s type.So if you remember a phrase but not the document it sits in, ⌘K will not find it.Your agents can search the text of every document. Ask yours: “Find the document where we wrote about the enterprise discount.”More detail in Finding documents.
Not from the web app. There is no trash, no undo, and no restore button.Deleted content is kept, not destroyed, so a connected agent can bring it back. Ask it to restore the document or folder, and tell it what the item was called and where it lived.Two things behave differently. A restored document takes the next free name if something else has since taken its place. A restored folder refuses rather than renaming itself — if a live folder now sits where it used to be, move or rename that one first. And a folder whose parent was also deleted has to be recovered by restoring the parent, which brings everything back with it.
Deleted documents cannot be searched for, so your agent needs enough detail to find one — its title and folder. If you are about to delete something you might want back, ask your agent to note its details first.
More detail in Deleting documents and folders.

​
Organizing

The web app has no way to move a folder. There is no drag for folder rows and no menu item for it. Moving a folder is only possible through a connected agent. Ask it to move the folder, and the move updates the paths of everything inside.Documents are different: you can drag a document onto any folder row in the sidebar, or use Move… in its menu.Renaming a folder in the app does work, and it updates the paths of every document and sub-folder inside it.More detail in Folders and organization.
A folder that still contains documents or sub-folders cannot be deleted from the web app. The dialog opens, but the Delete button stays disabled and the text names what is still inside.Two ways forward:
  • Empty the folder first (move its contents elsewhere or delete them), then delete the folder.
  • Ask a connected agent to delete it. An agent can remove a folder together with everything in it, which is the practical route for a large branch. It confirms first: the agent reports how many documents and sub-folders would go, and only removes them once you confirm.
If the folder contains a locked document anywhere inside it, neither route works: the delete is refused, naming the locked documents, until they are unlocked.More detail in Deleting documents and folders.

​
Saving and rendering

The most likely cause is tags. Five tags per document is the enforced limit, and the tag field does not stop you adding a sixth. The save fails instead. Remove tags until you are within the limit and the save goes through.The other cause is your plan’s document limit. If the workspace is over it, documents become read-only until you upgrade or delete some. Reads and deletes keep working at any level, so you can always free up space.See Organizing with tags and Plans and limits.
The document is locked. A locked document is approved content that refuses every change — the title input is disabled, the body does not accept edits, and the properties rail is read-only — until someone unlocks it.Only the document’s owner or a workspace owner can unlock it, from the padlock in the document’s topbar. If the padlock does not respond for you, you are neither; ask one of them.A locked document also cannot be renamed, moved, or deleted, and a folder that contains one cannot be renamed, moved, or deleted either.More detail in Writing and editing documents.
The document could not be shown in its format, so the app fell back to a plain editor. The banner names the format it was meant to open as, with a short note on what went wrong — usually that an edit broke the structure the view depends on.Nothing is lost. The document is intact and still readable, and the view returns on its own once the document is valid again.The quickest fix is to ask your agent: “This tracker isn’t rendering — can you repair it?” It can see what is wrong and put it right.More detail in Document formats.
HTML documents open in a secure sandbox that runs no code and makes no outside requests. That is deliberate — it means a page in your brain can never run something unexpected — but it also means a page built to fetch or generate parts of itself when opened will be missing them.Ask your agent to rebuild it: “This report isn’t displaying properly — rebuild it as a fully self-contained page.” Your agent knows the rules it has to meet, and Tatara re-checks the replacement.More detail in HTML documents.

​
Agents

A rejected write is a normal step in a working agent loop, not a fault. Every rejection states what is wrong and how to fix it, so a capable agent corrects itself and retries without your help. If your agent stops and reports the rejection to you, reading it usually tells you exactly what to ask for.If an agent keeps failing the same write, the usual cause is that it is retrying without reading the response. The agent skills teach it the document formats and the recovery loop up front.One rejection is not for the agent to fix: a write to a locked document. The rejection tells the agent to stop and hand the decision to you, because only the document’s owner or a workspace owner can unlock it, in the web app. An agent that responds by writing a modified copy of the document somewhere else is working around the lock — the rejection explicitly tells it not to.
Check the server address first. It is exactly https://www.tatara.app/api/mcp. No other host or path works.If the client cannot complete the browser sign-in, create an access token under Settings → Access tokens and configure the client to send it as a bearer credential instead. Only a workspace owner can create one.If an agent that used to work suddenly loses access, check two things. An access token is checked on every call, so revoking one under Settings → Access tokens stops the agent on its very next request. Disconnecting a browser-signed-in client under Settings → Agent access works differently: it stops that client renewing its access, so it must sign in again, but the credential it already holds keeps working until it expires, up to an hour later.If the person the agent connected as had their membership deactivated, they lose access to the workspace entirely, and so does anything connected under their account. A workspace owner can reactivate them from Settings → Members.More detail in Connecting an agent.