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
GodotIQ MCP Server Gives AI Coding Agents Spatial Understanding of Godot Scenes
GodotIQ is an MCP server that provides coding agents with true understanding of 2D/3D scenes, signals, and code dependencies in Godot. In a test, it autonomously built a twin-stick survivors game in one hour from assets and a prompt.
Open-Foundry: A Framework for Multi-Agent Debates with Claude Code
Open-foundry is a Python framework that assembles multiple Claude Code agents into a panel to debate complex questions, producing fully inspectable reasoning trails with transcripts, orchestrator logs, and per-agent working notes.
Crit: Local-first, single-binary CLI for reviewing agent plans and diffs
Crit is a single-binary CLI that opens files or diffs in a browser with a GitHub-inspired UI, allowing multi-round feedback loops with AI coding agents — no account needed.
MCP + Skills Framework: Guiding AI Agents for Efficient Data Science Workflows
A practical approach using MCP server + skills framework to constrain Claude/GPT agents toward platform-aware, efficient data science workflows — avoiding client-heavy code and unnecessary data movement.