Glossary
Terms used across the docs and the app, one line each.
Glossary
Agent. A Claude (or other CLI) instance running inside an Agent Terminal. Each one operates with the context and permissions its connections grant.
Agent Terminal. The node where the agent lives. Every AI conversation in Riggr happens inside one.
Autosave. Automatic .riggr write 500ms after the last change. Configurable in Settings → Workspace.
Bookmark. A named viewport marker (position + zoom). Stored with the workspace, accessible from the Command Palette.
Canvas. The app's main surface. An infinite space where you place and connect nodes.
Chip. The small button in the middle of a connection. Click it to choose the permission (or port integration) for that link.
API key (AI provider). We don't ask for one. Riggr never requests an Anthropic, OpenAI, or Google key. The chosen CLI (Claude Code, Codex, Gemini) handles its own login. The Settings → API Keys tab is only for credentials to external tools (GitHub, Docker, MCPs).
CLI agent. The external binary the Agent Terminal spawns — claude-code (default), codex, gemini, or a custom path. Each one handles its own login with the corresponding AI provider.
Command Palette. The command menu opened with Ctrl+Shift+P. Lists every action in the app, including adding any node type.
Connector. The permission attached to a connection. Defines what the agent can do with the target node. Slugs like code-full-access, db-read-query.
Connection. A line between two nodes. Carries a connector (agent permission) and/or a typed-port integration. Persists in the .riggr.
Delegation. When one agent hands a task to another connected agent. Enabled by agent-delegate, agent-send, agent-read-output, agent-interrupt, agent-full-access.
Device fingerprint. A unique machine hash (UUID + hostname/username/platform) stored encrypted in riggr-device.json. Sent on every license request to prevent token sharing.
Edge. Synonym for connection. Inherited terminology from canvas libraries.
Handle. The connection point on a node's edge. Where you click to start drawing a line.
Lifetime license. Riggr's pricing model. One-time payment, access forever, updates for as long as the product exists.
MCP. Short for Model Context Protocol. The standard for communication between AI agents and external tools. Riggr exposes canvas nodes as MCP tools to the agent and also accepts external MCP servers (GitHub, Filesystem, etc.).
Node. A block on the canvas. Each one is a specialized tool — editor, terminal, database, agent, scheduler.
Node Bridge. Internal mechanism that connects an MCP tool called by the agent to the concrete capability of a node on the canvas.
Permission. Synonym for connector — the level of access a connection grants the agent.
Typed port. An input or output on a node with a defined type and mode (string-stream, json (value), etc.). When two compatible ports are connected, data flows between them without going through the agent.
Profile (browser). A named set of cookies and browser state, shared across Webviews. Useful for keeping a reusable "Gmail logged in" profile.
RIGGR.md. Optional convention enabled in Settings → Agent → RIGGR.md. The agent is instructed to read and update RIGGR.md at the workspace root as persistent project memory.
Safe storage. Electron API that encrypts strings with OS-derived keys (DPAPI on Windows, Keychain on macOS, libsecret on Linux). Riggr uses it for the license token, device fingerprint, and credentials to external tools (GitHub, Docker, MCP tokens). Doesn't include any AI provider key — that lives with the CLI.
Session ID (Claude). UUID identifying a Claude Code conversation. Riggr saves it in the Agent Terminal's .riggr and uses --resume <uuid> to pick the conversation back up on future sessions.
Scheduled task. A Task Node configuration — prompt + schedule (cron or interval) + target. Automatically fires the prompt to the selected Agent Terminal.
MCP tool. A function exposed to an agent via Model Context Protocol. In Riggr, each connection permission generates one or more named tools (riggr_*).
Workspace. The complete set of nodes, connections, viewport, and bookmarks saved in a .riggr file (JSON). Equivalent of a document or project.