Building a local AI assistant that operates your machine
Browser, files, terminal and Telegram from one assistant: the architecture decisions behind a local AI assistant like Kestro — surfaces, provider layers, confirmations and audit trails.
A local AI assistant that can operate your browser, files, terminal and connected tools.
// category
AI assistant
home/kestro// about
Kestro is a local/desktop AI assistant that works with the tools you already use: the browser, your files, the terminal and connected platforms like Telegram.
It keeps control where it belongs. Actions that modify anything ask for confirmation first, every action is written to an audit log, and you choose which model answers — from multiple AI providers down to fully local models.
// capabilities
// how it works
Kestro runs on your machine as a local assistant. Each capability — browser, files, terminal, Telegram — is a controlled surface the assistant can act on, with your permission.
A provider layer wraps the different model backends behind one interface, so Claude, GPT, Gemini, Grok, LM Studio and Ollama models are interchangeable. You pick the model manually, or let Kestro auto-select the best fit for the task.
The safety loop is structural: read actions run quietly, write and destructive actions pause for confirmation, and the audit log records what was asked and what was done.
// use cases
Ask Kestro to locate files, inspect code or apply well-defined edits — with a confirmation before anything is written.
Have it read pages, summarize content and gather information as you keep an eye on what it opens.
Ask for commands or run scripts interactively while every execution is reviewed and logged.
Send tasks from Telegram and monitor results from anywhere, with the same confirmation and audit rules.
// limitations
// responsible use
// related writing
all articles →