Skip to content

Bug: agentctl peek cannot read a stopped session that agentctl status can still resolve #149

@c-h-

Description

@c-h-

What happened

While supervising a completed opencode session, agentctl status <id> returned the stopped session metadata, but agentctl peek <same-id> -n 200 returned Session not found.

Expected

If status can resolve a stopped session, peek should also be able to resolve it (or status should expose the log path/summary needed for post-run supervision).

Repro

  1. Launch an agentctl session and let it stop normally.
  2. Run agentctl status <id> — session is found.
  3. Run agentctl peek <id> -n 200 — returns Session not found.

Example

  • Session id: 2f299488-78a8-44f4-8527-bb7594683e96
  • Adapter: opencode
  • CWD: ~/code/mono-eng-8669-retry
  • agentctl status --json returned the session metadata successfully
  • agentctl peek failed for both the full id and short id

Workaround

Use agentctl status --json plus repo/PR inspection, but this loses the actual session output needed by the coding-agent supervisor flow.

Environment

  • macOS Darwin 25.2.0 arm64
  • OpenClaw workspace on Charlie's Mac Studio
  • agentctl used via globally linked CLI

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions