Skip to content

Require peer comparison for CLI operational conventions #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
irl-dan merged 1 commit into from
Oct 6, 2026
Merged

Require peer comparison for CLI operational conventions #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# OpenProse CLI repository guidance

**For agents.** These instructions apply throughout this repository, including
root packaging, distribution and harness integrations. Follow narrower
instructions where applicable. For changes beneath `cli/`, read
[implementation rules](cli/AGENTS.md) and [contributor guidance](cli/CONTRIBUTING.md).
This file does not change the CLI's runtime defaults or the OpenProse language.

## Prefer established operational conventions

Before implementing conventions for packages, installation, distribution,
updates, configuration, credentials, cache/state/log locations or diagnostics,
inspect the current official documentation or source of comparable established
tools. Relevant peers include Codex, Claude Code, OpenCode and Prime Agent.
Record the comparison in the task, design note or PR before implementation:
sources, areas of agreement, meaningful differences and the selected approach.

Where peers agree, prefer their established convention. Do not introduce a
custom alternative without first documenting the concrete requirement that
existing conventions cannot satisfy, its user impact and any migration cost.
Where peers differ, report that variation and select an established approach
suited to the product; do not manufacture consensus or require unanimity.
Explicit user decisions take precedence over this general selection guidance.

Keep user preferences independent of whether the executable comes from npm,
npx, Homebrew or a standalone archive. Distinguish installation artifacts,
user configuration, credentials and reconstructible caches. Preserve explicit
user overrides during upgrades. Missing configuration should inherit built-in
defaults; do not write those defaults as user overrides automatically.

This constraint governs operational plumbing. It does not authorize copying
another tool's language semantics, bypassing local controls, broadening
permissions or claiming capabilities that have not been implemented and tested.
Loading