Sweep AI
No dedicated persistent memory layer. Operates as a GitHub App — reads issue + codebase fresh on each trigger. Some context implicit in the PR/issue threads it created previously.
At a glance
- Type
- GitHub-thread-as-implicit-memory
- Tier
- T2
- Section
- Coding-agent memory
- Created
- 2023 (GitHub app launched); pivoted to JetBrains plugin 2025
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Free (community); Pro and Team tiers; LLM cost + 5% markup model for agent usage
- Funding
- $500K Seed · 2023-01
Taxonomy
- storage
- file
- retrieval
- extraction-pull
- persistence
- session
- update
- read-only
- unit
- episode
- governance
- inspectable
- conflict
- none
When to use
Optimised for: GitHub-thread-as-memory simplicity
Anti-fit: not for non-GitHub workflows; no dedicated memory layer
Pros & cons
Pros
GitHub-issue-to-PR agent with memory of past PRs and code-review feedback.
Cons
GitHub-PR scope; less useful for interactive coding sessions.
Claims & capabilities
Pivoted to JetBrains plugin (2025); no cross-session memory added.
Technical surface
- API surface
- searched not found
- Backend storage
- searched not found
- Deployment
- Both (GitHub App managed + JetBrains plugin local)
- Embedding model
- searched not found
- Multi-tenancy
- searched not found
- MCP
- searched not found — Sweep is a GitHub-app-shaped tool; MCP not surfaced
- 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.
- 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.