A remote such as center.for.cybernetic.beauty@tangled.org:did:plc:… is a working tangled.org remote: git pushes over it. tang only took the git user (git@tangled.org:…, ssh://git@tangled.org/…), so in such a clone every command said "Not in a Tangled repository" and needed -R.
The SSH user names the account that pushes, never the repository. So isTangledRemote and parseTangledRemote now accept any user of letters, digits, dots, dashes and underscores. The host is still matched exactly, and the path is read as before: owner/name, or a bare repository DID.
Tested. The new cases went red first. A test that another host, or an empty or spaced user, is still refused stays green. In a clone whose remote has a handle as its user, tang context now resolves the repository and tang issue view works without -R. bun run check passes (458 tests).
🤖 Generated with Claude Code