Install

There's one way to install: the getstream CLI. It puts the Stream Dashboard in your terminal — coding agents use it to configure your app, send API requests, and pull data — and installing it, then running init, also sets up the skills.

1. Install the CLI:

curl -fsSL https://getstream.io/cli.sh | bash

The install script supports macOS and Linux.

2. Initialize your project (run in your working directory):

getstream init

getstream init authenticates with Stream, lets you pick an app (or create one), and writes your project credentials, so data queries and app configuration work immediately. As its final step it offers to install the skills: pick your coding agent (Claude Code, or the universal .agents location that Cursor, Codex and other tools read), or skip with None.

To install or add skills later without re-onboarding, use getstream skills. With no arguments it installs the default set (the stream router, plus stream-docs and stream-builder); name one to add it, for example getstream skills stream-swift. Skills are downloaded into a shared cache at ~/.stream/skills and linked into the project's skills directory (.claude/skills/ and/or .agents/skills/), so re-running the command refreshes the cache and every project that links a skill picks up the update. The router installs the web pack (stream-react) and the platform packs on demand the first time a task needs them.

Network operations

A few later operations can touch the network — some prompt first, some run unprompted:

• The getstream CLI install. You run curl -fsSL https://getstream.io/cli.sh | bash yourself to install the CLI. The skills never download or run this installer for you: if the getstream binary is missing, the skill asks you to install it and waits.
• On-demand skill fetches. When a task needs a pack that isn't installed yet (the web stream-react pack, or a platform pack), the router fetches its markdown with getstream skills <name>. Most packs install silently, without a prompt; the Flutter pack asks for one confirmation first.
• Scaffolding a project. Building an app runs npx / npm to create and install the project, which needs network the same way any scaffold does. The build pack announces its network plan up front and treats your request to build as consent; it doesn't prompt per command.
• Optional frontend skills. /stream-builder can offer to pull in three open-source frontend skills for UI polish. It lists them and waits for your approval first.

The Security and trust page covers each of these in full, and the file-by-file audit lives in the repo README.md.

Claude Code auto mode

Claude Code's auto mode runs shell commands through a safety classifier that blocks downloading and running code from the network. That stops the steps in this pack that fetch something at runtime:

• an on-demand skill fetch the router would otherwise run (getstream skills <name>)
• the npx / npm calls a scaffold makes
• the optional frontend skills the builder offers

Pre-install what you can in a normal session before switching to auto mode: install the getstream CLI up front, and pre-install any pack you'll need (for example getstream skills stream-swift) so the router never has to fetch it mid-task. The other two can't be pre-run: a scaffold's npx / npm calls and the optional frontend skills fetch at runtime, so do that work in a normal session and switch to auto mode afterwards.