Safety locks and sessions
Control when agents may act and keep related work in a named session.
| State | Permitted classes |
|---|---|
| Unlocked | Tools allowed by the key and resource policies. |
| Soft Lock | Public, discovery and read operations; no mutations. |
| Hard Lock | Public operations only. |
Check the effective state
Use server.status to inspect lock and schedule information. Review manual lock controls and working-hours settings under AICOM → Safety. Effective restrictions still apply even when a key has the required scope.
Open a session before changes
session.status({})
session.open({"name":"Update contact copy","description":"Back up the page, update the requested text and verify."})Writes, destructive operations and sensitive administration require an open session. If one is already active, inspect it before starting another. Use a name and description that explain the actual work.
Verify and close
Read back changes and inspect the public result where relevant, then call session.close. The session groups audit records; opening one does not grant new scopes or disable locks.
Recovery
Back up supported content before editing. Recovery depends on the operations and available snapshots, and may not cover an entire session. See backup and recovery and AICOMBase.
Reviewed for AICOM 3.23.1 · 22 October 2026. Your installed version and permissions determine available features.