Local-first workspaceWindows beta liveOne package install

Run your coding agents in one workspace, not ten terminals.

Kyma Ter is the local browser workspace for parallel Kyma Agent and shell sessions. Install once, launch fast, keep real work visible.

Install once`@kyma-api/agent` gives you both `kyma` and `kyma-ter`.
Work in parallelPlanning, coding, tests, builds, and docs stay on screen at the same time.
Windows path exists`kyma` native. `kyma-ter` beta. WSL2 recommended for shell panes.

Both methods install @kyma-api/agent, which gives you kyma and kyma-ter. Use npm in PowerShell or Windows Terminal.

then run: kyma-terWindows setup
kyma-ter
Kyma Agent
$ kyma init
Kyma Agent
$ kyma "fix the login bug"
Shell
$ npm test
Kyma Agent
$ kyma "write tests"
Kyma Agent
$ kyma "optimize query"
Kyma Agent
$ kyma "refactor utils"
Shell
$ npm run build
Kyma Agent
$ kyma "add validation"
Kyma Agent
$ kyma "update docs"
Windows beta

`kyma` runs natively in PowerShell or Windows Terminal. `kyma-ter` uses the same local web UI and works best with WSL2-backed shell panes.

Read Windows setup
Workflow

The point is not more agents. The point is less context switching.

Good agent UX is not another black-box chat window. It is a workspace where the agent, the shell, and the repo all stay in view while work moves forward.

4 panes · one workspace

Refactor while tests keep running

One pane rewrites auth, one runs `npm test`, one updates docs, and one reviews the diff before commit.

Agent + shell mix

Full-stack sprint without tab chaos

Frontend, backend, and database tasks stay visible at once. You stop alt-tabbing and start coordinating work in one place.

Browser UI · local runtime

Local-first, not a cloud black box

Kyma Ter runs on your machine, opens in the browser, and keeps the workflow close to the repo you are actually shipping.

Why Kyma Ter

A real product story beats a generic terminal grid.

Parallel panes

Run Kyma Agent and shell sessions side by side.

Use Kyma Agent for planning, coding, and edits while shell panes run tests, builds, migrations, and logs in parallel.

One install

Install once. Get both `kyma` and `kyma-ter`.

The same package installs the coding agent and bootstraps the local workspace runtime. No separate app download flow.

Windows beta

Windows is live, with WSL2 as the best path for shell panes.

`kyma` runs natively in PowerShell or Windows Terminal. `kyma-ter` works as a Windows beta workflow and prefers WSL-backed shell panes.

Agent panes

Run `kyma` directly in dedicated panes with the same account and model catalog as the CLI.

Shell panes

Keep test runs, builds, migrations, servers, and logs alive next to your agents.

Keyboard-first flow

Fast pane creation, workspace switching, and command-driven navigation without leaving the keyboard.

Browser workspace

A local web UI instead of another heavy desktop app install. Open it and start working.

Support

One package, different platform paths, one clear story.

Kyma API powers the models. Kyma Agent is the `kyma` CLI. Kyma Ter is the local workspace. That relationship should be obvious on the first screen.

macOS

Native

Install the package, run `kyma-ter`, and work in the local browser UI.

Linux

Native

Same install flow, same local workspace model, same package.

Windows

Beta

`kyma` runs natively. `kyma-ter` works best with WSL2 for shell panes.

13Active models
1Package install
2Commands: `kyma` + `kyma-ter`
Learn more at kymaapi.com →
Install

Install once. Launch when one terminal stops being enough.

Keep the public command simple, then let docs explain the platform details. That is the right split for Kyma Ter.

Both methods install @kyma-api/agent, which gives you kyma and kyma-ter. Use npm in PowerShell or Windows Terminal.

Read Kyma Ter docs →Read Kyma Agent docs →Windows setup →Try Kyma API →