Skip to content
free-pi

FreePi Bots

Meet the crew.

Friendly agents in the cloud that get stuff done for you. Free.

A crew of friendly, flat, colorful FreePi bots with simple faces, gathered together

How it works

Tell a bot its job in plain words. It works on its own computer and reports back in the chat.

  1. Give a bot a job

    Each bot is a persistent teammate with its own conversation, memory, routines and apps. Describe the job the way you would to a person. It asks for anything else it needs.

  2. Let it work

    The bot does the work on a computer of its own, in the cloud, so your machine stays out of it. Every result comes back to the same chat.

  3. Decide what it does alone

    You choose whether it asks before acting. “Allow once” answers that one card; “Always allow this tool” stops it asking for that tool.

Give each bot a job

Ask for it in chat. The bot sets it up.

A routine is a prompt a bot runs on its own: on a schedule, or when something changes. You do not fill in a form. You ask, and the bot creates it and reports every run back to you.

Examples of what you can ask

“Every weekday at 8am, summarize my inbox.”

“Every Monday, check our competitors’ pricing pages and tell me what changed.”

“Remind me in 20 minutes to call Dana.”

Its own computer

Every bot has a desk of its own.

Each bot gets a real computer with a browser, a terminal, files and a desktop, so it can do work that needs more than a chat. It starts when the bot needs it and goes to sleep when idle.

  • Watch it work. Open the bot’s computer beside the chat and see its screen live.
  • Take control. Sign in to a site yourself, then release control. While you hold the screen, the bot’s screen actions are refused, not queued, so you never fight over the mouse.
  • It asks when it needs you. For a CAPTCHA, a texted code or a payment it asks in the chat and carries on when you choose “I’m done”.
  • Teach it by showing it. Record a task once on its screen and it saves the steps as a skill. Passwords typed with protected input are not recorded.

You set the limits

Approvals decide how much a bot can do without asking.

When a bot needs a yes, it posts a card in the chat that shows exactly what it wants to do. A pending card never blocks the chat: you can keep talking and new work still runs.

Ask

The bot asks before any action that changes something, such as sending an email or editing a document.

Auto

An approval check compares each action with what you asked for. Actions that fit go ahead. It asks when one is off-task, or cannot be undone and you did not ask for it.

Never ask

Every action runs without waiting.

Approval card

Send an email to Dana with the weekly summary?

Allow onceAlways allow this toolDeny

Allow and Block lists of exact tools or sites apply in every mode, and a blocked action is refused without a card. Start with Ask or Auto, and approve the same action a few times to teach the bot what is fine. The card text above is an illustration.

More than chat

Connected apps

Gmail, Slack, GitHub, Notion, Linear and more, plus your own MCP servers and OpenAPI tools. Ask a bot to connect one and approve the sign-in it sends you.

Web search

Bots can look things up on the web while they work.

Remembers

A bot builds knowledge about you and keeps its own memories. A Space is the boundary: memory never crosses Spaces implicitly. Memory is context, not permission, so a remembered line never authorizes an action.

Wakes up on its own

Routines run on a schedule, so a bot can start work without you opening the chat.

Pages

Bots build live dashboards and documents you can open full screen, share by link, and ask about.

Voice replies

Ask a bot to answer out loud.

On the free plan

Free, paid for by ads and your shared FreePi allowance.

Sign in with your FreePi account (Google, GitHub or a verified .edu address). Bots draws on the same daily allowance as the other FreePi products. These are the current free-plan settings and they can change.

  • One bot works at a time. Other runs wait in line, and waiting costs nothing.
  • One active routine, running at most daily. It pauses after two results you have not read.
  • Past the allowance, a run is paid from your bought or earned credits, or waits for the reset when you have none.
  • One model, chosen by FreePi, for every bot.
  • Included: integrations, web search, voice replies, as many bots as you like.
  • Not on the free plan: chat-app messaging, webhooks, subagents and delegation between bots, media generation, phone calls.

Questions

Good to know.

Is it free?
Yes. Ads and your shared FreePi allowance pay for it, and you do not need a card. Past the allowance, a run is paid from your bought or earned credits, or waits for the reset when you have none.
Can I choose the model, or use my own subscription or a local model?
Not on the free plan. FreePi picks one model for every bot, and the model settings are hidden.
Can a bot keep working while I chat?
Yes. A pending question or approval never blocks a chat. You can keep chatting, new work still runs, and the card stays answerable until someone replies. On the free plan one bot runs at a time and others wait their turn.
Can I take over when a bot gets stuck?
Yes. Take control of its screen, do the step, and release it. A bot that needs you for a sign-in, CAPTCHA, passkey or payment asks in the chat and continues when you press Done.
Will a bot act without asking me?
That depends on the approval mode: Never ask, Auto, or Ask. Allow and Block lists apply in every mode, and a blocked action is refused without a card.
Does one bot see another bot’s memory?
Isolated memory is bot-specific. Shared is an explicit choice to pool knowledge with other bots in the same Space.
Where does it come from?
FreePi Bots is a modified version of the open-source Rakazo project, under the Apache License 2.0. It is not affiliated with or endorsed by Rakazo’s authors.