OpenParable
Skip to content
← Back to skills

Convex Retention

Development
convex-retention

Convex Retention is an Agent Skill for development published in the openclaw/clawhub repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when adding or changing ClawHub Convex tables, TTL fields, cleanup crons, retention policy, auth/session cleanup, metric dedupe cleanup, or deprecated table removal

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/openclaw/clawhub/blob/HEAD/.agents/skills/convex-retention/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/convex-retention, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Convex Retention

Overview

ClawHub retention is code-owned. Every current Convex table must be classified in convex/lib/retentionPolicy.ts, and ephemeral tables need an indexed, bounded cleanup path unless their lifecycle is handled by usage-time validation or a documented component.

Checklist

  • Use clawhub-convex and read convex/_generated/ai/guidelines.md first.
  • Add every new schema table to RETENTION_POLICIES; the Record<TableNames, RetentionPolicy> type is the enforcement gate.
  • For ephemeral tables, prefer an explicit expiration field plus index, then prune with .withIndex() and .take(...).
  • For new generic TTL tables, prefer expirationTime to match Convex Auth. Keep existing expiresAt, dayStart, and processedAt fields unless that table already needs a real migration.
  • Use RETENTION_STANDARD_BATCH_SIZE for ordinary retention jobs. Keep incident-tested special cases, such as skillStatEvents, on their documented caps.
  • Cron jobs should schedule bounded cleanup entrypoints only. Large one-off production migrations or destructive backfills still start with convex-migration-helper.
  • Do not bulk-clear active auth state. Expired authSessions and authRefreshTokens are pruned by convex/retention.ts.

Verification

  • Add or update focused tests for policy classification and cleanup behavior.
  • Run the focused Vitest slice for touched cleanup modules.
  • Run bunx convex codegen after schema/API changes.
  • Run a real Convex runtime check such as bunx convex dev --once --typecheck=disable.