create_file
ChatGPTCreate a new file in one of the user's write-enabled folders. If the user has not specified a folder, use list_folders to find folders where allow_writes is true. 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
ChatGPTCreate a new file in one of the user's write-enabled folders. If the user has not specified a folder, use list_folders to find folders where allow_writes is true. 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.
edit_file
ChatGPTMake a targeted text replacement inside an existing file in the user's knowledge base. 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 where allow_writes is true (use list_folders to check). Use this for precise edits; for full rewrites or new files, use create_file.
edit_file
ChatGPTMake a targeted text replacement inside an existing file in the user's knowledge base. 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 where allow_writes is true (use list_folders to check). Use this for precise edits; for full rewrites or new files, use create_file.
list_files
ChatGPTList files indexed in the user's knowledge base, with optional filtering by title, path, or modification date.
list_files
ChatGPTList files indexed in the user's knowledge base, with optional filtering by title, path, or modification date.
list_folders
ChatGPTList all folders in the user's knowledge base, with file counts. Each folder includes an allow_writes field — when true, you may use create_file to create files in that folder.
list_folders
ChatGPTList all folders in the user's knowledge base, with file counts. Each folder includes an allow_writes field — when true, you may use create_file to create files in that folder.
read_file
ChatGPTRead the full contents of a file by its path. Returns text for documents and base64-encoded image content for image files (png, jpg, gif, webp, svg). Use after search to get the complete contents of a result.
read_file
ChatGPTRead the full contents of a file by its path. Returns text for documents and base64-encoded image content for image files (png, jpg, gif, webp, svg). Use after search to get the complete contents of a result.
search
ChatGPTSemantic search over the user's local notes and knowledge base. Returns the passages most relevant to the query, drawn from the user's own files. Relevant when a request concerns the user's notes, documents, projects, or past work, or could be answered from information they may have written down. This searches one of two separate corpora, chosen with the source argument. A search hits exactly one; they are never combined: - "documents" (the default) — the user's own notes and files. - "chats" — the user's past conversations with AI assistants (ChatGPT and Claude) that they have saved into Miyo. Set source: "chats" whenever the user refers to an earlier AI conversation rather than their own notes — for example "what did I ask ChatGPT about taxes", "find the Claude chat where we designed the schema", "in a previous conversation the assistant suggested…", or "look through my old chats for…". Leave it as documents otherwise. If you are unsure which corpus holds the answer, search "documents" first, then "chats" in a second call. Each result's path identifies the source conversation or note, so you can cite it.
search
ChatGPTSemantic search over the user's local notes and knowledge base. Returns the passages most relevant to the query, drawn from the user's own files. Relevant when a request concerns the user's notes, documents, projects, or past work, or could be answered from information they may have written down. This searches one of two separate corpora, chosen with the source argument. A search hits exactly one; they are never combined: - "documents" (the default) — the user's own notes and files. - "chats" — the user's past conversations with AI assistants (ChatGPT and Claude) that they have saved into Miyo. Set source: "chats" whenever the user refers to an earlier AI conversation rather than their own notes — for example "what did I ask ChatGPT about taxes", "find the Claude chat where we designed the schema", "in a previous conversation the assistant suggested…", or "look through my old chats for…". Leave it as documents otherwise. If you are unsure which corpus holds the answer, search "documents" first, then "chats" in a second call. Each result's path identifies the source conversation or note, so you can cite it.
