Phantom: A Persistent AI Agent Built with Claude's Agent SDK

What Phantom Does
Phantom is a persistent AI agent that runs 24/7 on a dedicated machine rather than terminating when you close a terminal session. The system wraps Claude's Agent SDK (specifically Opus 4.6) with three key components: persistent vector memory, a self-evolution engine, and an MCP (Model Context Protocol) server. You interact with it through Slack, and it runs on its own VM or via Docker Compose with three commands to set up.
Key Features and Architecture
- Technology Stack: Built with Bun and TypeScript
- Core SDK: Uses Claude's Agent SDK (Opus 4.6)
- Memory System: Persistent vector memory for retaining context across sessions
- Self-Evolution Engine: Automatically rewrites its own configuration after each session
- MCP Server: Enables tool registration and reuse
- Communication: Primary interface is Slack
- Deployment: Runs on its own VM or via Docker Compose
- Setup: Three commands to get running
- License: Apache 2.0
- Testing: Includes 770 tests
Production Examples from the Source
When asked to help with data analysis, Phantom autonomously installed ClickHouse on its VM, downloaded 28.7 million rows of Hacker News data, built an analytics dashboard, created a REST API for it, and registered that API as an MCP tool for future use.
When someone asked "can I talk to you on Discord?", Phantom responded that it didn't support Discord but could probably build it. It then walked the user through creating a Discord bot, collected the token through a secure form, spun up a container, and went live on Discord—effectively adding a communication channel it was never originally built with.
The agent also integrated Vigil (a tiny open-source monitoring tool) into its ClickHouse setup and built itself a monitoring dashboard for its own infrastructure, essentially watching itself.
Self-Evolution Mechanism
The self-evolution engine runs a 6-step pipeline after every session to rewrite its own configuration. The creator discovered that using Sonnet to judge changes proposed by Opus prevented drift that occurred when Opus judged its own work, implementing cross-model validation to maintain stability.
The entire project was built using Claude Code as the only engineering teammate.
Who This Is For
Developers interested in building persistent AI agents with Claude's Agent SDK, particularly those looking for examples of autonomous tool integration and self-modifying systems.
📖 Read the full source: r/ClaudeAI
👀 See Also

DebugBase: A Collective Error Knowledge Base for AI Coding Agents via MCP
DebugBase is an MCP-compatible tool that provides a shared knowledge base where AI coding agents can check for known fixes to common errors like Next.js hydration mismatches or TypeScript resolution issues. It includes 11 MCP tools and comes pre-seeded with 58 error/fix pairs from real agent sessions.

Claude Workflow Library: 10 Complete AI Workflows for Non-Technical Users
A free GitHub repository provides 10 complete AI workflows for Claude users without technical backgrounds, including study, research, writing, business, content creation, decision making, learning, job search, productivity, and life planning systems.

Dynamic Status Bar for Claude Code Shows Live Updates
A developer has improved their Claude Code status bar from static text to dynamic display with real-time updates showing what Claude is working on. The configuration is available as a GitHub gist.

Reducing Multi-Modal Agent Latency by Omitting Screenshot History
A developer found that omitting previous screenshots from multi-modal agent requests and replacing base64 image data with "[image omitted]" strings significantly reduces latency while maintaining performance. The experiment was conducted using Claude and documented on GitHub.