A new Claude Code skill lets it check its own context

Long Claude Code sessions can become unreliable when the fills up. A person can see the remaining context through the on-screen display or by running `/context`, but Claude Code cannot run that built-in command by itself.

`/claude-context` is different because it is a skill, so Claude Code can call it during work and read its own context status. That makes it possible to build safer workflows, such as compacting earlier when the session gets crowded or taking action before five-hour and seven-day limits matter.

Claude Code still cannot start a fresh session on its own, so a more practical pattern is to delegate work to subagents while the parent agent watches the overall context. The wider pattern is the same across recent tools and habits: need cleaner memory, shorter project notes, decision logs, less terminal noise, and better access to web pages or repo knowledge so they do not lose the reasons behind earlier choices.

Key points

  • `/claude-context` is an alpha skill that lets Claude Code inspect its own context status.
  • The normal `/context` command is built in for humans, so Claude Code cannot run it itself.
  • The skill can support safer compaction or warnings before become a problem.
  • Claude Code cannot start a new session by itself, so subagents are a practical workaround.
  • Decision logs, repo wikis, and terminal-output cleanup all address the same context-loss problem.

Sources covering this story (12)

Read original