Skip to content

Unable to load Session history after 1.0.30-block.202506272302-a3ef5 #3200

@bjersando

Description

@bjersando

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:

  1. Click Settings Icon
  2. Click on Session History
  3. See error

Expected behavior
See session summaries instead of error in step 3.

Screenshots
Observed error:
Image

Where Goose gets stuck when asking to open jsonl:
Image

When I ask goose to retrieve the last message:
Image
Image

Yesterday's logs:
Image

Enormous goosed.log after a reboot today:
Image

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:

20250701_110414-goosed.log
20250630_132239-goosed.log

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions