Follow the evidence. Keep the history of your judgment.
근거를 따라, 판단의 변화를 남기다.
Get started ·
Features ·
Verification ·
Contribute
English · 한국어
Your documents change. A result gets revised. A colleague needs to understand why.
THOTH is a local, AI-assisted research workbench that keeps the question, source evidence, competing explanations and recorded results connected. Inspect what supports a judgment, see what remains unresolved, and compare two saved results before deciding what comes next.
Original THOTH brand illustration — the Egyptian scribe, reimagined for a research workbench.
Note
Experimental source preview for personal/local use. The interface is Korean-first. Focused feature checks passed; the latest repository-wide verification is not passing. See the verification limits below. 2026-09-29 update: isolated model authentication and restart recovery are included. Real-provider analysis and a current-source FULL pass remain unverified; Claude subscription login is disabled without client configuration. See status and limits before relying on a result.
| Follow the evidence | Inspect the judgment | Keep the changes |
|---|---|---|
| Connect documents and return to source-located evidence, versions and time eligibility. | Review an answer alongside competing explanations, missing evidence and next actions. | Compare two exact saved results and inspect immutable history. Supported restores create a new revision. |
Continue a question without losing its earlier result. Queue new input behind running work; request identity is preserved across retries and recovery.
Keep unresolved work visible. A completed operation can still contain a partial answer or a held judgment. Completion is not a claim that the evidence is sufficient.
Choose your own connection. Configure a supported provider login or API key in your local workspace, then select the model and reasoning setting. Saved choices are preserved; unavailable routes are shown explicitly. Reading a saved result or comparison does not start a model call.
| Step | In THOTH |
|---|---|
| 1 · Ask | Start with a research question and connect the relevant documents. |
| 2 · Inspect | Follow the answer back to evidence; review competing explanations and gaps. |
| 3 · Continue | Add information or a follow-up question. Input can wait behind running work. |
| 4 · Compare | Select two saved results to inspect what changed. Revisit history when needed. |
Windows · source checkout · Python 3.12 or 3.13 · uv · Node.js · pnpm
Clone the repository:
git clone https://github.com/hyperdrivebeep/thoth.git
cd thothOr choose Code → Download ZIP on GitHub, extract it, and open PowerShell in the extracted
thoth-main folder. If PowerShell is in the folder containing that extraction, run cd thoth-main.
First prepare the Windows Python environment,
then install the locked dependencies from the repository folder:
uv sync --python .\.venv\Scripts\python.exe --no-managed-python --no-python-downloads --frozen --extra dev --dev
pnpm.cmd install --frozen-lockfileStart the API in one terminal:
.\.venv\Scripts\python.exe -m thoth.cli workspace
.\.venv\Scripts\python.exe -m thoth.cli serve --port 8765Start the Web interface in a second terminal, after entering the same thoth or thoth-main folder:
pnpm.cmd --dir apps/web run devOpen http://127.0.0.1:5173/. In setup/settings, select a supported login route or enter your own provider key, then choose a model before starting research. Provider use may consume its quota.
New Windows installations keep research data in %LOCALAPPDATA%\THOTH, independently of the
downloaded source folder. If you used an earlier version, open its existing data directory with
serve --workspace "C:\path\to\your\old\.thoth-local" --port 8765.
THOTH reports the selected directory at startup and does not move old data automatically.
Codex sign-in uses a separate THOTH profile and requires a compatible official standalone CLI. Use THOTH's connection flow; an existing Desktop login is not imported. This source version adds experimental xAI device-code sign-in with a THOTH-owned profile. Its controlled Chrome/RPC flow passed with fake providers; real-account acceptance is pending. Claude and xAI API keys remain separate routes. See connection requirements and restart behavior.
The API binds to loopback; Vite proxies API calls to port 8765. Keep the migration tree with the source checkout: a standalone wheel is not supported by this preview.
Installation details and optional integrations
The isolated Windows check used Python 3.13.15, Node 24.19.0, pnpm 12.6.0 and uv 0.12.5. The basic PDF path uses pypdf. Structured PDF parsing, browser acquisition, additional connectors and managed sandboxes have optional dependencies and prerequisites.
The default connection does not import OMO or Codex Desktop credentials. The experimental Codex bridge uses its own profile for login, token refresh and model discovery. No account configuration is distributed here; successful login alone does not establish a successful model response.
This is an experimental reference implementation, with evidence scoped to the checks below.
| Checked locally | Boundary |
|---|---|
| Input queue, strict input-version checking and exact-result comparison | Four selected integration tests passed; unchanged comparison UI retains recorded Chrome acceptance. |
| Fresh frozen installation, doctor and Web build | Passed on the recorded Windows environment. |
| Synthetic evidence interface | 36 focused Web tests passed. |
| First-run Chrome/API smoke | Passed with no credentials or model calls. An unconfigured model was expected. |
| 2026-09-28 authentication/restart r2 | Partial independent Chrome/RPC acceptance with synthetic providers; five saved results reopened in another process without model calls. Diagnostic failure and unrun scenarios are documented. |
| Connection/restart Web acceptance after signed Python recovery | 247 Web tests and 8 doctor checks passed; actual Chrome/RPC with fake providers covered setup, saved results, drafts and workspace separation. Real OAuth and physical PC reboot remain unverified. |
The latest repository-wide verification is not passing. These results are separate from the focused feature checks. No complete current-source regression pass is claimed. Some legacy assets are also omitted because their redistribution rights were not established.
Real-provider answer quality, hosted multi-runtime readiness, broad platform portability and actual collaborator time savings have not been established by these checks.
Verification record · Exact known failures · Package boundary
| Area | Location |
|---|---|
| Python backend | src/thoth — domain → ports → application → adapters; composition under apps. |
| React / TypeScript interface | apps/web |
| Canonical records and versioned history | SQLite, with versioned migrations in migrations. |
| Brand assets and writing style | docs/brand |
UI summaries do not replace canonical records or authorization. Use synthetic data and an isolated workspace for reproductions. Contributions should preserve source-time, scope, currentness and authorization checks. Read the contributor notes before opening a change.
Original code, documentation, THOTH brand assets and THOTH-authored synthetic fixtures in this snapshot are available under the MIT License, copyright 2026 THOTH. Dependencies retain their own licenses; see third-party and asset notices.
Evidence. Judgment. Revision.
Built by Hyperdrive