Before filing
Closest existing issue
None found.
What's broken
The right-side workspace browser fails to load an attached empty, non-Git directory, even though Berd records the folder correctly and the agent can access it. The displayed recovery action, “Try again,” does not respond.
Steps to reproduce
- Launch Berd 0.6.2 on macOS.
- Open a Goose chat whose working directory is an empty, non-Git directory. The issue was reproduced with both an existing chat and another session attached to the same directory.
- Open the right sidebar and view the Context, Changes, or Files area.
- Observe “Couldn't load this folder. Try again.”
- Click “Try again.”
- Observe that nothing happens and the folder remains unloaded.
The affected folder existed, was readable by the current user, and had standard drwxr-xr-x permissions. The model is not relevant to this app-shell file-browser behavior. Whether the affected chats had prior transcript history was not recorded.
What you expected to happen
The right sidebar should display an attached directory even when it is empty and not a Git repository. If loading fails, “Try again” should retry the operation.
What actually happened
The folder remained on the “Couldn't load this folder” state. “Try again” did not respond. Collapsing and reopening the sidebar, switching chats, and restarting Berd did not resolve it.
How often does it happen?
Every time in two sessions attached to the affected directory.
Berd version
0.6.2 (the latest release at the time of filing)
Operating system
macOS (Apple Silicon)
Model and provider
n/a — this concerns the app-shell workspace browser. The affected sessions used the Goose harness; the originally recorded model was gpt-5.6-sol, provider unknown.
Relevant log output
No relevant log output. The app log was checked for folder-loading or sidebar errors around the reproduction period.
Screenshots, recordings, or other context
No screenshot or recording is attached yet. The visible error text was: “Couldn't load this folder. Try again.”
Before filing
Closest existing issue
None found.
What's broken
The right-side workspace browser fails to load an attached empty, non-Git directory, even though Berd records the folder correctly and the agent can access it. The displayed recovery action, “Try again,” does not respond.
Steps to reproduce
The affected folder existed, was readable by the current user, and had standard
drwxr-xr-xpermissions. The model is not relevant to this app-shell file-browser behavior. Whether the affected chats had prior transcript history was not recorded.What you expected to happen
The right sidebar should display an attached directory even when it is empty and not a Git repository. If loading fails, “Try again” should retry the operation.
What actually happened
The folder remained on the “Couldn't load this folder” state. “Try again” did not respond. Collapsing and reopening the sidebar, switching chats, and restarting Berd did not resolve it.
How often does it happen?
Every time in two sessions attached to the affected directory.
Berd version
0.6.2 (the latest release at the time of filing)
Operating system
macOS (Apple Silicon)
Model and provider
n/a — this concerns the app-shell workspace browser. The affected sessions used the Goose harness; the originally recorded model was
gpt-5.6-sol, provider unknown.Relevant log output
Screenshots, recordings, or other context
No screenshot or recording is attached yet. The visible error text was: “Couldn't load this folder. Try again.”