NousResearch/hermes-agent

Proposed autoresearch skill: autonomous git-based experiment loop

Cluster 4822 · skills. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
7items grouped
Known?
Yes. 7 related items grouped here, 4 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and pull requests all concern a proposed 'autoresearch' skill featuring an autonomous, git-based experiment loop for ML optimization and knowledge research. The members appear to be duplicates, variants, or iterative rescopes of the same feature proposal.

Open issues1

  • Issue#5114[Feature]: Autoresearch skill - autonomous git-based experiment loop for ML optimization and knowledge research

Open PRs1

  • PR#76350feat(skills): add autoresearch — autonomous git-based experiment loop (rescope)

1 PR closed without merging

From the close comments: duplicate 1

  • #5175 feat(skills): add autoresearch — autonomous git-based experiment loop · duplicate → #5112, #7911
Closed issues · 4
  • Closed#4822Feature: Autoresearch Skill - Autonomous Git-Based Experiment Loop for ML Optimization and Knowledge Research
  • Closed#4823Feature: Autoresearch Skill — Autonomous Git-Based Experiment Loop for ML Optimization and Knowledge Research
  • Closed#4824Feature: Autoresearch Skill — Autonomous Git-Based Experiment Loop (inspired by Karpathy's autoresearch)
  • Closed#4832[Feature]: Autoresearch skill - autonomous git-based experiment loop for ML optimization and knowledge research
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.27: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
skills
Closed issues
4
Attempts
1 PR closed without merging

For your agent

The same facts, typed.