Persistent Files and Agent Tools
Capka treats files as both the input and the finished result. A chat keeps its own persistent working directory so the agent can inspect, transform and return artifacts across multiple steps.
File-oriented workflows
- Turn a ZIP of source material into a PDF report and an Excel workbook.
- Clean, join or analyze CSV and spreadsheet data.
- Convert or edit office documents with LibreOffice.
- Inspect a codebase and return a patch.
- Process media with FFmpeg or extract text with OCR.
Persistence and separation
Files remain in the chat workspace between agent steps and browser sessions. Closing the tab does not cancel server-side work. When the task finishes, its output remains available in the same chat.
Each chat has separate storage. A job cannot read another chat’s working files, and one user’s files do not appear in another user’s account.
Tools and package installation
The sandbox provides a real Linux environment rather than a simulated code interpreter. The agent can run Python and Node.js, use browser automation, and install packages needed for a task within the sandbox boundary.