Skip to content

fix(web): folder links from chat open in the file tree - #2

Merged
pc-style merged 1 commit into
mainfrom
fix/web-folder-mentions-open-in-tree
Sep 9, 2026
Merged

fix(web): folder links from chat open in the file tree#2
pc-style merged 1 commit into
mainfrom
fix/web-folder-mentions-open-in-tree

Conversation

@pc-style

@pc-style pc-style commented Sep 9, 2026

Copy link
Copy Markdown
Owner

When the agent mentions a folder in chat (for example .agents/skills), clicking it opened a file surface for that path. The server refuses to read a directory, so the preview showed "Failed to read workspace file '.agents/skills' in '/home/exedev'." and the tree did not reveal anything.

The file surface now recognizes a directory from the workspace listing the tree already has. For a folder it skips the preview pane and error, and the tree expands and selects the folder instead.

Validation:

  • vp test run apps/web/src/components/files/FilePreviewPanel.test.ts: 10 passed
  • tsc --noEmit in apps/web: clean
  • vp lint on touched files: no new warnings

Written by Claude Fable 5.1 in Claude Code.

🤖 Generated with Claude Code

A folder mentioned by the agent opened as a file surface, which asked the
server to read a directory and showed 'Failed to read workspace file'.
The file surface now recognizes a directory from the workspace listing,
skips the preview pane, and expands and selects the folder in the tree.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@pc-style

pc-style commented Sep 9, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@pc-style
pc-style merged commit c79fd1c into main Sep 9, 2026
2 checks passed
@pc-style

pc-style commented Sep 9, 2026

Copy link
Copy Markdown
Owner Author

Asset host for upstream pingdotgg#10908: streaming render of a nested fence on the fix branch (idle frames dropped).

nested-fence-streaming-fast.mp4

@pc-style

pc-style commented Sep 9, 2026

Copy link
Copy Markdown
Owner Author

Asset host for upstream pingdotgg#10908, take two: same broad README prompt, unfixed server vs fixed server, plus the streaming clip (sped up).

Before: README spills out of the code block

After: one block, inner fences intact

after-readme-streaming-fast2.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant