session_ping
Record your current task and modified files so the next AI provider can reconstruct progress even if the session was interrupted. Use this checkpoint every ~5 tool calls or after completing a significant step.
Instructions
Lightweight checkpoint — call this every ~5 tool calls or whenever you complete a significant step. Stores the current task + files touched so session_start on the NEXT provider can reconstruct what happened even if session_end was never called (e.g. Claude context limit hit, window crashed). This solves the provider-switching problem: Claude → Copilot → Cursor all see the same last checkpoint. Extremely fast — one Redis SET, no blocking operations.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | What you are currently working on (e.g. "Implementing invite handler in handler/invite.go") | |
| provider | No | Current AI provider (e.g. "claude-code", "copilot", "cursor", "windsurf") | |
| next_step | No | What the NEXT step is after this checkpoint (helps next provider resume immediately) | |
| instance_id | Yes | UUID of the cache instance | |
| files_touched | No | Files modified so far this session |