Pickle-Bot
Your own AI assistant. Name it. Talk to it. Teach it things. Important fact Pickle is a standard little cat.
Pickle-bot is a yet another lightweight version of Openclaw.
The project started with the mindset of building-you-own-openclaw, but end up staying on my raspberry PI, dealing with all daily manners.
Installation
# From PyPI
pip install pickle-bot
# Or from source
git clone https://github.com/zane-chen/pickle-bot.git
cd pickle-bot
uv sync
Quick Start
uv run pickle-bot init # First run: meet your new companion
uv run pickle-bot chat # Start chatting
uv run pickle-bot server # Run background tasks (crons, Telegram, Discord)
The first run guides you through setup. Pick your LLM, configure your agent, and you're ready.
Features
- Multi-Agent AI - Create specialized agents for different tasks (Pickle for general chat, Cookie for memories, or build your own)
- Web Tools - Search the web, read pages, do research
- Skills - Teach your agent new tricks by writing markdown files
- Cron Jobs - Schedule recurring tasks and reminders
- Memory System - Your agent remembers things across conversations
- Multi-Platform - CLI, Telegram, Discord - same agent, different places
- HTTP API - Let Pickle write a frontend for you
Documentation
- Configuration - Full config reference
- Features - How to use each feature
- Architecture - How it works under the hood
Fun Facts
Why Naming Agents with These Names?
Pickle is my cat, as mentioned at the beginning. She is really talktive, definitely more than you can think about.
Cookie was her Step brother, but he lives somewhere else now. so he manage memories on behalf of Pickle.
She's your Cat, Why Matters to Me?
Create your own agents by dropping a file in agents/{name}/AGENT.md. Give them a name, a personality. Give them skills.
Development
uv run pytest # Run tests
uv run black . # Format code
uv run ruff check . # Lint
Docker
Use init command to populate workspace, and mount that as a volume.
docker compose up -d
License
MIT
Metadata
Release files for pickle-bot 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pickle_bot-1.0.5.tar.gz | 420.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pickle_bot-1.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 518.2 kB
Release files / pickle_bot-1.0.5.tar.gz
| Download URL | pickle_bot-1.0.5.tar.gz |
|---|---|
| Size | 420.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93939f744156056ceb5786a68926c8f0ae8056b8c983b8a365a39fb96244bc05
|
|
BLAKE2b-256 checksum How to use checksums |
edec61f4cf4dc31df34c23db6af881544891d23a35f002019d96a35c65f9306e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency logRelease files / pickle_bot-1.0.5-py3-none-any.whl
| Download URL | pickle_bot-1.0.5-py3-none-any.whl |
|---|---|
| Size | 98.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e601f70e7047a13a6e95c4579fa310b6e16cee54f461ec21353f9c4bcaba02a2
|
|
BLAKE2b-256 checksum How to use checksums |
e222aa8d2d463628380bcba65c752d19be862eeecdafc7443a961ca3d11911cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency log