All docs

Agent files

Find instruction, skill, rule and memory Markdown files without exposing an entire agent configuration folder.

Ophio isn’t released yet. These docs describe the development version; app downloads are not available.

Open Library → Files. The Agent files group organizes discovered Markdown into Instructions, Agents, Skills, Commands, Rules and styles, and Memory. Choose a category, then a file. Longer lists offer search and identify the tool or project each file belongs to.

This collection is for reading and editing. Library → Agents and Skills are the separate task-launching lists.

What is discovered

Ophio looks in known locations rather than indexing the whole computer:

  • Ophio’s saved agents.
  • Claude Code’s user and project agents, skills, commands, rules, styles, plugins and project memories.
  • Codex instructions, prompts and skills, including .agents skills.
  • Hermes SOUL.md, memories and skills.
  • Registered projects’ Claude, AGENTS, Hermes and Gemini instruction files and supported tool folders.
  • Nested instructions, up to six levels deep while skipping generated directories, and applicable ancestor Claude instructions.

Configured tool-home locations are respected where supported. A discovered linked agent or skill is resolved to its real location and exposed through a restricted root. Discovery of a tool’s files does not make that tool a native Ophio task integration; Hermes and OpenClaw remain terminal-only integrations.

What is not exposed

Discovery allows the relevant Markdown files, not an entire configuration directory. It does not expose settings.json, .credentials.json, auth.json, history.jsonl or conversation transcripts through these automatic roots. Ophio’s own private directories and roots that would expose them are excluded. Nothing is executed to discover the list.

If a file already belongs to an accessible Library root, that root is reused. Otherwise the limited automatic root stays out of Folders on the computer and transfer destinations. You cannot use it to upload arbitrary files into an agent’s configuration folder.

Reading still requires Read Library. Editing requires Edit Library and a writable root. Inspect Markdown for secrets before sharing it; a file type or familiar location does not certify its contents as public.

Refresh and edit safely

The computer rescans when the previous scan is more than 30 seconds old or registered projects change. Read the displayed age, errors and truncation notice. A missing or unreadable file is not proof it does not exist.

Open a file in the normal Library viewer, then use the reviewed save workflow. Changes can affect later runs; a save does not prove an already running agent reloaded the file.

For one task’s evidence, open Talk’s task-title menu → Instructions. That report distinguishes discovered files from sources the agent reported loading. Neither discovery nor a visible file alone proves it was read.