Skip to main content

Quickstart

Get a workflow live in under 5 minutes.

Context as Code

How generated helpers make workflows more stable.

Why Terse

Most AI workflows are easy to prototype and hard to keep running. An integration’s schema drifts, a prompt quietly regresses, a step that called an LLM now needs a guardrail, and the agent that wrote the workflow can’t fix it because it can’t see the audit log. Terse handles the long tail of that work in one place: a typed TypeScript SDK with deterministic ACL guardrails on every integration call (the Slack guardrail, for example, only lets the agent post in channels the workspace has explicitly approved), a sandboxed runtime you ship to with terse deploy, an audit log that unifies deterministic and agent steps, and agent skills (terse-create, terse-improve, terse-self-host) you install with npx terse-cli install so the coding agent in your editor can build and maintain workflows with you.

What a workflow looks like

A Terse workflow is a single TypeScript file. Triggers come from your generated SDK, so the GitHub repo and Slack channel referenced below resolve to typed constants your editor can autocomplete. The agent receives skills, the scope contract for integration access, and the runtime refuses any tool call outside what those skills declare. Deterministic SDK calls and agent runs share one audit log. The job below watches a repo for new pull requests, posts a deterministic Slack message announcing the PR, then threads a Block Kit summary under it:
The skills passed to generateText are the only surface the model can reach: it can post in one Slack channel and read this one repo, nothing else. The deterministic toolbox.slack.sendMessage call returns a typed result you can thread on directly, and generateText picks up the GitHub and Slack tools without further wiring.

Supported integrations

GitHub

Slack

Attio

Linear

Notion

Snowflake

Gmail

Google Search Console

PostHog

Datadog

LaunchDarkly

Apollo

WorkOS

HeyReach

Resend

Start building

Quickstart

Install the CLI, generate your typed SDK, and deploy a workflow that runs on the next GitHub PR. Five minutes, end to end.

Jobs

How createJob ties triggers, handlers, and agents together. The primitive every workflow is built on.