aget-wake-up

To get a quick agent session status briefing, run a wake-up protocol that surfaces the agent's identity, version, and operational state. This eliminates manual file inspection by executing a script or fallback commands to summarize the session.

Checking git status and version before launching research tasks is done by running a wake-up protocol that reads local files like version.json and AGENTS.md headers. This provides an immediate briefing of the repository state and software version.

The wake-up protocol works by applying resilient fallbacks if the startup script fails, reading local version.json, AGENTS.md headers, and git status directly. It explicitly handles script exit codes to ensure the session diagnostics still complete.

Yes, you can use this agent diagnostics protocol for supervisor fleet checks because it reports fleet size and active project context. It summarizes operational status across local repository agent startups, making it ideal for fleet monitoring.

An AGET agent session startup report includes agent name, software version, repository state, fleet size, and counts of skills and learnings. This human-readable briefing allows operators to quickly confirm the active project context.

You need to count skills and learnings during local repository agent startup to provide supervisors with a complete operational profile of the agent session. This count helps verify the active project context and agent readiness before long-running tasks.