Draft:Harness Config
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed arti
Submission declined on 2 June 2026 by GearsDatapacks (talk).
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
| Harness Config | |
|---|---|
| Original author | Jalil Laaraichi |
| Developer | Harness Config contributors |
| Release | May 26, 2026[1] |
| Preview release | 1.0.0-alpha.7
/ June 1, 2026[1] |
| Written in | TypeScript |
| Operating system | Cross-platform |
| Platform | Node.js |
| Type | Configuration management, developer tool |
| License | Apache License 2.0 |
| Website | www |
Harness Config is an open-source specification proposal and reference implementation for managing repository-local configuration used by AI coding agents and developer-facing tool runtimes.[2][3] The project proposes a source-to-surface model in which reviewed configuration is kept in a durable source layout, commonly under .harness/, and projected into declared harness surfaces such as AGENTS.md, .agents/, .claude/, and .cursor/.[4]
The project includes a TypeScript reference implementation and a command-line interface named harnessc.[1] The repository describes the standard as a v1 specification proposal with an alpha reference implementation.[2]
Background
Software repositories increasingly contain configuration files for multiple AI coding tools. These files may include instruction documents, rules, prompts, skills, hooks, and local runtime settings. Different tools often read from different repository-local files or folders, which can lead to repeated instructions and unclear ownership of configuration.[3]
Harness Config addresses this problem by separating durable source configuration from live tool-facing files and folders. The project describes these tool-facing locations as "harness surfaces". A harness surface is a repository-local file or folder that a harness reads from while operating on a project.[4]
Design
Harness Config uses a one-way projection model. Authored configuration is kept in configured source roots. A manifest file, usually .harness/harness.toml, declares source roots and target locations. Projection computes the files that should appear in each declared target, and activation writes that projection to disk.[4]
The model is intended to make ownership of repository-level harness configuration explicit. In this model, .harness/ is used as a reviewed source layout, while live harness surfaces are treated as projected outputs rather than durable source repositories.[3]
The standard defines several concepts, including resources sources, dir sources, target declarations, target-specific overrides, composable instruction files, profiles, ignore rules, and mutable files.[4] Mutable files are projected once from source and then treated as runtime-owned target files unless explicitly forced to be regenerated.[4]
Command-line interface
The reference command-line tool is harnessc. It can validate a repository configuration, explain how a path participates in projection, preview activation, and apply projected outputs.[1]
The activation command is dry-run by default. Running harnessc activate previews planned changes, while harnessc activate --yes applies them.[1] The CLI reports actions such as created files, updated files, kept files, preserved unmanaged entries, and mutable files left untouched by activation.[4]
Features
Harness Config supports explicit target declarations, source-to-target copy projection, target-specific overrides, profile overlays, composable instruction files, projection ignore rules, and runtime-owned mutable files.[4] These features allow a repository to share configuration across multiple tools while still producing tool-specific outputs when needed.[4]
The project documentation emphasizes that Harness Config does not require every tool to receive identical configuration. Shared resources can remain shared, while Codex, Claude, Cursor, and other tools can receive tailored projected files.[3]
Licensing
Harness Config is released as open-source software under the Apache License 2.0.[2]
See also
References
External links
Category:Free software programmed in TypeScript Category:Software using the Apache license Category:Configuration management Category:Command-line software
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.
- provide significant coverage: discuss the subject in detail, not just brief mentions or routine announcements;
- are reliable: from reputable outlets with editorial oversight;
- are independent: not connected to the subject, such as the subject's own website, or sponsored content.
Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia.