Follow CONTRIBUTING.md and the component's instructions. For validation and shipping, use docs/validation-and-release.md. For product names, terminology, and visible copy, follow the Naming System. - Measure the user's request through completion. Record implementation, validation, merge, publication, and waiting separately; an Actions duration is not the total. - Choose the necessary checks before starting them. Run affected tests and relevant integration checks; use full suites for broad changes. Start independent checks together within the machine's capacity. Do not add a second full…
1.4k17d agoReviewMountCreate a free account to mount
Read this before changing anything under cli/. The repository-wide process rules (validation, merging, releases) are in ../AGENTS.md. The design, and why, is in ../docs/design/2026-10-03-harnessd.md. The one-page picture for new contributors is ../docs/design/2026-10-04-harnessd-before-after.md. The master runs the core and every service process (SERVICE_HOSTS in src/harnessd/services.ts). Each service process runs one or more services, each on its own link to the core. In Activity Monitor and ps they show as harnessd, harnessd-core and harnessd-<process> (src/harnessd/processName.ts). HARNESSDSERVICES names a subset to run in…
Steady38 mentions in 2 weeks
No other project uses it yet
1.4k17d agoReviewMountCreate a free account to mount
Use CLAUDE.md for architecture, build commands, and testing. For DSH dashboards, follow the DSH workspace contract: 70% viewer on the left, 30% real agent chat on the right, including loading, missing dependencies, failures, retries, and restoration. Reserve the chat slot before startup; never let an unavailable conversation become a full-width viewer. The Swarm's Your devices is a dashboard-only exception: fill its center pane, keep the sidebars visible, and do not start or reserve a Devices conversation. Standalone Devices retains its…
Steady38 mentions in 2 weeks
No other project uses it yet
1.4k17d agoReviewMountCreate a free account to mount
Before creating or changing a DSH, read the authoring guide and the DSH workspace contract. A DSH dashboard always has the real agent chat to its right, initially 70% viewer and 30% chat. Loading or failed setup must keep that chat slot and show recovery there. Verify the whole workspace, including failures, rather than only the viewer. Package AGENTS.md files describe the materialized agent's job; they do not replace this desktop integration contract.
Steady38 mentions in 2 weeks
1 project uses a version of this
1.4k17d agoReviewMountCreate a free account to mount
Follow CONTRIBUTING.md and the component's instructions. For validation and shipping, use docs/validation-and-release.md. For product names, terminology, and visible copy, follow the Naming System. - Measure the user's request through completion. Record implementation, validation, merge, publication, and waiting separately; an Actions duration is not the total. - Choose the necessary checks before starting them. Run affected tests and relevant integration checks; use full suites for broad changes. Start independent checks together within the machine's capacity. Do not add a second full…
Steady38 mentions in 2 weeks
No other project uses it yet
1.4k17d agoReviewMountCreate a free account to mount
This file provides guidance to Codex and other coding agents when working in this repository. Treat CLAUDE.md as the upstream source of truth; this file is the Codex-compatible mirror of those project rules. This repo is developed across multiple AI-assisted environments. The following rules apply to all code changes: 1. Update docs on code change - When changing behavior, architecture, or APIs, update both the English and Vietnamese docs. Keep numbers, flows, endpoints, and states accurate with the code. Platform…
4947mo agoReviewMountCreate a free account to mount
AGENTS.md is directory-scoped guidance, not a role selector. This root file applies to any coding-agent session operating in the source repository. Shared architecture rules come first. The section Coding agents building this repository is specifically for agents modifying, reviewing, testing, or documenting Workshop; it is not the product-run workflow. A normal product run is launched in a separate persistent toy project. The host materializes the complete .agents/product-run/ template there, including its root AGENTS.md and nested .agents/skills/autonomous-workshop/SKILL.md. Autonomous Workshop is a…
2124d agoReviewMountCreate a free account to mount
Read the immutable run-root MAKE-OPTIONS.json before Make. Its check_motion is false by default; workshop wish, start, or fix with --check-motion true enables it for that run. Every operator resume reselects this option, defaulting to false; reread it even if this session previously enabled motion. The host migrates older runs before resuming them. If the file is absent in an unmigrated run, retain its original motion policy. When false, skip the Python motion sweeps, motion-manifest authoring solely for those checks, operating-animation…
2124d agoReviewMountCreate a free account to mount
You are Codex running in a Harness workspace for Workshop: describe a 3D object, get a validated, printable STEP part or assembly. This file is the whole workflow for that; it is the Make stage of Autonomous Workshop on its own, with no Inventor, Wish packet, host gate or shop. - CADSKILLROOT and WORKSHOPPYTHON are set in your environment. Every CAD command is "$WORKSHOPPYTHON" "$CADSKILLROOT/scripts/<tool>". Where a skill says CADSKILLROOT="$(workshop skills path)/cad", skip that line — the variable is already…
2124d agoReviewMountCreate a free account to mount
autonomous-aiAGENTS.md