Claude session links miss sessions under an agent's own config directory, and a failed read looks like no sessions #740

New issue

Open

opened 2026-10-07 04:13:42 +00:00 by claude · 3 comments

claude commented

2026-10-07 04:13:42 +00:00

Member

Found during IW-678 (Claude session links). Items:

ClaudeSessionsReader reads only the server's <CLAUDE_CONFIG_DIR>/sessions, so a Remote Control session started under another config directory (on this machine: the agents under ~/.claude while the server uses ~/.claude-iw) gets no Claude link on any page. LiveAgent.configDir makes the fix small: also read the sessions directories of the live agents' config directories.
The transcript fallback is skipped when one agent in a worktree has a config directory and another has none (unreadable environ), so the second agent's transcript is not read — AgentSessionService.scala configDirsFor uses the fallback only when the list is empty; review-phase-01-20261007-045846.md (architecture, error-handling).
A bad CLAUDE_CONFIG_DIR (server or agent) becomes None for transcripts with no message, and a failed /proc listing looks like "no agents" — ServerDaemon.scala claudeConfigDir.toOption, ClaudeConfigDir.ofEnviron, LiveAgentReader.agents getOrElse(Nil); review-phase-01-20261007-045846.md (error-handling).

Found during IW-678 (Claude session links). Items: - [ ] ClaudeSessionsReader reads only the server's `<CLAUDE_CONFIG_DIR>/sessions`, so a Remote Control session started under another config directory (on this machine: the agents under ~/.claude while the server uses ~/.claude-iw) gets no Claude link on any page. LiveAgent.configDir makes the fix small: also read the sessions directories of the live agents' config directories. - [ ] The transcript fallback is skipped when one agent in a worktree has a config directory and another has none (unreadable `environ`), so the second agent's transcript is not read — AgentSessionService.scala `configDirsFor` uses the fallback only when the list is empty; review-phase-01-20261007-045846.md (architecture, error-handling). - [ ] A bad `CLAUDE_CONFIG_DIR` (server or agent) becomes `None` for transcripts with no message, and a failed `/proc` listing looks like "no agents" — ServerDaemon.scala `claudeConfigDir.toOption`, ClaudeConfigDir.ofEnviron, LiveAgentReader.agents `getOrElse(Nil)`; review-phase-01-20261007-045846.md (error-handling).

mph referenced this issue from a commit

2026-10-07 04:15:21 +00:00

chore(IW-678): file follow-ups as #740 and #741

claude referenced this issue

2026-10-07 04:15:33 +00:00

IW-678: Claude session links for versioned binaries, per-agent config dirs, and the / board #742

claude commented

2026-10-07 23:40:37 +00:00

Author

Member

Intake: agent-ready
Workflow: diagnostic
Reason: all gates passed
Analysis: project-management/issues/IW-740/analysis.md on branch IW-740

Intake: agent-ready Workflow: diagnostic Reason: all gates passed Analysis: project-management/issues/IW-740/analysis.md on branch IW-740

claude added the

agent-ready

label

2026-10-07 23:40:37 +00:00

claude commented

2026-10-15 15:02:33 +00:00

Author

Member

Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin's batch-implement command does not compile against the iw-cli core on this branch

The branch was merged with main at 33e14e5f before the run. Since #778–#780, main returns TrackerError from the tracker port's forge calls, and the installed kanon plugin (lib/batch/ForgeCatchUp.scala:143) still expects String. No phase ran, and no batch-implement.log was written. The cause is in the plugin, not in this issue: every batch-implement run in iw-cli fails the same way until the plugin follows the port change.

[error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7
[error] Found:    Either[iw.core.model.TrackerError, Option[batch.ForgeState]]
[error] Required: Either[String, Option[batch.ForgeState]]
Compilation failed

Implement: needs-human Reason: batch-implement exit 1 — the kanon plugin's batch-implement command does not compile against the iw-cli core on this branch The branch was merged with `main` at 33e14e5f before the run. Since #778–#780, `main` returns `TrackerError` from the tracker port's forge calls, and the installed kanon plugin (`lib/batch/ForgeCatchUp.scala:143`) still expects `String`. No phase ran, and no `batch-implement.log` was written. The cause is in the plugin, not in this issue: every `batch-implement` run in iw-cli fails the same way until the plugin follows the port change. ``` [error] /home/mph/.local/share/iw/plugins/kanon/lib/batch/ForgeCatchUp.scala:143:7 [error] Found: Either[iw.core.model.TrackerError, Option[batch.ForgeState]] [error] Required: Either[String, Option[batch.ForgeState]] Compilation failed ```

claude added

needs-human

and removed

agent-ready

labels

2026-10-15 15:02:33 +00:00

claude commented

2026-10-16 17:10:41 +00:00

Author

Member

Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.

claude added

agent-ready

and removed

needs-human

labels

2026-10-16 17:10:41 +00:00