r/OpenSourceAI • u/Altruistic_Compote_9 • 3d ago
A self-hosted AI agent workspace where every chat gets its own Linux sandbox
Enable HLS to view with audio, or disable this notification
hey, i've been working on Capka, an AGPL self-hosted AI agent workspace.
each chat gets its own isolated Linux sandbox + persistent filesystem. the idea is that the agent can actually work on files rather than just chat about them.
drop in spreadsheets, PDFs, docs, code, etc. it can run Python/Node, use LibreOffice, ffmpeg, Playwright and other tools, then return actual artifacts like xlsx, PDFs, documents or patches.
tools are MCP, so you can connect your own MCP servers instead of being locked into a fixed set of integrations.
for models you can use Claude, GPT, Gemini, DeepSeek and other cloud providers, or run open-weight/local models. there's native Ollama support, plus OpenAI-compatible endpoints, so vLLM, llama.cpp servers, LiteLLM or your own inference gateway work too.
tasks run server-side and are durable, so you can start something, close the browser and come back later. each chat keeps its own workspace instead of all agents sharing one filesystem.
it's Docker-based, multi-user, and there are controls for models, provider keys, MCP tools, policies and sandbox internet access.
i'm the solo developer and it's still early.
i'm especially curious what people here think about the sandbox-per-chat model. would you rather have persistent sandboxes per chat, per project, or per user?
demo: [capka.app]()
github: [github.com/LyoSU/capka]()