Possible complementary direction: LongHorizon-Harness for sustained agent tasks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start by reviewing Raven's existing documentation and example conventions, then read the linked LongHorizon-Harness project and paper for the proposed workflow. Done means a small, repository-consistent note or example that explains the complementary direction without replacing Raven's existing agent or runtime.
Written by the indexing model from the issue text.
Description
Hi, I'd like to suggest a complementary direction for Raven.
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
- Dominant language
- Python
- Stars
- 4.1k
- Forks
- 94
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 371
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EverMind-AI/Raven
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EverMind-AI/Raven#1029 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
EverMind-AI/Raven#1000 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
EverMind-AI/Raven#998 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
EverMind-AI/Raven#997 ·
Maintainers usually reply within 1 day
-
security: tool output scrubbing misses raven's own oauth token filesPossibly taken @akushonkamen claimed this 10 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EverMind-AI/Raven#842 · 2 comments ·
Maintainers usually reply within 1 day
All issues in EverMind-AI/Raven
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zach-blumenfeld/aip#13 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nathanmarlor/foxess_modbus#1287 ·
Maintainers usually reply within 4 days
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
OpenLakeForge/openlakeforge#498 ·
Maintainers usually reply within 1 day
-
good first issue hacktoberfest help wanted python
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
pollen-robotics/reachy_mini#1493 ·
Maintainers usually reply within 1 day