gait-session-tracking

To audit a NetClaw session end-to-end, initiate a branch with gait_branch, record individual actions using gait_record_turn, and finalize the audit log with gait_log to preserve a complete changelog.

GAIT session tracking provides a structured lifecycle for NetClaw engagements by mandating a gait_branch at session start, recording every AI-assisted turn with gait_record_turn, and concluding with gait_log to preserve a complete changelog.

Yes, GAIT session tracking requires a GAIT MCP server and access to the GAIT_MCP_SCRIPT environment variable to execute lifecycle commands and record session branches, turns, and audit trails.

To pin a pre-change baseline before starting NetClaw operations, begin a new GAIT session branch using gait_branch to establish an immutable record of the initial state for troubleshooting and governance.

Yes, GAIT session lifecycle management supports reviewing audit trails across sessions, devices, and configurations by viewing the immutable logs generated through branch creation and recorded turns.

Recording every individual turn with gait_record_turn provides auditability by creating an immutable trail of AI-assisted actions and commits, which is essential for troubleshooting, governance, and compliance.