.versuno/ folder as a markdown file with YAML frontmatter. The file is committable and can be edited, then pushed back to Versuno with push_asset.
Unlike get_asset, the content is not loaded into the agent’s context. The agent only sees the file path.
Input
Example
Prompt:“Pull the ‘onboarding context’ from Versuno.”Tool call chain:
- Agent calls
search_assetswith"onboarding context"to get the id. - Agent calls
pull_assetwith{ "id": "abc123" }.
File organisation
The file is placed under.versuno/<folder>/ based on its type:
The filename is a URL-safe slug of the asset’s title.
What happens if the file exists
pull_asset currently overwrites the local file without checking for unsaved changes. If you have local edits that haven’t been pushed, use push_asset first, or commit the file to git so you can recover it.
When to use it
- You want to edit an asset in your normal editor and version-control it in git.
- You want the agent to reference a full asset by path without bloating its context window.
- You’re building up a local
.versuno/folder for offline or CI use.
See also
- push_asset — sync edits back to Versuno.
- Frontmatter reference — the full list of fields written to each file.
- CLI: versuno prompts pull — bulk version of this tool.