Golem

Build, configure, and ship an AI agent in minutes.

🤖 Multi-agent  •  💬 Telegram-native  •  🧠 Working memory  •  🔧 Skills & MCP  •  ⏰ Schedules & webhooks

Quick start

On a VPS:

npm install -g golem-agent
golem install-daemon

That's it. The daemon is running under systemd (Linux) or launchd (macOS), survives reboots and SSH logouts. To configure your first agent, open an SSH tunnel from your laptop and visit the wizard:

ssh -L 3015:localhost:3015 you@your-vps
# then open http://localhost:3015 in your browser

Local development:

git clone https://github.com/AvivK5498/Golem.git
cd Golem && npm install
cp .env.example .env
npm start                # http://localhost:3015

For full install options, see docs/INSTALL.md. For the CLI reference, docs/CLI.md.

What your agent can do

Each agent runs in its own Telegram bot with a custom persona, working memory, schedules, and a toolset you pick. Out of the box:

• AI-generated personas — describe the job in a sentence, Golem writes the prompt.
• Working memory — agents remember things between conversations (your coffee order on Monday, used on Friday).
• Skills & MCP — drop a SKILL.md or wire an MCP server; the agent learns a new trick.
• Filesystem mounts — mount an Obsidian vault at /mnt/<name>, agents read and write.
• Schedules & webhooks — cron-driven check-ins, GitHub/Strava/CI webhook handlers.
• Voice in, voice out — Whisper transcription, ElevenLabs TTS replies.
• Group chats, handled — LLM classifier decides when to chime in; identity tagging keeps multi-bot rooms sane.
• Sub-agent delegation — parent agents hand specialised jobs to specialist children.
• Code agent — delegate coding tasks to Claude Code with live progress.
• Tool approval — destructive operations ping you on Telegram with Approve/Deny buttons.
• Phoenix observability — OpenTelemetry traces for every turn.

Philosophy

• Agents act, they don't chat. Every agent has tools, schedules, webhooks, and the agency to use them. Conversation is one input among many.
• One bot per job. Specialized agents beat one mega-prompt. Spin up a research agent, a code agent, a personal assistant — each with its own bot.
• Telegram-native, not Telegram-bolted-on. Your agents live where you already are. Voice notes in, voice replies out, group chats, media, buttons.
• You own the stack. Your machine, your SQLite, your API keys, your bot tokens. Portable. Forkable. No cloud account required.
• Configuration is data. No YAML to edit by hand. The web UI writes SQLite; everything is hot-reloadable.

Tech stack

Node.js 20+ · TypeScript · Mastra · OpenRouter · Telegram (grammY) · LibSQL + SQLite · Next.js 16 + shadcn/ui · Phoenix (OpenTelemetry) · Bun test

License

MIT