Resume doesn’t auto-execute and uses an invalid session ID (Claude + Codex) — observed since v0.0.22 (WSL/Windows)

[powyncify]

First: Agent View is growing by leaps and bounds—huge kudos for the pace and quality.

Summary

The Resume workflow has never worked reliably for me (since ~v0.0.22). This affects Claude and Codex (perhaps more – we tested two).

There appear to be two problems:

1. Agent View prints the resume command but doesn’t execute it
   Example shown in the attached screenshot: claude --resume <session_ref> is inserted/visible, but it is not actually run (it doesn’t behave like “command + Enter”).

2. Even when executed manually, the resume ID is invalid for the tool
   When I manually run the exact command shown by Agent View, Claude returns:

   No conversation found with session ID: 872[...]
   

   (screenshot attached)

This suggests the resume action may be passing an Agent View internal identifier instead of the tool’s actual conversation/session identifier (or the ID is being truncated/incorrectly stored).

Steps to Reproduce (Claude)

1. Create a Claude session in Agent View.
2. Detach/stop/hibernate the session (any state that requires “resume”).
3. Trigger “resume” for that session in Agent View.
4. Observe the resume command is shown (e.g. claude --resume 872) but not executed.
5. Run the same command manually in the pane:

   claude --resume 872[...]

6. Observe:

   No conversation found with session ID: 872[...]
   

Steps to Reproduce (Codex)

Same pattern:

• Resume command appears but does not run automatically
• Manual execution doesn’t resume correctly (tool complains / session not found)

Expected Behavior

• Resume should execute automatically (equivalent of typing the command + pressing Enter).
• Resume should use the correct persisted tool session identifier (Claude/Codex conversation/session ID), so the tool actually resumes the prior conversation.

Actual Behavior

• Resume command appears but is not executed.
• The resume ID appears invalid (Claude cannot find the conversation).

Environment

• OS: Windows 11
• Terminal: Windows Terminal
• WSL: Ubuntu (WSL2)
• Agent View version: v0.0.22 and later (still reproducible)
• tmux version: (paste tmux -V)
• Claude version: (paste claude --version)
• Codex version: (paste codex --version)
• Note: tools are launched from WSL but run using Windows credentials (via cmd.exe interop / wrappers)

Attachments

• Screenshot showing:
  1. resume command displayed but not executed
  2. manual command returns “No conversation found…”