Connect a source
A source is a Markdown file in one of two places:- A local file on your computer.
- A file on a GitHub branch. Rivet reads it with the GitHub CLI, so sign in with
gh auth loginfirst.
path can be absolute or relative to the JSON file:
motion-source.json
motion-source.json
rivet context update <id> --remove-source. The instruction keeps its current text.
Sync modes
Each source has a sync mode:daily(default) — Rivet refreshes the source on its own while Rivet is running. It checks local files about every minute, and GitHub files about once a day.manual— Rivet refreshes the source only when you ask.off— Rivet never refreshes the source. Even an explicit refresh of that source fails withsource_sync_off.
daily, Rivet refreshes a collection about 24 hours after its last import or refresh.
Refresh now
Refresh saved instructions withrivet context refresh, and imported reference collections with rivet profile refresh. Both take one of:
<sourceId>— refresh one source. For a saved instruction, this is its ID fromrivet context list.--all— refresh every connected source. Sources set tooffare reported asskipped_offand left alone.--preview— show each source’s sync mode, last sync, and errors, without contacting any source.
rivet_refresh_sources instead. See the reference.
A refresh only queues the work and returns. If a saved instruction’s source can’t be read, Rivet keeps the last good text. A reference refresh reads only the collections you approved and never adds new ones. It can add new items from those collections and start analysis on them, which uses your agent’s usage.
Next
Design context
See the other ways to show Rivet what you mean.

