Use the workspace as your cloud computer
Work on shared files and code repositories in the cloud, with every agent using the same files, without setting up servers.
Every workspace has its own files, and each agent works in a cloud computer of its own that reads and writes them. You can use the workspace the way you use your own computer: keep files there, clone repositories, and ask any agent to work on them, without hosting anything.
Problems this solves
| Problem | What Kavela does |
|---|---|
| Running agents in the cloud means setting up servers and environments | Each agent gets a ready computer with a shell, git, the GitHub CLI and a real browser |
| Work gets lost between runs | Files are saved after each run and restored on the next one |
| Each agent or teammate works on a different copy | Every agent and every person in the workspace works on the same files |
The agent's computer
| Part | Detail |
|---|---|
| CPU and memory | 2 vCPUs, 8 GiB |
| Software | A shell, git, the GitHub CLI and a real browser |
| Between runs | Sleeps about 2 minutes after its last activity, with its files saved |
Work with files
Open Files in the sidebar to see the workspace's files. Open one to read it, Download it, Edit a text file, or Reference it in chat so Kav and the agents work from it.
When an agent needs a file from you, it asks with a card in Approvals that you upload the file to.
Work with a code repository
Connect GitHub once (see Connect your tools), then ask:
Clone github.com/acme/web into the workspace, fix the failing checkout test,
and open a pull request.The agents use git and the GitHub CLI with the workspace's GitHub connection, so they can clone, commit, push and open pull requests. Every agent sees the same clone, so one agent can write a fix and another can review it in the same files.
If a private repository answers "not found", the GitHub account connected to the workspace doesn't have access to it.
What is kept between runs
| Kept | Not kept |
|---|---|
| Every file in the workspace | Processes that were running, such as a dev server |
| A repository's git history | node_modules. Reinstall with your package manager |
| Files over 5 MB, fetched when an agent needs them |
Prompts to try
| Goal | Prompt |
|---|---|
| Keep notes the whole team works from | "Keep a running decisions log in docs/decisions.md and add today's three decisions." |
| Clean data in one place | "Merge the CSVs in data/ into one file, remove duplicate rows and save it as data/clean.csv." |
| Turn a repo task into a pull request | "In our web repo, update every dependency with a security fix, run the tests and open one pull request." |
| Review before merging | "Read the open pull request on our web repo and comment on anything that would break checkout." |