Stele
Summary
Swap one AI coding agent for another mid-project and watch the new session ask questions the last one already answered — because context lived in the chat window, not in the project.
Stele is a shared memory layer that sits between your agents and your codebase. Every agent reads the same knowledge graph — decisions, tasks, risks, lessons — before it acts, and writes back what it learns. The atomic task-claiming mechanism means two agents cannot pull the same work item simultaneously, which prevents duplicated effort across parallel sessions. The friction is real: the product is invite-only and cloud-hosted with no self-hosted option, so teams with strict data residency requirements hit a wall immediately.
Bottom line: Stele works well for a solo developer or small team cycling through Claude Code, Cursor, and Codex on a single project — but teams that cannot send codebase context to a third-party cloud service have nowhere to go.
Pricing Plans
Subscription- Free Tier
- 1 private project, 250 assistant turns/mo, 2 members on private
Free
Side projects and open-source
- Unlimited public projects
- 1 private project
- 250 assistant turns/mo
- Local plugin
Pro
Solo devs with private work
- Unlimited private projects
- 1,500 assistant turns/mo
- Hosted MCP
- Monthly knowledge review
Team
Per user for collaboration
- Unlimited members and projects
- 5,000 pooled assistant turns/mo
- Biweekly knowledge review
- Roles + audit log
Enterprise
Large repos and custom needs
- Custom limits
- SLA
- SSO and self-hosting add-ons
View full pricing on stele-ai.dev →
Pricing may have changed since last verified. Check the official site for current plans.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Shared knowledge graph across agents, so switching from Cursor to Claude Code mid-project does not reset the session's understanding of prior decisions and open tasks.
- Atomic task claiming prevents two agents from starting the same work simultaneously, which means parallel sessions produce additive progress rather than duplicated or conflicting output.
- Risk and lesson records surface at the moment a relevant change is being made — not after it ships — so an agent flags a known production bug before the code guard that prevents it gets removed.
- Single CLI install with no dashboard configuration required, so the memory layer becomes active without adding a workflow step between prompts.
Cons
Sign in to edit- The product is invite-only during beta. Teams that need to start using a shared memory layer immediately cannot — there is no self-service onboarding path, and the waitlist timeline is not published by the vendor.
- The service is cloud-hosted with no self-hosted option. Teams working under data residency requirements or corporate policies that prohibit sending codebase decisions and task data to a third-party service cannot use Stele at all — and at that point the only path forward is building a local context-passing layer themselves or using a different tool that supports on-premise deployment.
- There is no API surface exposed by the vendor, so teams that want to pipe Stele data into existing project management or observability tooling have no programmatic integration path beyond what the CLI and agent plugins provide.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Web, local plugin (MCP)
- API Available
- No
- Self-Hosted
- No
- Last Updated
- 2026-07-23T06:30:23.510Z
Best For
Who it's for
- Solo developers needing private AI agent memory
- Teams collaborating with multiple coding agents
- Projects requiring versioned knowledge graphs
What it does well
- Maintaining shared context across multiple AI coding agents
- Storing and retrieving project decisions, tasks, and lessons
- Semantic search over coding project knowledge bases
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Stele free?
- Stele has a permanent free tier alongside paid upgrades. You can keep using a baseline version indefinitely without paying.
- Is Stele open source?
- No — Stele is a closed-source tool. Source code is not publicly available.
- What platforms does Stele support?
- Stele is available on: Web, local plugin (MCP).
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Every new agent session starts cold. It has no memory of the race condition you fixed last sprint, the architectural decision you argued about in a doc, or the task another agent is mid-way through. Stele addresses this by maintaining a persistent, shared knowledge graph that any connected agent reads before responding and writes back to as it works. Setup is a CLI install and a single slash command inside your agent; after that, the record updates automatically as agents work.
The differentiating mechanic is atomic task claiming. When two agents — or two sessions of the same agent — are running, they cannot both claim the same task. The record serializes that access, so parallel work stays parallel rather than colliding. The graph also surfaces past decisions and known risks at the moment they become relevant: if an agent is about to remove a code guard, and that guard was added to prevent a production race condition, the risk surfaces in the agent’s response before the change ships — not after.
Stele integrates with Claude Code, Cursor, Codex, Copilot, OpenCode, Grok, Kimi, and similar CLI-based coding agents via the Stele CLI. The integration model means the tool works wherever an agent can read a local context file, and switching between agents mid-project preserves full context. The product is currently in invite-only beta and is cloud-hosted only — the vendor states no self-hosted path exists.