NEW RUNTIME

Topic hub

Claude Code

A New Runtime topic hub collecting signals, patterns, field notes, and public sources about claude code.

Short answer

  • Claude Code is tracked here as an evidence-linked topic, not as a static glossary entry.
  • The page connects raw observations to pattern hypotheses, longer analysis, and public sources.
  • Use it as the canonical landing page before drilling into individual records.

Field notes

Longer analysis

3 notes

  1. Claude Code Subagents Split Memory Instead of Inflating One Session

    Claude Code subagents show a practical form of agent memory hygiene: move noisy work into a separate context and return only the compressed result to the main session.

  2. Claude HUD Turns Agent Observability into a Status Bar

    Claude HUD shows that agent observability can begin as a small status line for context health, tools, running agents, and progress instead of a large dashboard.

  3. Long-Running Loops Need Goals, Not Keep-Going Prompts

    Long-running agent work is useful only with a testable goal, checkpoints, a terminal condition, and recovery policy; otherwise the loop becomes expensive blind continuation.

Raw signals

Recent observations

4 signals

  1. Claude Code Startup Context Can Be Reduced to 13K Tokens

    A measured context audit shows that tool descriptions and default instructions consume a material share of the initial window before repository work begins.

  2. Codex Can Import an Existing Claude Code Setup

    Codex CLI can reuse selected Claude Code skills, hooks, MCP configuration, and project instructions, making operational context more portable across agent runtimes.

  3. CLAUDE.md Shrinks as Skills, Hooks, and Subagents Mature

    Agent behavior moves out of one giant context file into scoped mechanisms that load only for the relevant task and lifecycle stage.

  4. Claude Code Can Build a Task-Specific Harness Before Coding

    Instead of applying one universal setup, the agent creates targeted scripts, checks, and context for the current task before entering the implementation loop.