---
{
  "n": 76,
  "title": "An environment has one live session; a second asks the user to take over",
  "abstract": "",
  "refs": [],
  "seen": [
    "agent"
  ],
  "data": {
    "keywords": [
      "session",
      "environment",
      "sessions"
    ],
    "environment": "main"
  },
  "created": 1791670802.555278,
  "updated": 1791670860.330664,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "rule"
}
---
The user's ruling, 2026-10-11, refined in his own words: 'we shouldn't be able to have multiple sessions on an environment. The journal should tell the user, Hey, there's a session already here. What do you want to do? Do you want to take over? That means that the other session is unbound to that environment.' So a session starting on an environment that already has a live one does not take it silently and does not stop the other by itself: the journal asks the user what to do. On take over, the session that was there is unbound from the environment and the new one holds it; otherwise the new session does not get the environment. It came after his messages 25226, 25229 and 25230 reached a session he was not watching, while environment main held three live sessions at once.