Jasper guides
Get Started with Jasper, the AI Coding Terminal
Jasper is a desktop workspace for command-line AI coding agents. Open separate terminals for Claude Code, Codex, Copilot, Aider or Gemini, organize them by project, and keep track of the work each agent is doing.
Each tool still uses its own account, model access and command-line interface. Jasper provides the terminal workspace around those tools.
1. Install Jasper
Open the download section to see the current builds, then sign in to your Jasper account. Desktop downloads use a download code; redeem your code in the account area to get the installer. Build availability is shown there before you download.
The desktop catalogue includes macOS on Apple silicon and Windows. For mobile availability and access, check the current account catalogue. A remote VPS is optional when you work on a local project.
2. Sign in to the AI tools you use
Install and authenticate the coding CLI you want to run on the machine where it will execute. For a local terminal, that is your computer. For an SSH terminal, it is the remote server.
Jasper includes presets for Claude Code, Codex, GitHub Copilot CLI, Aider, Gemini and OpenCode. You can also register another command-line tool. You bring your own AI subscriptions or API keys; a Jasper plan does not include the model providers’ tokens.
If a tool fails to start, first confirm that its command runs in a regular terminal on that same machine. Then check the tool selected in Jasper. The support guide covers startup and connection problems.
3. Open a project terminal
Choose your project folder and the AI tool for the terminal. Write a bounded task with the relevant files, expected behavior and a way to check the result. Open another terminal when a separate task can proceed independently.
For example, one terminal can investigate a failing test while another reviews documentation. When both jobs edit the same files, coordinate the changes or use separate Git worktrees. Separate terminal contexts do not isolate changes to a shared working directory.
Jasper keeps project terminals together and tracks supported tools’ usage. Its terminal sessions are designed to survive app restarts, so returning to the workspace can reconnect you to running work.
Choose where your agents run
| Workspace | Where work runs | Next step |
|---|---|---|
| Desktop project | Your local computer | Get the desktop client |
| Remote SSH project | A VPS you connect to | Learn about remote terminals |
| Shared team board | The board’s server container | Learn about team workspaces |
Common questions
Does Jasper replace Claude Code or Codex?
Jasper runs their command-line tools in a shared workspace. You keep using the provider’s own authentication and model access.
Do I need to rent a server?
A local desktop project runs on your computer. Remote SSH and managed VPS workflows are available through Pro; shared project access is part of Team. See the current plans for availability and pricing.
Where do I get help?
Visit Jasper support or email support@agent-jasper.com. Include your platform, the AI tool, and whether the terminal is local or remote.