Quickstart
Sleev is a context-management gateway for AI coding agents, bundled with a
small command-line tool, sleev, that
installs and manages it. Both run entirely on your own machine, so your
conversation history stays on your computer and is never sent to us. Sleev
sits transparently between your coding tool and your model provider, so it
never changes how you use your coding tools.
Coding tools resend their entire conversation on every turn, which burns tokens quickly as a session grows. Sleev intelligently manages that history by compressing the stale parts into compact summaries while keeping recent context and your provider's prompt cache intact, so you send far fewer tokens upstream and save a significant amount on usage.
Install
Start by installing the sleev
command-line tool, which you use to set up and manage the gateway. On macOS and
Linux, the easiest way is the install script, which downloads
sleev and adds it to your path.
On Windows, or if you prefer npm, you can install
sleev with npm instead, which works on
macOS, Linux, and Windows:
Setup
With sleev installed, run it to launch
the guided setup.
The setup walks you through signing in to your account, installing and
starting the local gateway, and pointing your coding tool at it. Once the
setup is complete, you can close the
sleev command-line tool and the gateway
keeps running in the background, so your coding tool routes through Sleev automatically.
Let's set things up.
Sign in
The first time you run sleev, it
asks you to sign in to your account. This links the gateway on your machine to
your Sleev account so your usage and metrics show up in your dashboard.
Installing on a restricted network or a machine that cannot use normal browser sign-in? Approved accounts can use offline licensing instead.
Install the gateway
The gateway and the sleev command-line
tool ship as one package and always run the same version. The gateway binary is
not part of the CLI download, though: the first time you run
sleev, just after signing in, it
fetches the matching gateway version and installs it, then keeps it running as
a background daemon. Because you just installed the latest
sleev, that first gateway is the
latest release too.
Stay up to date
The CLI and the gateway always run matching versions, and you update both
together through the CLI. There are two ways to do it: open the TUI and press
the update notification, or run sleev upgrade.
Each time you open sleev, it checks
for a newer release. If one is available, a notification appears in the corner
with the new version and an Update button that upgrades the CLI and the
gateway in one step.
Or update from the command line at any time:
Pass a version to pin both the CLI and gateway to it: