Skip to content

Require agents to push a working branch immediately and read open PRs - #866

Merged
rogerSuperBuilderAlpha merged 1 commit into
contribfrom
cursor/remote-visibility-harness-d983
Oct 28, 2026
Merged

rogerSuperBuilderAlpha merged 1 commit into
contribfrom
cursor/remote-visibility-harness-d983

Conversation

@rogerSuperBuilderAlpha

Copy link
Copy Markdown
Owner

What changed

The researcher harness told agents to branch off contrib and push once, at the end. It did not tell them to push before editing, to keep pushing, or to read the other open branches and pull requests.

Every agent entry point now states the same three rules:

  1. Branch and push before substantive work. git fetch --all --prune, create a branch off contrib, and git push -u origin <branch> before the first edit. Open a draft pull request into contrib with the first commit.
  2. Commit and push after every meaningful step. A probe, an artifact, a protocol stage, or a checkpoint is pushed when it lands. Remote state is the recoverable state.
  3. Read other open branches and pull requests before starting, and again while working. git branch -r --sort=-committerdate, recent commits across those branches, and gh pr list --state open. Join an in-flight branch when it already covers the question.

main and contrib stay protected. The push target is the working branch. The nested dissertation repo follows the same three visibility rules on its own remote.

Files

  • AGENTS.md — canonical Remote visibility section, land flow, definition of done
  • CLAUDE.md, .cursorrules, .cursor/rules/remote-visibility.mdc, .cursor/rules/start-here.mdc, .github/copilot-instructions.md
  • README.md, NOW.md, START_HERE.md, OVERVIEW.md, llms.txt, CONTRIBUTING.md, GETTING_STARTED.md, PUBLISHING.md, REPO_LAYOUT.md
  • MAP.md, tools/build_map.py
  • Nested AGENTS.md files: org_frontier/, org_frontier/research/, org_frontier/qualitative/, org_frontier/survey/, org_frontier/recurrence/, foundations/, submissions/hospitality_phygital/, submissions/slacker_thirds/
  • Protocol: org_frontier/protocol/RESEARCH_PROTOCOL.md, org_frontier/protocol/README.md, org_frontier/protocol/new_question.py, org_frontier/protocol/question_pipeline.js, org_frontier/protocol/template/hypotheses.md, org_frontier/research/DAILY_REFRESH.md
  • submissions/dial_response_algorithmacy/corpus/CONTRIBUTING.md

The Slacker arm still does not commit chapter prose unless the session was asked to land changes. When it was, the three rules apply.

Checks

Index --checks for the map, directory, catalog, and research index are clean. new_question.py compiles and question_pipeline.js passes node --check.

Open work inspected before editing: one draft PR (#842, q221 temporal-null calibration) and the recent remote branches (Org Sci, harness path fixes, CFP arms, Berthon). None of them edit this harness rule.

Open in Web Open in Cursor 

The harness told agents to branch off contrib and push once at the end.
Every entry point now requires three things: push the working branch
before the first edit, commit and push after every meaningful step, and
read other remote branches and open pull requests so parallel work stays
aligned.

Co-authored-by: Roger Hunt <rogerSuperBuilderAlpha@users.noreply.github.com>
@rogerSuperBuilderAlpha
rogerSuperBuilderAlpha merged commit bad09b6 into contrib Oct 28, 2026
2 checks passed
rogerSuperBuilderAlpha added a commit that referenced this pull request Oct 28, 2026
Promote contrib to main: researcher harness remote visibility rules (#866)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants