Fork incorrectly reports “no conversation found” even when the Claude session has activity

[powyncify]

Description

Again, kudos for the rapid development of Agent View — it’s evolving impressively and already very useful.

The Fork feature is a great complement to Claude Code’s branching capability, but currently it appears to misdetect whether a conversation exists in the session.

Agent View reports:

Cannot fork: no conversation found.
Have at least one exchange with Claude first.

However, the session does contain multiple exchanges with Claude and is actively being used.

This suggests Agent View may be misreading the conversation state or using a detection method that fails under certain environments.

---

Steps to Reproduce

1. Create a Claude session in Agent View.
2. Have several exchanges with Claude (normal conversation).
3. Return to the Agent View dashboard.
4. Select the session.
5. Press f (Fork).

---

Expected Behavior

Agent View should create a new forked session based on the current conversation context, similar to Claude Code’s native fork functionality.

---

Actual Behavior

Agent View reports:

Cannot fork: no conversation found.
Have at least one exchange with Claude first.

even though the session clearly contains conversation history.

---

Environment

• OS: Windows 11
• Terminal: Windows Terminal
• WSL: Ubuntu (WSL2)
• Agent View version: v0.0.22+
• tmux: (output of tmux -V)
• Claude CLI: (output of claude --version)

Additional context:

• Claude sessions are launched from WSL but executed via Windows CLI wrappers (cmd.exe /c claude) to reuse Windows authentication.
• The issue has been present since initial adoption of Agent View and does not appear to be tied to a recent update.

---

Screenshot

Showing the message:

Cannot fork: no conversation found.
Have at least one exchange with Claude first.

while the session clearly contains activity.

---

Possible Cause (speculative)

Agent View may be checking for conversation state via a local conversation file or CLI state mechanism that differs when the Claude CLI runs through Windows interop (cmd.exe) rather than directly inside WSL.

---