← Blog

Personal AI Agent: What It Is and How to Run Your Own

Personal AI Agent: What It Is and How to Run Your Own

A personal AI agent is an AI system that acts for one person: it remembers them, takes goals and schedules, uses tools, and reports back where they already talk. POLYROB is an open-source personal AI agent you run on your own machine, with your own model, and this guide shows what it does and how to set one up.

The phrase is used loosely, so the first job is to pin it down. The second job is to show what a working one looks like in practice. Every POLYROB claim below comes from the public repository at release v1.7.6, and the sources are listed at the end.

What is a personal AI agent, and how is it different from a chat assistant?

Aembit’s glossary, checked on 2026-11-10, gives a clear working definition:

“A personal AI agent is an AI system that acts on behalf of one individual, learning their preferences over time and executing multi-step tasks across the services they connect.” — Aembit, Personal AI Agent glossary entry

The useful part is the contrast with a chat assistant. A chat assistant answers when you type and does nothing between sessions. A personal agent keeps going after you close the window.

Chat assistantPersonal AI agent
When it worksOnly while you typeAlso between your messages, on a goal or a schedule
What it keepsA session, sometimes a short historyMemory across sessions, an identity, a goal board
What it doesAnswersPlans steps, uses tools, follows up, reports back
Who holds the dataUsually the vendorDepends on where it runs

That last row matters. A personal agent holds a lot about you, so where it runs is part of the product. POLYROB is self-hosted. There is no hosted POLYROB and no account to create.

What should a personal AI agent be able to do?

Five abilities separate an agent from a chat window. Each one below is a real, shipped feature of POLYROB, with the command you would use.

Does it remember you between sessions?

Cross-session memory is on by default and scoped to you. Out of the box it uses keyword recall over SQLite. An optional local vector index adds semantic recall. If the vector extra is missing, the agent logs one warning and falls back to keyword recall instead of failing. Run /memory in the terminal to inspect what the active provider holds. Memory and state are local SQLite files under ~/.polyrob/data. How recall ranks rows, how memory forgets and which settings to check are covered in AI agent memory.

It also keeps one conversation across devices. Every line you exchange on the terminal, the web console and your phone is recorded in one durable thread. A fresh session reads the tail of that thread on its first turn, so a reply to something said three minutes ago on another device lands with its context. /thread shows it.

Can you give it a personality you control?

Yes, in layers. The SOUL is a pair of plain Markdown files you write: who the agent is, its mission and its boundaries. The agent can never edit it. Below it sits a character, the voice, stored as a JSON file you pick with polyrob identity persona.

polyrob identity soul init
polyrob identity persona init mybot --from writer
polyrob identity persona show

persona show prints exactly what the model receives. Six curated presets ship with the install: analyst, coder, default, ops, researcher and writer.

Does it work on goals while you are away?

It can, once you switch that on. A goal board and scheduled jobs live in SQLite and survive restarts. A goal is one piece of work done once. A job is the same work at set times.

polyrob autonomy on
polyrob goals create "Draft the weekly report" -b "Summarize this week's notes in ./notes into report.md"
polyrob job new "every day 09:00" Summarise the inbox and post the three items that need me

Schedules accept a duration such as 30m, a phrase such as every monday 09:00, or a cron expression. This is off on a fresh install. polyrob autonomy on is the deliberate switch, and polyrob autonomy status shows every setting behind it. For the full picture of the levels and the risks, read the guide to the autonomous AI agent.

Does it live in the apps you already use?

POLYROB talks to you in the terminal, in a web console, and in eight chat surfaces: Telegram, email, WhatsApp, Discord, Slack, Signal, Feishu/Lark and DingTalk. polyrob gateway runs every enabled surface in one process. A new surface starts locked, so the agent answers no stranger until you let them in.

polyrob surfaces add telegram

Can it do real work with tools?

It reads the web with web_fetch (a URL becomes markdown, no browser needed) and drives a browser with Playwright. It works with files, git and GitHub, a persistent shell with background jobs, its own mailbox, and an MCP client. It can hand work to sub-agents that get a narrower toolset and cannot delegate again. Code execution is off by default. Reusable procedures it can load on demand are covered in the guide to agent skills.

How do you keep a personal AI agent under control?

