Replit Agent
https://replit.com/products/agent
No documented built-in persistent semantic memory store. Session duration expanded to 200 min (Agent 3); Agent 4 shifts toward persistent runtimes. Temporal used for orchestration durability, not semantic memory. Cross-session memory relies on filesystem + agent-written notes.
At a glance
- Type
- Project-files-as-memory + Temporal orchestration
- Tier
- T1
- Section
- Coding-agent memory
- Created
- 2018-01
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Free + paid
- Funding
- $852M total $9.0B val Series D · 2026-03
Taxonomy
- storage
- file
- retrieval
- injection
- persistence
- cross-session
- update
- overwrite
- unit
- document
- governance
- inspectable
- conflict
- none
When to use
Optimised for: project-files-as-memory + Replit deploy
Anti-fit: not for desktop/local workflows; Replit-only
Pros & cons
Pros
Built into the Replit IDE so memory + execution + deployment are one product — agent memory is grounded in actual workspace state.
Cons
Tied to Replit's hosted environment; not usable for projects living in a normal local repo.
Claims & capabilities
Product adoption T1; memory-layer maturity T2 (immature).
Technical surface
- API surface
- Web UI primary; REST (Replit Cloud API) and CLI for project ops
- Backend storage
- custom
- Deployment
- Managed-only
- Embedding model
- locked
- Multi-tenancy
- Each customer isolated in dedicated GCP project; Enterprise plans add private deployments and single-tenant hosting options
- MCP
- MCP server configuration via .replit / agent settings as of Replit Agent 3
- A2A
- searched not found
- OpenTelemetry
- searched not found
Compare Replit Agent with…
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.
- Bolt.new (StackBlitz) T2
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.
- 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.