Skip to content

fix(ssh): match container history to the verified author role - #205

Merged
makeitfutureDev merged 1 commit into
betafrom
fix/ssh-author-runtime
Oct 25, 2026
Merged

makeitfutureDev merged 1 commit into
betafrom
fix/ssh-author-runtime

Conversation

@makeitfutureDev

Copy link
Copy Markdown
Owner

SSH previously omitted the verified user's admin rank when resolving its container, sending admin SSH sessions to project HOME while their ordinary chat turns used admin HOME. Pass the current verified rank at attach and refresh, disconnect on a scope change, and recheck the resolved target's operator-home grant before entering it.

Keep session-file, login and held/current MCP relay cleanup scoped to each container so concurrent admin/project sessions do not retain or revoke each other's state. Explain history scopes in connection guidance and document persisted host keys. No histories are migrated or deleted; the existing Admin + operator-home SSH refusal remains enforced.

Validation:

  • 67 targeted author-isolation and SSH tests passed, including 7 new regressions. The initial routing/cleanup regressions failed against the original implementation.
  • Static checks, secret scan, security coverage gates and DCO check passed.
  • Independent security review found no introduced blocker.
  • Claude and Codex live acceptance definitions registered; live terminal/VS Code execution remains pending deployment and is not claimed as passed.

Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
@makeitfutureDev
makeitfutureDev merged commit 226f278 into beta Oct 25, 2026
2 of 5 checks passed
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