Skip to main content
Examples of the CLI commands you’ll use most often.

​
1. List your most recent notes

Pretty output in a TTY:
Add --json to switch to NDJSON for piping:

​
2. Search by keyword and date range

tiro notes search runs a full-text search and includes each note’s primary documents (one-pager, custom) in the result. Pass the keyword as a positional argument or with --keyword. Date filters accept ISO-8601 or relative shorthand:
Folder-scoped:

​
How keyword matching works

tiro notes search runs a full-text search over note titles and paragraphs. Matching is case-insensitive, so "OKR planning" finds notes containing both words. Results are ordered by relevance, with createdAt descending as the tiebreaker. tiro notes search and POST /v1/external/notes/search return each note together with its primary documents (one-pager, custom). tiro notes list --keyword "..." returns metadata only. Without --keyword, tiro notes list orders results by createdAt descending. With --keyword, the pagination cursor is always null.
Unfinished notes are excluded. tiro notes list and tiro notes search exclude notes where title === "Untitled" or sourceType === "onboarding" by default. Pass --include-untitled to include them.

​
3. Save a single meeting note as Markdown

stdout returns one line of metadata — the actual content goes to disk:
The Markdown file contains a YAML frontmatter, the participant list, and a transcript with one elapsed-timestamp header per paragraph followed by speaker-attributed segments:
Pass --no-timestamps (v0.3.0+) to drop the ### mm:ss headers entirely — handy for raw saving and LLM ingest where the timestamps are noise:

​
4. Pipe search results to jq

--json always emits NDJSON for list/search responses — one note per line. Combine with jq -c (compact) for further pipelines, or head / tail to slice. If the response includes a next-page cursor, it’s emitted as a final NDJSON line keyed _cursor:
Pass that back as --cursor to continue:

​
5. Get a transcript with speaker labels

For agents that already understand MCP’s get_note_transcript payload, switch to --format json — the shape is byte-for-byte identical:

​
5. Explore the workspace wiki

The wiki is Tiro’s auto-extracted knowledge graph (entities, concepts, and their links) over your notes. These commands are read-only and require a wiki-enabled workspace (paid, opt-in).
For --workspace, pass the guid of a wiki-enabled workspace from tiro wiki workspaces. A gated workspace prints the backend’s upgrade message and exits non-zero. → Continue to For AI agents for tool-selection guidance and worked agent flows.