Skip to content

Question: should Thoth be listed as an AutoResearch runtime? #13

Description

@Royalvice

Hi, thanks for maintaining this focused AutoResearch list.

I wanted to ask whether Thoth fits your curation model, and if so where you would prefer it to be listed.

  • Project: https://github.com/SeeleAI/Thoth
  • Type: implementation/runtime rather than a single optimization use case
  • Fit: dashboard-first Claude Code and Codex runtime for autoresearch-style work, with durable runs, locked work items, visible ledgers, and reviewable verdicts

I noticed the README asks for submissions to be verifiable, with a minimum progress chart or ideally full per-solution traces. Thoth currently exposes the runtime/control-plane layer for durable autoresearch runs, but I do not want to open a weak PR that violates the use-case/trace standard.

Would you prefer one of these contribution paths?

  • A row under "Implementations & Forks" describing Thoth as a runtime/control plane
  • A future "Use Cases" row only after there is a public Thoth-run optimization trace/progress chart
  • No listing unless there is a concrete optimization trajectory attached

Happy to follow whichever standard keeps the list high-signal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions