Back to directory

Deep Researcher Agent

An autonomous agent that runs deep-learning experiments around the clock on a local machine, a remote server over SSH, or a Slurm cluster, tracking real job outcomes with constant-size memory and zero-cost monitoring.

Deep Researcher Agent

Deep Researcher Agent autonomously runs a user's deep-learning experiments continuously, using a leader-worker architecture and constant-size memory rather than an ever-growing context, with monitoring that costs nothing while jobs run. It can drive experiments locally, over SSH, or on a Slurm cluster, where training is submitted with sbatch --parsable over a single transient SSH call so no process is left running on the login node, and job liveness is read from sacct and squeue with bounded checks that guarantee the monitor loop eventually terminates.

The agent records a job's true terminal state, such as failed, timed out, or cancelled, rather than always marking a finished job as completed, and reasons over that outcome when deciding what to try next. It can run against a Chinese LLM API instead of a Claude or Codex subscription by setting a one-word provider preset (deepseek, qwen, kimi, or glm) that fills in the matching OpenAI-compatible base URL and key environment variable, with the same path also usable for self-hosted or proxied endpoints.

It is written in Python and Apache-2.0 licensed.

More in Agent frameworks

See all 902
  • Recurse

    recurse.run

    A serverless harness that lets a coding agent design, test, and deploy its own specialist sub-agents as tools, MCP servers, or bots, defined by a schema-validated manifest.

  • ProofForge

    shulgin.is-a.dev

    An AI-agent pipeline that decomposes a mathematics problem, proves each piece, and formalizes the result in Lean 4 and Mathlib until the Lean kernel accepts it, with six of its proofs already merged into Google DeepMind's formal-conjectures repository.

  • local-coder

    github.com

    Builds a local coding-agent team on top of Ollama and OpenCode by detecting the machine's hardware, recommending models for seven specialist roles, and testing whether each assigned model can actually use tools, edit a repository and pass verification.