Your AI engineer, built to work on your code.
Connect a GitHub repository, hand Klinpi a task, and the agent reads the code, edits files and runs the work in an isolated cloud sandbox — streaming every step back to you.
GitHub sign-inSandboxed executionLive agent events
Fix #234 — expired session tokens are not refreshed
Task
Fix #234 — expired session tokens are not refreshed
Waiting for the agent…
sandbox · /workspace
auth.middleware.ts
+64−4Animated preview of a Klinpi run: the agent clones the repository, lists files, reads jwt.ts, explains the cause of issue 234, edits auth.middleware.ts in the sandbox, runs the auth tests and completes with one changed file.
Workflow
Give it a task. Let it work.
Klinpi takes a repository and a task, inspects the code, edits it inside a sandbox and reports back — with every step visible while it happens.
Connect a repository
Sign in with GitHub and pick the repo to work on.
Describe the task
An issue, a bug report, or a plain sentence.
It explores the code
The agent reads files and traces the relevant path.
list_files /workspace
read_file lib/jwt.ts
It works in a sandbox
Files are edited in an isolated cloud environment.
− isExpired(payload)
+ shouldRefresh(payload)
+ continueWithFresh(…)
You review the result
A changed file and the reasoning behind it.
Connect a repository
Sign in with GitHub and pick the repo to work on.
Describe the task
An issue, a bug report, or a plain sentence.
It explores the code
The agent reads files and traces the relevant path.
list_files /workspace
read_file lib/jwt.ts
It works in a sandbox
Files are edited in an isolated cloud environment.
− isExpired(payload)
+ shouldRefresh(payload)
+ continueWithFresh(…)
You review the result
A changed file and the reasoning behind it.
Repository
It starts with your repository.
Sign in with GitHub, pick a repository, and Klinpi clones it into the session sandbox. The agent works against your actual codebase — not a paste of it.
- Sign in with GitHub — no extra credentials to manage
- Your repository list, pulled live from your GitHub account
- The chosen repo is cloned into the sandbox at /workspace
Select a repository
GET /user/repos- 2h ago
arav-menon/klinpi
TypeScriptmain
- yesterday
arav-menon/playground
JavaScriptmain
- 4d ago
arav-menon/infra-scripts
Shellmaster
git clone --branch main github.com/arav-menon/klinpi.git /workspaceExecution path
per sessionRepository
github.com
Klinpi agent
reads · plans · edits
isolated
Cloud sandbox
/workspace
Code changes
1 file
Result
ready to review
Repository
github.com
Klinpi agent
reads · plans · edits
isolated
Cloud sandbox
/workspace
Code changes
1 file
Result
ready to review
- Isolated
- one sandbox per session
- Workspace
- /workspace
- Lifetime
- 30 min, extended while running
- Teardown
- destroyed after the run
Sandbox
A real environment, not a chat window.
Each session gets its own isolated cloud sandbox. The repository is cloned into it, the agent reads and edits files there, and the work stays contained — nothing runs on your machine.
Isolated by default
No shared state between sessions.
Real files
Edits land on the cloned working tree.
Ephemeral
The sandbox expires when the run ends.
Observable
Every command and file change is visible.
Live activity
Every step, as it happens.
A Klinpi run is a stream of events, not a spinner. Status changes, tool calls, tool results and the agent's own reasoning arrive as they occur, so you can follow the work instead of waiting for it.
AGENT_STATUSrun lifecycle updatesTOOL_CALLan action the agent invokesTOOL_RESULTwhat the sandbox returnedAGENT_MESSAGEthe agent's explanationAGENT_ERRORthe run stopped earlyAGENT_COMPLETEDchanges are ready
agent events
streamingConnecting to session…
Features
Built like a developer tool.
No orchestration layer, no dashboard to learn — a repository, a task, an environment, and a stream you can read.
Get started
Give your repository a task.
Klinpi is in active development. Create an account and follow a run from task to changed file.
open source · typescript · self-hostable
