---
name: tangled-mirrors
description: Both repos are mirrored to tangled.org; how to push there
metadata: 
  node_type: memory
  type: reference
  originSessionId: 7ed8744a-1e31-4832-8cdc-3b726ab41f9a
---

`agent-orchestrator`, `project-orchestrator`, and `agent-orchestrator-benchmark` are mirrored to
**tangled.org**, owned by `notplants.bsky.social` (DID `did:plc:3nogfd4smhmbrv4wo6kl7zg2`). Push URLs:
- `git@tangled.org:did:plc:3nogfd4smhmbrv4wo6kl7zg2/agent-orchestrator`
- `git@tangled.org:did:plc:3nogfd4smhmbrv4wo6kl7zg2/project-orchestrator`
- `git@tangled.org:did:plc:3nogfd4smhmbrv4wo6kl7zg2/agent-orchestrator-benchmark`

**Auto-mirror is configured:** `origin` in both repos has TWO push URLs (git.autonomic.zone AND
tangled), so a plain `git push origin <branch>` fans out to both — no separate step. Set up with
`git remote set-url --add --push origin <primary>` then `… --add --push origin <tangled>` (the first
`--add` replaces the fetch-url default, so the primary must be re-added too). A standalone `tangled`
remote also exists for explicit `git push tangled …`. Tangled's git SSH wants **DIDs, not handles**,
in the path; the `Welcome to Tangled's hosted knot!` line is just a banner (not an error). If tangled
is unreachable, `git push origin` reports a failure for that target only.

Auth: dedicated key `~/.ssh/tangled-ed25519`, registered to the tangled bot account
`notplants-bot.bsky.social` (the bot's own DID is `did:plc:qfngkejlw4ghji2myc73hbdh`); `~/.ssh/config`
has a `Host tangled.org` block pointing `IdentityFile` at it. The PO repo's git identity is set
locally (see [[git-identity-local]]) and the standing rule is [[always-commit-and-push]].