Catalog Systems Coding-agent memory Replit Agent

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.

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 48 cited facts, 3 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Type
Project-files-as-memory + Temporal orchestration vendor fix
Tier
T1
Section
Coding-agent memory
Created
2018-01 vendor fix
Latest release
not applicable — not OSS fix
License
not applicable — not OSS fix
GitHub
not applicable — no GitHub repo fix
Pricing
Starter free; Core $20/mo ($18 annual); Pro $100/mo ($90 annual); Enterprise custom vendor fix
Funding
latest: $400M Series D at $9B valuation (led by Georgian; 2026-03); total not stated by Replit vendor fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
commercial vendor fix
Deployment locus
cloud vendor fix
Platform vs product
product vendor fix
Accelerator
yc-w18 third-party fix
Protocols
mcp-client, mcp-server vendor fix
Compliance
soc2-type2 vendor fix

Memory 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
yes — Agent connects to listed or custom MCP servers via Integrations (OAuth or custom headers), with one-click install links
A2A
searched not found
OpenTelemetry
searched not found

Compare Replit Agent with…

Alternatives to Replit Agent → live options ranked by shared design, licence, hosting and MCP support

Similar systems

Other coding-agent memory in the catalog, ranked by inbound references.

  • 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.

  • 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. Acquired by Harness (2026-10-08): Harness bought select Augment Code assets, including Cosmos, the Auggie CLI and the Context Engine, and the team joined Harness. augmentcode.com now leads with Cosmos, a software-factory agent platform.

  • Letta Code T3

    Letta's stateful coding-agent harness: agents rewrite their own memory blocks and skills, version context in git via MemFS (syncable to GitHub) and reflect via a periodic /sleeptime 'dreaming' process. from Letta (MemGPT) team. letta-ai/letta-code is now the main Letta source (harness, terminal UI, App Server, channels); the Letta V1 API server was retired to the archive branch of letta-ai/letta.

  • agentmemory (rohitg00) T3

    Self-hosted persistent memory layer that captures coding-agent activity and recalls it in later sessions, positioned on public benchmark results. #7 in TeleAI Awesome-Agent-Memory

  • Beads (Steve Yegge) T3

    Dolt-backed, dependency-aware graph issue tracker that acts as persistent structured memory for coding agents, replacing markdown plans; `bd remember` stores durable facts and `bd prime` re-injects them.

Sources (47 cited facts, 3 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-22
    • Pricing “Free + paid” → “Starter free; Core $20/mo ($18 annual); Pro $100/mo ($90 annual); Enterprise custom” source
    • Funding / ownership “$852M total $9.0B val Series D · 2026-03” → “latest: $400M Series D at $9B valuation (led by Georgian; 2026-03); total not stated by Replit” source
    • MCP support “MCP server configuration via .replit / agent settings as of Replit Agent 3” → “yes — Agent connects to listed or custom MCP servers via Integrations (OAuth or custom headers), with one-click install links” source
    #219

Related systems

Referenced by (1)

  • OpenRouter integrates with — OpenRouter docs have a community guide on using OpenRouter with Replit Agent. (verified 2026-10-29)