mcpField
A
autoresearch-hooks

autoresearch-hooks

github.com/davebcn87Agent workflows8.2k36 installsUpdated 3w ago
Repository

About autoresearch-hooks

autoresearch-hooks is a skill for adding optional scripts to the boundaries of an autoresearch iteration. The before and after hooks receive session data as JSON and can send concise guidance to the agent through stdout.

Key features

  1. 01Optional before- and after-iteration scripts
  2. 02JSON input with run and session state
  3. 03Stdout messages steer the agent
  4. 04Timeout and error reporting
  5. 05Hooks preserved across automatic reverts

Use cases

  1. 01Search for information before an experiment run
  2. 02Record learnings after a result is logged
  3. 03Notify or redirect an agent based on run outcomes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davebcn87/pi-autoresearch --skill autoresearch-hooks

After installing, type/autoresearch-hooksin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

examples/
README.md
examples/after/
auto-tag-winners.sh
learnings-journal.sh
macos-notify.sh
examples/before/
anti-thrash.sh
context-rotation.sh
external-search.sh
hypothesis-reflection.sh
idea-rotator.sh
qmd-search.sh

Details

From the project README

autoresearch-hooks

Optional scripts that run at iteration boundaries in an autoresearch session. Two hooks, both transparent to the loop-running agent — their effect is a file on disk or a steer message.

.auto/hooks/
  before.sh    # fires before each iteration (prospective)
  after.sh     # fires after each log_experiment (retrospective)

Both files are optional. Files without the executable bit are silently ignored.


Contract

Stdin — before.sh

One JSON line. Parse with jq. Realistic example:

{
  "event": "before",
  "cwd": "/path/to/workdir",
  "next_run": 6,
  "last_run": {
    "run": 5,
    "status": "discard",
    "metric": 42.1,
    "description": "Simplified to sorted(arr) — copy cost dominates",
    "asi": {
      "hypothesis": "Built-in sort avoids Python overhead",
      "next_focus": "list copy avoidance"
    }
  },
  "session": {
    "metric_name": "total_ms",
    "metric_unit": "ms",
    "direction": "lower",
    "baseline_metric": 40.7,
    "best_metric": 33.5,
    "run_count": 5,
    "goal": "optimize sort speed"
  }
}
FieldNotes
last_runThe most recent run entry. null on a fresh session.
session.direction"lower" or "higher" — which end of the scale wins.
session.baseline_metricFirst run of the current segment. null until one run exists.
session.best_metricOptimal metric across kept runs only. null until one is kept.
session.goalThe session name set by init_experiment.
session.run_countTotal runs logged so far (any status).
Stdin — after.sh
{
  "event": "after",
  "cwd": "/path/to/workdir",
  "run_entry": {
    "run": 6,
    "status": "discard",
    "metric": 38.9,
    "description": "Timsort hybrid slower on random",
    "asi": {
      "hypothesis": "Partial-sort heuristic on input distribution",
      "learned": "Overhead dominates on random arrays"
    }
  },
  "session": {
    "metric_name": "total_ms",
    "metric_unit": "ms",
    "direction": "lower",
    "baseline_metric": 40.7,
    "best_metric": 33.5,
    "run_count": 6,
    "goal": "optimize sort speed"
  }
}
FieldNotes
run_entryThe run just logged. Always present.
sessionSame shape as in before.sh, reflecting state after the run.
Output
  • Stdout (up to 8 KB) — delivered to the agent as a steer message on the next turn. Empty = silent.
  • Stderr + non-zero exit — surfaced as an error steer.
  • Timeout — 30 s hard kill; flagged in the observability entry.
Preservation

.auto/** survives the auto-revert — the entire .auto/ folder is preserved. (Legacy autoresearch.* paths are still preserved too, for in-flight sessions.)


Examples

Runnable reference scripts live in this skill's examples/ directory — one file per pattern. Paths are resolved against the skill directory (parent of SKILL.md). Browse them for inspiration; they're not policy.

  • examples/before/ — external search, qmd document search, anti-thrash, idea rotator, hypothesis reflection, context rotation
  • examples/after/ — learnings journal, macOS notification on new best, auto-tag winning commits

Each example is a complete, self-contained script with named constants, short helper functions, guard clauses, and intention-revealing names. Read the header comment for its purpose, copy to .auto/hooks/<stage>.sh, adapt.


Steps to add a hook

  1. Understand the session. Read .auto/prompt.md for the objective and metric; glance at .auto/measure.sh for the workload. Your hook should complement the loop, not duplicate it.

  2. Clarify the user's intent. What should happen, at which boundary? Research before / log after / notify on wins / intervene on thrash / etc.

  3. Start from an example in examples/ that's closest to the intent (resolve against the skill directory). If nothing fits, write from scratch following the same style (named constants, short functions, guard clauses, JSON stdin parsed with jq). If the request combines retrospective + prospective concerns, use both before.sh and after.sh — don't overload one.

  4. Copy, adapt, mark executable.

    mkdir -p .auto/hooks
    cp "<skill-dir>/examples/before/external-search.sh" .auto/hooks/before.sh
    # ... adapt the script ...
    chmod +x .auto/hooks/before.sh
    
  5. Sanity-test with a piped mock before relying on it in the loop:

    jq -n '
      {
        event: "before",
        cwd: ".",
        next_run: 1,
        last_run: null,
        session: {
          metric_name: "total_ms",
          metric_unit: "ms",
          direction: "lower",
          baseline_metric: null,
          best_metric: null,
          run_count: 0,
          goal: "test"
        }
      }
    ' | ./.auto/hooks/before.sh
    

    For after.sh, swap last_run: null for a run_entry object (see the schema above).

  6. Commit the hook alongside other session files. It's preserved across reverts because it lives under .auto/.


Rules of thumb

  • Read whatever fields the agent naturally writes — asi.hypothesis, asi.next_focus, asi.learned, description. Don't invent a "hook input" field and instruct the agent to populate it; that breaks the transparency principle.

  • Silent is the default. Only print to stdout when you have something useful for the agent. Empty stdout means no steer.

  • Guard with early exits. [ -z "$query" ] && exit 0 is cheaper and clearer than wrapping everything in if.

  • One concern per script. If you want research + learnings, put them in separate files (before.sh and after.sh). Don't bundle.

  • No environment variables. Everything is on stdin; extract cwd (and anything else) with jq. There is no $AUTORESEARCH_WORK_DIR.

Comments

Markdown supported