DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to claim a code area so other agents see ownership with Foremerge

Mark which agent is working on a symbol, with an advisory lease that never blocks anyone.

Who it is forA developer whose agents may overlap on one area and who wants visible ownership without locking files.

The problemAgents cannot see who is already working on a symbol, and file locks would stall the whole fleet if one agent crashed.

The outcomeEach agent's claim is visible to others in a query, and overlapping claims show as warnings rather than blocks.

What you need first

  • Git and jq installed
  • macOS or Linux, or the Windows binaries from the releases page
  • A Git repository to coordinate, with at least one coding agent or a shell to act as one
  • Rust 1.85+ only if you build from source

Steps

  1. Claim the scope with foremerge --json work claim --agent "$STRIPE_AGENT" --intent "$STRIPE_INTENT" --scope symbol:PaymentService --reason "Changing the provider boundary", using the agent and intent ids from your earlier publish. (inferred, check the README)
  2. Claim the same scope for a second agent with its own intent id and a reason.
  3. Read the second claim's advisory_only and warnings fields with jq '.data | {advisory_only, warnings}'.
  4. List who holds the scope with foremerge --json work query --scope symbol:PaymentService | jq '.data[] | {agent: .agent.name, intent: .intent.summary, open_conflicts}'. (inferred, check the README)

Prompt for your agent

In the <repo path> repository, have two registered agents claim symbol:<target> with separate intents and reasons. Expected output: both claims succeed and the second response includes an overlap warning. Verify that advisory_only is true in the claim data before you tell anyone the scope is owned.

Caveat. A claim is advisory and never exclusive ownership, so agents still have to read the warnings and decide for themselves.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page