Bolt.new (StackBlitz)
In-browser WebContainer (Rust-backed shared memory) is the implicit state store. No dedicated memory abstraction — project files are the state. Team plan adds shared workspaces + GitHub integration.
At a glance
- Type
- WebContainer file system
- Tier
- T2
- Section
- Coding-agent memory
- Created
- 2024-09
- Latest release
- no releases
- License
- MIT
- GitHub
- 16.4k★ TypeScript
- Pricing
- Free + paid
- Funding
- $135M total raised: $7.9M seed (Apr 2022); $22M Series A (Nov 2024); $105.5M Series B (Jan 2025) at ~$700M valuation
Taxonomy
- storage
- file
- retrieval
- injection
- persistence
- session
- update
- overwrite
- unit
- document
- governance
- user-controllable
- conflict
- n/a
When to use
Optimised for: in-browser WebContainer dev experience
Anti-fit: not for traditional codebases; WebContainer-only
Pros & cons
Pros
WebContainer-based agent — full-stack apps run in the browser; memory is grounded in actual runnable state.
Cons
Browser-runtime-only; not applicable to native or backend-heavy projects.
Claims & capabilities
Conversation context does not persist; project files do.
Technical surface
- API surface
- not applicable — web IDE
- Backend storage
- custom (browser-based WebContainer)
- Deployment
- Managed-only
- Embedding model
- not applicable — code-gen agent
- Multi-tenancy
- WebContainer-based browser-side execution — code runs client-side; server multi-tenancy details not published
- MCP
- no first-party MCP; WebContainer runtime restricts external server transports
- A2A
- searched not found
- OpenTelemetry
- searched not found
Similar systems
Other coding-agent memory in the catalog, ranked by inbound references.
- Aider T2
Appends conversation turns to .aider.chat.history.md in project root. restore_chat_history defaults to false — no automatic replay into new sessions. Community /session save command for JSON state snapshots. .aider.conf.yml carries static preferences.
- Augment Code T1
Real-time knowledge graph indexed from connected repos + commit history + CI/CD + tickets + docs. Separate Agent Memory layer (Sept 2025) captures session decisions/corrections/goals as discrete items with developer review/approval UI. MCP endpoint exposes the graph.
- Continue.dev Memory MCP T2
Official Memory MCP (Mar 2025) backed by a knowledge graph. Memory is injected via MCP rather than native to the Continue core. Scope depends on MCP server deployment (local or shared).
- Devin (Cognition) T1
Structured Knowledge items stored server-side. Three-tier scope: repo-pinned (always injected), global (recall by relevance), org/enterprise (visible to org members). Auto-generates Repo Knowledge from repo structure each session; reads past session trajectories for self-improvement; writes notes for recurring scheduled tasks.
- Lovable T2
Long-term context stored as files in /docs that the agent reads on each session. Agent Mode (default since July 2025) holds working context within session but doesn't persist cross-session beyond filesystem state.
- Mistral Vibe (Remote Agents) + Mistral Medium 3.5 T1
Vibe is Mistral's cloud-hosted coding-agent platform: each session runs in an isolated sandbox with task state, history, and approvals. Spawnable from CLI or Le Chat, with parallel execution. Local CLI sessions can be "teleported" to the cloud and resumed. Powered by Mistral Medium 3.5 (77.6% SWE-Bench Verified). Plugs into GitHub, Linear/Jira, Sentry, Slack/Teams.