An agent that knows you and can act for you needs limits you set first. POLYROB’s limits are mechanisms, not promises:

Wallet and payment features exist as an opt-in extra and are off by default. The crypto code has had no independent audit. If you ever enable it, start on a testnet with a small cap.

How do you run your own personal AI agent?

You need Linux, macOS or Windows with WSL2, and one model: an API key, or a local model server such as Ollama. The installer fetches Python 3.11 or newer if you do not have it.

curl -fsSL https://polyrob.dev/install.sh | bash
polyrob doctor
polyrob

The installer clones the source, builds a virtualenv, puts polyrob on your PATH and starts the setup wizard, which asks for a provider key, a model, a persona and a chat surface. polyrob doctor is the preflight check. It names the one command that fixes anything missing. Then type a task in the REPL, or run one directly:

polyrob run "summarize https://example.com"

To keep it running after you close the terminal, install the background service:

polyrob service install
polyrob service status

On the model side, OpenAI, Anthropic, Google Gemini, DeepSeek, OpenRouter and NVIDIA NIM are built in. Any OpenAI-compatible or Anthropic-compatible endpoint, including a local one, works through ~/.polyrob/providers.yaml. /model <name> switches the model in the middle of a chat. For the full install walkthrough, with a hosted and a local model route, see how to self-host an AI agent and the install page.

One honest note on data. Memory, goals and sessions stay on your machine. Your prompts reach the model provider you chose, so a hosted model sees them and a local model does not. Since version 1.7.5 the installer sends one anonymous count after a fresh install (version, OS and install method, with no ID). --no-telemetry or DO_NOT_TRACK=1 turns it off.

Want more than one agent? polyrob profile create scout gives a second agent its own config, memory, skills and goals on the same machine, and polyrob -P scout runs it.

Where does POLYROB fall short as a personal AI agent?

Check these before you commit.

If you are weighing it against other self-hosted agents, the OpenClaw alternatives guide and the compare page give dated, sourced rows.

How do you choose a personal AI agent?

Ask the same eight questions of any candidate, including this one.

  1. Where does it run? On your hardware or on a vendor’s server.
  2. What does it keep? Memory across sessions, and in what format.
  3. Who writes its identity? You, or the vendor.
  4. Does it work between messages? On goals and schedules, and does that survive a restart.
  5. Where do you reach it? Which chat apps, and is one conversation shared across them.
  6. What stops it? A step cap, a spend cap and a stop command that works without calling a model.
  7. What waits for you? Do risky actions queue for approval, and can you answer from your phone.
  8. Which models can it use? Can you bring a key, or a local model.

Personal AI agent questions

What is the difference between a personal AI agent and a chatbot?

A chatbot answers a message and stops. A personal AI agent keeps memory across sessions, works on goals and schedules between your messages, uses tools, and reports back. The difference is what happens when you stop typing.

How risky is a personal AI agent?

The risk depends on the limits you set. In POLYROB, autonomy is off until you turn it on, every autonomous run stops at a step cap and a spend cap, high-impact actions wait in an approval queue, and /pause stops background work. These reduce risk. None of them makes an agent risk-free, so start with small caps and low-impact tasks.

Can I run a personal AI agent without paying for an API?

Yes, with a local model. Declare your Ollama, LM Studio or vLLM endpoint in ~/.polyrob/providers.yaml. POLYROB itself is MIT licensed and free. You supply the hardware, and quality depends on the model.

Does a personal AI agent keep my data private?

Its memory, goals and sessions stay in files on your machine. Prompts go to your model provider, and the tools you switch on reach their own services. A local model keeps prompts on your machine.

Can I talk to it from my phone?

Yes. Add a chat surface such as Telegram with polyrob surfaces add telegram, and the same agent and the same memory answer there, in the console and in the terminal.

Where do you start?

Install it, run polyrob doctor, and give it one task before you switch on autonomy. The shortest path is two commands:

curl -fsSL https://polyrob.dev/install.sh | bash
polyrob doctor

Install POLYROB, read the docs, or see the full feature list on the capabilities page. The source is MIT licensed at github.com/theselfruleorg/polyrob.

Sources

All POLYROB facts are from the public repository at release v1.7.6 (github.com/theselfruleorg/polyrob).


POLYROB is an open-source AI agent you run and own. Install it or read the docs.