GCWing / GCWing/OpenBitFun

Possible complementary direction: LongHorizon-Harness for sustained agent tasks

Ouverte
#2,233 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
new idea
Langage dominant
Rust
Étoiles
2.3k
Forks
231
Merge moyen
2 h 46 min
PR mergées (30 j)
577

Description

Hi, I'd like to suggest a complementary direction for `BitFun`.

Project:
https://github.com/AMAP-ML/LongHorizon-Harness

Your project focuses on an agent harness and orchestration layer.

LongHorizon-Harness focuses on carrying one task across many rounds without state drift. It keeps the goal and verified progress in durable state, starts each execution round with a fresh context, and uses an independent Auditor before accepting progress.

Why this may be useful here:

- A short workflow note could show how to avoid context drift and premature completion in a task that spans many rounds.
- it adds an outer task-lifecycle layer without claiming to replace the project's existing agent or runtime

If this direction fits, I can prepare a small documentation or example contribution following the repository's conventions.

I am part of the team behind LongHorizon-Harness, so I wanted to disclose that connection.

Paper:
https://arxiv.org/abs/2608.01964

Project page:
https://lh-harness.pages.dev

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

The issue names no repository file, test, or entry point. Start by reviewing the repository's documentation and example conventions, then decide whether the proposed LongHorizon-Harness workflow fits. Done would be a scoped, accepted documentation or example contribution, but the issue does not define its contents.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
documentation
Type d'issue
Documentation
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
Calme
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.