ciaobot 0.4.4

Ciaobot personal assistant server.

Ciaobot

Ciaobot is an opinionated UI and UX layer for using Claude Code as a personal assistant and second brain. It is a local web app around agentic work: chats, projects, files, schedules, memory, and archived knowledge all live in one interface instead of being scattered across terminal sessions.

A personal project, shared

Ciaobot is my personal idea of how an AI assistant should work day to day. I built it for my own use, run it on my own machines, and the defaults reflect that: project-first navigation, a plain-markdown vault as memory, explicit model routing, and self-improvement loops that propose changes instead of applying them blindly.

I'm sharing it because the patterns may be useful to you, and because I'm happy to receive contributions: ideas, bug reports, disagreements with my defaults, and pull requests are all welcome. See CONTRIBUTING.md.

What it does

• Runs Claude Code-backed chats in a PWA with project and workspace navigation.
• Lets you create, preview, edit, and restore workspace files from the UI.
• Lets you schedule project or workspace routines to run when you choose.
• Archives chats into a markdown vault, then extracts session insights and drafts memory proposals for review.
• Keeps durable project context separate from short-lived chat state.
• Supports voice transcription, push notifications, model/provider settings, and local package updates from the UI.
• Shows a macOS menu bar icon (ciao menubar) with server status and open/restart/logs actions — the Ciaobot face turns scared when the server is down.

What it does not do automatically: it never promotes memory proposals into your long-term memory files without review, never discards or rewrites an existing notes folder during onboarding, and never locks you into one provider; chats and routines can route through any configured backend.

Agent-agnostic, standalone vault. The vault structure, project folders, markdown notes, and configuration files (such as CLAUDE.md and MEMORY.md) created in your workspace are standard, open files. They work with any other AI agent, IDE assistant, or bare terminal tool even if Ciaobot is not running. Ciaobot is the opinionated local web interface on top.

Providers

Use the access you already have:

• Claude Code through your Claude subscription or Anthropic API key.
• Ollama Cloud, a local Ollama daemon, or compatible Ollama model routing.
• OpenRouter through an OPENROUTER_API_KEY.

The model is project-first: a workspace represents a life area (personal, work, a client), each workspace contains projects, and each project carries files, notes, decisions, and context that Ciaobot injects when you work inside it, so the agent does not rediscover what you are talking about every time.

Install

Install from PyPI — the wheel ships with the pre-built PWA (the same wheel is attached to each GitHub release):

Requires Python 3.12 or newer (use whichever python3.X you have, e.g. brew install python@3.13):

python3.13 -m venv ~/.ciaobot-venv
~/.ciaobot-venv/bin/pip install ciaobot
~/.ciaobot-venv/bin/ciao run

Then open http://localhost:8443: with no configured workspace the server starts in bootstrap mode and the setup wizard walks you through choosing the workspace folder (default ~/ciaobot) — one root folder that holds your second brain (memory-vault/) alongside app data (config, .env, runtime state, chat metadata) — plus provider choice, before anything is created. Starting from scratch scaffolds the vault inside that folder; you can also point Ciaobot at an existing notes folder elsewhere and it adapts it into the vault structure. When you finish, it writes the config, scaffolds the vault, and (on macOS) renders the LaunchAgents and Ciaobot.app. Setup makes sure the workspace folder is one git repository (running git init with a .gitignore that keeps .env and runtime state out of commits) so snapshots and sync work from the start; an existing notes folder outside the workspace gets its own repo with a minimal .gitignore for OS/editor litter.

For scripted or headless setups, ciao setup --workspace <dir> pre-creates a workspace with defaults and skips the wizard. It prints the resolved workspace, the localhost login URL to open, and — since the CLI lives in a venv that is not on your PATH — an export PATH=… hint if you want to type ciao instead of the full ~/.ciaobot-venv/bin/ciao path.

If the app or menu bar ever opens an ?setup=… URL that returns invalid setup token (the token is one-time-use and deleted on first login), mint a fresh one and print the URL to open:

~/.ciaobot-venv/bin/ciao setup-url --workspace <dir>

Pass --no-rotate to print the existing token's URL instead of minting a new one. The Workspace: line it prints is the workspace whose token the running server validates against — if it does not match the folder holding your data, the server is serving a different workspace.

Quickstart (from source)

A git checkout does not include the built PWA bundle, so build it once before running:

python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install -e '.[test]'
(cd web && npm ci && npm run build)
ciao setup --workspace ~/ciao-workspace
ciao run

ciao setup is idempotent: it writes the initial .env, seeds the workspace docs and vault, and (on macOS) renders LaunchAgents for the server and the menu bar companion plus a Ciaobot.app shortcut that opens the local PWA. The menu bar companion is included automatically on macOS installs (no extra needed). Full setup details and optional Node tooling: docs/DEVELOPMENT.md.

Optional capabilities (Google Workspace, Apple Intelligence titles, MCP connectors) each have their own setup in INTEGRATIONS.md.

Documentation

Doc	What's in it
docs/ARCHITECTURE.md	System design: repo and workspace layout, chat pipeline, memory and insights, schedules, providers, frontend, device branches.
docs/DEVELOPMENT.md	Setup, dev workflow, testing, change guidelines.
INTEGRATIONS.md	Operator config: env vars, OAuth, MCP connectors, server runtime knobs.
PWA_API.md	API endpoints, auth flow, state paths, agent recipes.
web/README.md	PWA frontend workflow, iOS Safari gotchas, design tokens.
SECURITY.md	Security policy.
CONTRIBUTING.md	How to contribute.

Naming note: the user-facing product is Ciaobot. The CLI is installed as both ciaobot and ciao (same command); the Python package, import path, and many environment variables are still named ciao/CIAO_* for compatibility.

For coding agents

CLAUDE.md (loaded every prompt) is the contributor guide; docs/ARCHITECTURE.md is the canonical orientation doc, read on demand. After changes that affect layout, capabilities, env vars, endpoints, or commands, dispatch the doc-updater agent to keep the docs truthful.