Skillget

Thoth

agent
Guvenlik Denetimi
Gecti
Health Gecti
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 30 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This tool is an orchestration runtime designed to manage and automate research workflows (autoresearch) via an interactive dashboard. It integrates with AI coding assistants like Claude Code and Codex to turn agent-driven tasks into structured, trackable, and reviewable runs.

Security Assessment
Overall Risk: Low. Based on the automated code scan across 12 files, no dangerous patterns were found. The tool does not request inherently dangerous permissions (such as unchecked filesystem access or elevated execution rights). While no hardcoded secrets were detected, developers should note that as an orchestration engine making use of AI plugins, it inherently processes the prompts and data fed into those sessions. Review the repository directly to understand exactly what local or network data it binds to during its operations.

Quality Assessment
The project appears to be actively and recently maintained, with the last code push occurring today. It operates under the standard and highly permissive MIT license, which is excellent for open-source adoption. The community trust is currently modest at 30 GitHub stars, indicating it is a relatively new or niche project rather than a widely established tool. However, the provided documentation and README are thorough and professional.

Verdict
Safe to use, though you should monitor the project as it continues to mature and verify its plugin configurations before integrating it into sensitive environments.
SUMMARY

🐦 Thoth — Dashboard-First Orchestration Runtime for Autoresearch

README.md

English | 简体中文

🐦 Thoth — Dashboard-First Runtime for Autoresearch

Thoth logo

Dashboard-first orchestration runtime for autoresearch.

Turn drifting agent work into durable runs, locked contracts, and reviewable verdicts.

Runtime Dashboard First Mode Autoresearch Engine Orchestration Trust Contract Locked

Claude Code Plugin Codex Plugin Strict Tasks --task-id Version 0.1.4 License MIT

Thoth concept banner

Control Plane At A Glance

                               THOTH CONTROL PLANE

                    Claude Code surfaces      Codex surfaces
                 /thoth:* command set        $thoth command set
                              \                 /
                               \               /
                                +-------------+
                                              |
                                              v

+----------------------------------------------------------------------------+
| Layer 1. Host Surface                                                      |
|                                                                            |
|  init   discuss   run   loop   review   status   dashboard                 |
|  report doctor    sync  extend                                             |
+----------------------------------------------------------------------------+
                                              |
                                              v
+----------------------------------------------------------------------------+
| Layer 2. Planning Authority                                                |
|                                                                            |
|  init      -> bootstrap .thoth authority and host projections              |
|  discuss   -> record decisions and contracts                               |
|  sync      -> regenerate projections and derived surfaces                  |
|                                                                            |
|  Discuss -> Decision -> Contract -> Task Compiler                          |
|                                         |                                  |
|                                         v                                  |
|                               Strict Task (--task-id)                      |
+----------------------------------------------------------------------------+
                                              |
                                              v
+----------------------------------------------------------------------------+
| Layer 3. Execution Runtime                                                 |
|                                                                            |
|  run      -> one durable execution packet                                  |
|  loop     -> one durable recoverable loop packet                           |
|  review   -> structured findings through the same protocol                 |
|                                                                            |
|                           +---------------------------+                    |
|                           | Strict Task (--task-id)   |                    |
|                           +-------------+-------------+                    |
|                                         |                                  |
|                              +----------+----------+                       |
|                              |                     |                       |
|                              v                     v                       |
|                            Run                   Loop                      |
|                              |                     |                       |
|                              +----------+----------+                       |
|                                         |                                  |
|                                         v                                  |
|                 Run Ledger / Events / Artifacts / Result                   |
|                                         |                                  |
|                                         v                                  |
|                  Mechanical Validation / Acceptance                        |
|                                                                            |
|  attach   watch   resume   stop                                            |
+----------------------------------------------------------------------------+
                                              |
                                              v
+----------------------------------------------------------------------------+
| Layer 4. Read Surfaces                                                     |
|                                                                            |
|  dashboard -> human-visible runtime workbench                              |
|  status    -> active / stale / attachable run summaries                    |
|  report    -> derived project truth from current authority                 |
|  doctor    -> health, projection, and runtime-shape audit                  |
|                                                                            |
|                     +-----------+-----------+-----------+-----------+      |
|                     |           |           |           |                  |
|                     v           v           v           v                  |
|                 Dashboard    Status      Report      Doctor                |
+----------------------------------------------------------------------------+

Key invariants:
- .thoth is the shared machine/runtime authority
- .agent-os is the human governance layer
- run and loop are strict --task-id surfaces
- dashboard, status, report, and doctor are read surfaces, not authority writers
- every live packet must end in complete or fail

Why Thoth

Thoth is a dashboard-first orchestration runtime for autoresearch. It assumes chat alone is not an operating system: truth must survive the session, progress must stay visible, and completion must be mechanically testable.

Failure Modes Table

Problem Why it matters
Work is not persistent Long-running work dies with the session, so the agent cannot keep working while you sleep and there is no durable state to resume or audit.
Parallel work is invisible Multiple threads or delegated runs drift apart, and humans cannot see what is actually active.
Agents can claim completion too early A fluent summary can hide that nothing mechanical passed.
Docs and state rot over time Decisions, contracts, and runtime facts drift until nobody knows which layer is authoritative.

Thoth Response Table

Mechanism What it does Counters
Hooks + watchdog + runtime Keep execution attached to durable ledgers and observable lifecycle events. Work is not persistent
Dashboard-first visibility Show live, stale, attachable, and host-specific runtime truth in one read surface. Parallel work is invisible
Mechanical yes/no acceptance Force validators, ledgers, and result payloads to decide whether work really passed. Agents can claim completion too early
Decision system + execution system + locked contracts Freeze what is allowed, compile it into tasks, and keep authority layers from drifting. Docs and state rot over time

