Miyo

Create a new file in a folder connected to Miyo that allows writes (a folder whose allow_writes field is true). The file is always placed inside that connected folder; nothing can be written outside it. The filename may include an existing subfolder path (e.g. "notes/today.md") — but this tool will NOT create new subfolders, so the parent directory must already exist. Returns an error if the file already exists.

create_file

Make a targeted text replacement inside an existing file in a folder connected to Miyo and available to remote AI. The file is addressed by a folder-relative path (e.g. "Notes/todo.md"); paths that resolve outside a connected folder are rejected. old_text must occur EXACTLY ONCE in the file — ambiguous matches are rejected, so include enough surrounding context (whole lines, not just the changed token) to make the match unique. The file must be inside a folder whose allow_writes field is true.

edit_file

List files indexed in the user's knowledge base, with optional filtering by title, path, or modification date.

list_files

List all folders in the user's knowledge base, with file counts. Each folder includes an allow_writes field indicating whether new files can be created in it.

list_folders

Read the full contents of a file inside a folder connected to Miyo and available to remote AI, addressed by a folder-relative path such as "Notes/todo.md" — the form search and list_files return. Returns text for documents and base64-encoded image content for image files (png, jpg, gif, webp, svg). Absolute paths and paths that resolve outside a connected folder are rejected.

read_file

Semantic search over the user's local notes and knowledge base. Returns the passages most relevant to the query, drawn from the user's own content. Widen a search with more phrasings, not a longer one: one phrasing only reaches notes written in that vocabulary. Keep the user's own question in `query` and put up to two complete rephrasings in `variants`: the domain synonym their notes probably use, or the mechanism an answer would have to name. Send them up front when the ask is broad ("everything I have on...", "did I ever write about...") or the wording is short or jargon-heavy; otherwise search again with them once a first attempt comes back thin. Never pad `query` with synonyms; it blurs the match and costs an exactly-titled file its ranking edge. Ranking stays anchored on `query`, so raise `limit` to about 30 when you send variants. This searches one of two separate corpora, chosen with the `source` argument. A search hits exactly one; they are never combined: - "documents" (the default) — notes and files the user wrote themselves. - "chats" — saved copies of the user's own ChatGPT and Claude conversations that Miyo downloaded and indexed from connected browser sources. Each result's path identifies the source file.

search