Match the project to your task before installing it.
Vector Retrieval and RAG · Public
ToM-SWE
Vector retrieval project for checking embedding storage, query semantics, RAG integration, data boundaries, and rollback.
Check whether this project matches your task before installing it.
What it can doVector database setup checks, embedding model boundaries, collection management, query acceptance, and deletion guidanceReview the portable capability path.
Before continuingVerify in a sandboxDo not treat a preview pack as a proven local install.
GitHub snapshot112 stars16 forks · 4 contributors
Doramagic.ai Last verification date: 2026-07-30 Verification method: source evidence, semantic profile, public page gate, and static build acceptance.
Publication status · 2026-07-30
What is ToM-SWE?
- ToM-SWE is a vector database, retrieval, or RAG storage component for AI applications.
- Best fit: Developers connecting knowledge bases, documents, or app data to semantic retrieval or RAG workflows.
- Not for: Not for one-off model API calls or environments that cannot isolate indexed data, credentials, and persistence paths.
- Capability added to an AI workflow: Vector database setup checks, embedding model boundaries, collection management, query acceptance, and deletion guidance
- First safe verification step: Verify create, query, delete, and rollback with a small public text sample before using real data.
- Verification state: source, Quick Start, and sandbox install checks are recorded as passed.
- Top risk: May increase setup, validation, or first-run risk for the user.
- Evidence base: https://github.com/OpenHands/ToM-SWE, https://github.com/OpenHands/ToM-SWE#readme, Human Manual, Pitfall Log
01
Quick decision
Use this section to decide whether the project is worth a deeper read.Vector retrieval project for checking embedding storage, query semantics, RAG integration, data boundaries, and rollback.
112 stars · 16 forks
02
What it can do
Translate the upstream project into concrete capabilities the user can judge before installing.Project Overview and System Architecture
Related topics: Core ToM Components, Memory, and Generation, OpenHands Integration, REST API, Visualization, and Deployment
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
Core ToM Components, Memory, and Generation
Related topics: Project Overview and System Architecture, Stateful SWE Benchmark, Session Washing, and Analytics, OpenHands Integration, REST API, Visualization, and Deployment
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
Stateful SWE Benchmark, Session Washing, and Analytics
Related topics: Project Overview and System Architecture, Core ToM Components, Memory, and Generation
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
OpenHands Integration, REST API, Visualization, and Deployment
Related topics: Project Overview and System Architecture, Core ToM Components, Memory, and Generation
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
Source: Doramagic discovery, validation, and Project Pack records
Sources: https://github.com/OpenHands/ToM-SWE, Human Manual, Project Pack evidence, and downstream validation signals.
03
Community Discussion Evidence
Project-level external discussion stays visible on the detail page, not only inside the manual.Community Discussion Evidence
11 source-linked itemsReview these external discussions before using ToM-SWE with real data or production workflows. They are review inputs, not standalone proof that the project is production-ready.
-
01
Dead link
github / github_issue
-
02
Stateful SWE benchmark data access request
github / github_issue
-
03
Connect with Openhands
github / github_issue
-
04
Create ToM Agent
github / github_issue
-
05
write a restful API for tom agent
github / github_issue
-
06
Add precommit
github / github_issue
-
07
size optimization
github / github_release
-
08
Clean packages
github / github_release
-
09
update typing
github / github_release
-
10
1.0 of tom-swe
github / github_release
-
11
Configuration risk requires verification
GitHub / issue
04
How to start
Only source-backed commands are shown here. Verify them in an isolated environment first.Try the prompt first
Test the workflow without installing the upstream project.
previewRead the Human Manual
Understand inputs, outputs, limits, and failure modes.
manualTake context to your AI host
Use the compiled assets in your preferred AI environment.
contextRun sandbox verification
Confirm install commands and rollback before using a primary environment.
verifypip install tom-sweOfficial start command · https://github.com/OpenHands/ToM-SWE#readme · verified: yes
05
Human Manual
The English page must expose the real manual, not a short placeholder.8+ sections · Human Manual
ToM-SWE Manual
The theory of mind module for the SWE agent
Open the full manual- https://github.com/OpenHands/ToM-SWE Project Manual
- Table of Contents
- Project Overview and System Architecture
- Related Pages
- Purpose and Scope
- Repository Layout
- System Architecture
- Stateful SWE Benchmark and Evaluation
Project Overview and System Architecture
Related topics: Core ToM Components, Memory, and Generation, OpenHands Integration, REST API, Visualization, and Deployment
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
Core ToM Components, Memory, and Generation
Related topics: Project Overview and System Architecture, Stateful SWE Benchmark, Session Washing, and Analytics, OpenHands Integration, REST API, Visualization, and Deployment
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
Stateful SWE Benchmark, Session Washing, and Analytics
Related topics: Project Overview and System Architecture, Core ToM Components, Memory, and Generation
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
OpenHands Integration, REST API, Visualization, and Deployment
Related topics: Project Overview and System Architecture, Core ToM Components, Memory, and Generation
Source: https://github.com/OpenHands/ToM-SWE / Human Manual
Doramagic Pitfall Log
Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.
Source: Doramagic discovery, validation, and Project Pack records
06
AI Context Pack and portable assets
After deciding to continue, take the project context into your own AI host.Complete pack plus user-owned assets
These files are planning and verification assets for Claude Code, Codex, Gemini, Cursor, ChatGPT, and other AI hosts.
07
Preflight checks
Treat this page as a planning asset, not proof that your local environment is ready.- The manual is generated from source-linked project files and Doramagic validation signals.
- Community evidence warnings stay visible instead of being converted into marketing claims.
- This English page is indexable because the locale quality gate passed and explicit English index approval is enabled.
- Use the upstream repository as the final authority for installation commands, license, and version-specific behavior.
08
Pitfall Log and verification risks
Doramagic surfaces high-risk items before users treat a candidate capability as verified.Configuration risk requires verification
May increase setup, validation, or first-run risk for the user.
Capability evidence risk requires verification
May increase setup, validation, or first-run risk for the user.
Runtime risk requires verification
May increase setup, validation, or first-run risk for the user.
Maintenance risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.
Security or permission risk requires verification
May increase setup, validation, or first-run risk for the user.
Maintenance risk requires verification
May increase setup, validation, or first-run risk for the user.
Maintenance risk requires verification
May increase setup, validation, or first-run risk for the user.