System At A Glance

Humans should not spend their attention tracking every grain of sand in the funnel. Thoth lets AI own the middle of the hourglass, while the dashboard shows the gold that survives: decisions, tasks, runs, results, and the current verdict.

Architecture Flow Table

Stage Purpose Input Output
Intent Capture the user request and operating boundary. Human goals, constraints, repo context Direction for planning
Decision Lock key choices before execution drifts. Intent, open questions, policy constraints Recorded decisions
Contract Freeze what is allowed and what counts as done. Decisions, requirements, acceptance rules Locked contracts
Task Compile executable work items from the contract. Contracts, project state, compiler rules Strict task specs
Run Execute one task through a durable runtime packet. Task spec, host surface, executor .thoth/runs/<run_id> ledger
Result Produce a mechanical verdict instead of narration alone. Validator outputs, artifacts, runtime checks Structured result and acceptance evidence
Dashboard Let humans read the final state without replaying the chat. Ledgers, read models, derived summaries Inspectable project truth

Quick Start

  1. Install Thoth on the host surfaces you use.
claude plugin marketplace add SeeleAI/Thoth --scope user
claude plugin install thoth@thoth --scope user
codex plugin marketplace add SeeleAI/Thoth

For Codex, adding the marketplace is the source step. Then install or enable the thoth plugin from the Codex plugin directory.

  1. Initialize the repository you want Thoth to manage.
/thoth:init
$thoth init
  1. Start the first strict run from a compiled task.
/thoth:run --task-id task-1
$thoth run --task-id task-1
  1. Open the read surface.
/thoth:dashboard
$thoth dashboard

Host Install And Upgrade

Host First install Stable upgrade Important note
Claude Code claude plugin marketplace add SeeleAI/Thoth --scope user then claude plugin install thoth@thoth --scope user claude plugin marketplace update thoth then claude plugin update thoth --scope user Restart Claude Code after plugin update so the new version is applied.
Codex codex plugin marketplace add SeeleAI/Thoth, then install or enable thoth from the Codex plugin directory codex plugin marketplace upgrade thoth add takes a source such as SeeleAI/Thoth; upgrade takes the configured marketplace name, which is thoth in this repo.

Command Matrix

Command Host Surface Purpose Input Result
init Claude: /thoth:init
Codex: $thoth init		 Audit the repo and materialize canonical Thoth authority. Optional project metadata or config payload .thoth authority, generated projections, dashboard scaffolding, scripts, and tests
discuss Claude: /thoth:discuss
Codex: $thoth discuss		 Record planning decisions without entering code execution. Topic, decision payload, or contract payload Updated decision or contract authority plus recompiled task state
run Claude: /thoth:run
Codex: $thoth run		 Execute one strict task through a durable runtime packet. --task-id, optional host or executor controls, optional attach/watch/stop Durable run ledger with state, events, artifacts, and terminal result
loop Claude: /thoth:loop
Codex: $thoth loop		 Iterate on one strict task with durable resume and stop semantics. --task-id, optional resume or sleep controls Recoverable loop ledger and bounded iteration history
review Claude: /thoth:review
Codex: $thoth review		 Produce structured findings without modifying source code. Review target, optional --task-id, optional executor controls Structured review result recorded through the shared protocol
status Claude: /thoth:status
Codex: $thoth status		 Show project health and active durable runs. Optional --json Shared status snapshot derived from authority and local registry
dashboard Claude: /thoth:dashboard
Codex: $thoth dashboard		 Start or manage the local dashboard runtime. Optional action: start, stop, or rebuild Local dashboard process and read endpoints backed by .thoth ledgers
report Claude: /thoth:report
Codex: $thoth report		 Build a structured report from current project truth. Optional output format such as md or json Derived progress report from ledgers and project docs
doctor Claude: /thoth:doctor
Codex: $thoth doctor		 Audit health, generated surfaces, and runtime shape. Optional --quick or host checks Health report with validation findings
sync Claude: /thoth:sync
Codex: $thoth sync		 Regenerate projections and align generated surfaces. No required positional input Refreshed host projections and synchronized derived files
extend Claude: /thoth:extend
Codex: $thoth extend		 Evolve Thoth itself under its own test gates. Change request or touched paths Verified repository changes that preserve public-surface parity

Why Trust It

Signal What you can inspect
Durable runtime truth .thoth/runs/* keeps run, state, events, artifacts, and result payloads.
Locked planning authority .thoth/project/decisions/, contracts/, and compiler-generated tasks/ define what execution is allowed to do.
Script-backed verification Validators, doctor checks, and selftests decide pass or fail mechanically.
Shared read model status, report, and dashboard all read from the same authority instead of chat memory.

Who It Is For

Good fit Why
Research and experimentation repos They need durable memory, replayable results, and visible long-running work.
Engineering teams using AI for real changes They need code execution, review, and acceptance to stay auditable.
Teams that want Claude Code and Codex parity They need one host-neutral command model rather than two drifting workflows.

Current Limitations

Current boundary Implication
run and loop are strict --task-id surfaces Free-form execution is intentionally rejected.
Host parity is semantic, not identical UX Claude and Codex still need their own install and local runtime wiring.
Dashboard is a local service, not a hosted control plane Operators need a machine that can run the backend and frontend assets.
The hero logo currently ships as a raster PNG A clean SVG and icon-family refinement is still useful for smaller surfaces and plugin packaging.

Contributors

Built in public by contributors who want AI work to remain inspectable.

Contributors

Contribution path: open a pull request or start a discussion.

License

MIT. See LICENSE.

Yorumlar (0)

Sonuc bulunamadi