Skip to main content
1

Install Terse

One command on a fresh machine: installs the CLI globally (when you confirm), syncs the official agent skills (terse-create, terse-improve, terse-self-host) into every coding agent the installer detects, and walks you through terse auth login. Run terse update later to refresh the CLI and skills.If you prefer to install only the CLI, use npm install -g terse-cli instead.
2

Scaffold a project

terse init handles the full setup in one command:
  1. Scaffolds your TypeScript project files (src/index.ts, config, etc.)
  2. Installs dependencies
  3. Opens the browser to authenticate via terse auth login
  4. Checks your connected integrations and prompts you to add more if needed
  5. Runs terse generate to produce a typed SDK from your workspace
After init, your project looks like this:
terse auth login during init stores CLI credentials in your user config, not in the project folder. Copy .env.example to .env when you want TERSE_API_KEY (or other secrets) available to your app or tooling as environment variables.In a coding agent with the Terse skills installed, you can also describe what you want (for example, /terse-create build a workflow that summarizes new PRs and posts to Slack) and let the agent scaffold, write, test, and deploy for you.
3

Write your workflow

Open src/index.ts and define a job. The scaffolded file includes a starter example. Your generated SDK gives you typed helpers for every integration you connected: trigger builders, skill constructors, resource constants, and deterministic tool wrappers.
4

Test locally

Runs your workflow locally against the Terse backend so you can verify it works before deploying.
5

Deploy

Your code is packaged, uploaded, and hosted serverlessly. Navigate to the link provided to monitor your workflow. Learn more about how deployment works.

​
What to do next

Context as Code

Understand what terse generate produces and why it matters.