Skip to content

Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS

fix: reconcile published forge-account review fixes

[._.]/ Adam Eivyf369e7791cf5
diff --cc docs/MANAGED_APP_FORGE_ACCOUNTS.md
index f25b5cf910,5a201e745b..6493ffbef8
--- a/docs/MANAGED_APP_FORGE_ACCOUNTS.md
+++ b/docs/MANAGED_APP_FORGE_ACCOUNTS.md
@@@ -85,14 -94,19 +94,19 @@@ account that should push — so most pe
Set the field when it is not: an organization repo, a bot account, or any repo
whose owner login differs from the account you push with.
- A pinned account is never second-guessed. If `gh` has no token for it on the
- repository's host, credential resolution refuses agent launches and PortOS-owned
- forge operations with `409 FORGE_ACCOUNT_UNAVAILABLE`. If the agent-spawn lookup
- exceeds its budget while the pin is present or still unresolved, it refuses the
- launch with `503 FORGE_AUTH_TIMEOUT`. Neither path silently falls back to a
- different account's token. Check `gh auth status -h <host>` and authenticate the
- pinned account on that host before retrying. Unpinned repositories retain their
- ambient-auth fallback.
+ ### When the selected account is unavailable
+
+ An explicit pin never falls back to another account or host. If `gh` cannot
+ return that account's token on the repository host, PortOS refuses the agent
-launch or forge operation with `FORGE_ACCOUNT_UNAVAILABLE`. A missing repository
++launch or forge operation with `409 FORGE_ACCOUNT_UNAVAILABLE`. A missing repository
+ path or origin also refuses an explicit pin. A timed-out spawn lookup refuses
-with `FORGE_AUTH_TIMEOUT` when a pin exists or the lookup has not yet established
++with `503 FORGE_AUTH_TIMEOUT` when a pin exists or the lookup has not yet established
+ whether one exists.
+
+ Check `gh auth status --hostname <host>` and sign in as the selected account on
+ that host. Scope refresh uses the same host and expected account; because
+ `gh auth refresh` refreshes only the active account, PortOS asks you to switch to
+ the selected account first when necessary.
## Related