KamoCRM

An AI workstation's take-over and MCP token are written only by their own UPDATEs

Fixkamo-shared-library
Shipped
September 27, 2026 at 8:39 PM UTC
Author
Kamo
Commit
1159a19

control_member_id/_started_at and **************** are now updatable = false, and HostedComputerRepository gains the only writes they get: recordControl, clearControl, recordMcpToken, clearMcpToken and clearAiSession (native, each in its own transaction). A save() is a merge of a copy and wrote every column as the copy had it. The ComputeService sweeps save copies read minutes earlier, so a hand-back made in the meantime was put back (the resumed AI found its computer TAKEN_OVER, with no token) and a token minted in the meantime was reverted (the re-mint closed the AI's live MCP session). SP11 final review, IMPORTANT 2.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing