-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Unable to load Session history after 1.0.30-block.202506272302-a3ef5 #3200
Copy link
Copy link
Closed
Description
Describe the bug
After updating Goose to 1.0.30-block.202506272302-a3ef5, I could no longer open up my sessions. However, Goose can find the files in /Users/benjaminersando/.local/share/goose/sessions/. See Slack thread for more details.
To Reproduce
Steps to reproduce the behavior:
- Click Settings Icon
- Click on Session History
- See error
Expected behavior
See session summaries instead of error in step 3.
Where Goose gets stuck when asking to open jsonl:

When I ask goose to retrieve the last message:


Enormous goosed.log after a reboot today:

Please provide following information:
- OS & Arch: MacOS 15.5 (24F74)
- Interface: UI
- Version: 1.0.30-block.202506272302-a3ef5
- Extensions enabled: Developer, Memory. Also none.
- Provider & Model: Sonnet 4
Additional context
Potentially interesting logs I found in 20250701_110414-goosed.log (I also see this in the previous day's logs):
2025-07-01T18:05:22.498161Z DEBUG goose::agents::subagent_manager: crates/goose/src/agents/subagent_manager.rs: SubAgentManager dropped
2025-07-01T18:05:22.498547Z INFO goose::agents::tool_router_index_manager: crates/goose/src/agents/tool_router_index_manager.rs: Indexed platform tools for vector search
2025-07-01T18:05:22.508505Z DEBUG goose::config::base: crates/goose/src/config/base.rs: Created config backup: "/Users/benjaminersando/.config/goose/config.yaml.bak"
2025-07-01T18:05:22.633119Z DEBUG goose::config::base: crates/goose/src/config/base.rs: Created config backup: "/Users/benjaminersando/.config/goose/config.yaml.bak"
2025-07-01T18:05:26.743165Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
2025-07-01T18:05:26.766104Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
2025-07-01T18:05:26.785588Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
2025-07-01T18:05:26.804432Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
2025-07-01T18:05:26.824624Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
2025-07-01T18:05:26.845040Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
2025-07-01T18:05:26.864742Z WARN goose::session::storage: crates/goose/src/session/storage.rs: Session file exceeds size limit during metadata read
Here are the normal sized logs following the extremely large ones:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels

