Discover and explore top open-source AI tools and projects—updated daily.
AncienttwoAI-powered auto-coding co-pilot
Top 73.5% on SourcePulse
Summary
This repository, repo-harness, addresses the challenge of making AI coding sessions (like those with Claude and Codex) repeatable and context-aware within a project. It transforms ephemeral chat-based interactions into a structured, file-backed workflow, enabling AI agents to coordinate effectively, reduce token consumption, and resume sessions from persistent artifacts rather than chat history. This is beneficial for engineers and power users seeking to integrate AI assistance robustly into their development lifecycle.
How It Works
The core innovation is the shift from chat memory to file-backed sessions. repo-harness uses a system of hooks and repository-local files to manage context, plans, handoffs, and review evidence. It leverages a pre-built CodeGraph index for efficient structural queries and employs progressive context loading via configuration files (.ai/context/context-map.json, capabilities.json) to minimize token usage. Agents interact with stable root contexts and capability blocks, drastically reducing the need to re-scan the repository in each session.
Quick Start & Requirements
curl ... | sh for macOS/Linux, irm ... | iex for Windows PowerShell) or using Bun/npx. Follow with repo-harness install for global bootstrap.--dry-run.repo-harness install command bootstraps the host runtime globally. To preview changes in a target repository, use repo-harness adopt --dry-run. To apply, use repo-harness adopt for existing repos or repo-harness-scaffold for new projects.scripts/check-task-workflow.sh --strict and bun test.Highlighted Details
.ai/harness/handoff/, tasks/current.md), ensuring continuity across sessions.tasks/reviews/<task>.review.md) and agent tracking, separating AI-generated evidence from human oversight.Maintenance & Community
The project is actively maintained, with the latest release noted as 0.8.1. Release notes are available in docs/CHANGELOG.md. No specific community channels (like Discord or Slack) or notable contributors/sponsorships are mentioned in the provided README.
Licensing & Compatibility
The provided README does not explicitly state the software license. This omission makes it impossible to determine compatibility for commercial use or closed-source linking without further inquiry.
Limitations & Caveats
The absence of a stated license is a significant blocker for adoption assessment. The system relies heavily on specific tooling like Bun and Bash, potentially limiting cross-platform compatibility or ease of setup in environments without these prerequisites. Advanced features like the MCP connector require substantial additional configuration and understanding of its protocols.
21 hours ago
Inactive
Josh-XT