Skip to content

Removed redundant extension check with goose config when resuming a session #6759

Merged
lifeizhou-ap merged 1 commit intomainfrom
lifei/remove-check_missing_extensions_or_exit
Jan 28, 2026
Merged

Removed redundant extension check with goose config when resuming a session #6759
lifeizhou-ap merged 1 commit intomainfrom
lifei/remove-check_missing_extensions_or_exit

Conversation

@lifeizhou-ap
Copy link
Collaborator

@lifeizhou-ap lifeizhou-ap commented Jan 28, 2026

Summary

Remove check_missing_extensions_or_exit function. The function checks whether original session extension exists goose config when resuming a session. This check is redundant and unnecessary now.

Discussion: #6502 (comment)

Type of Change

  • Feature
  • Bug fix
  • Refactor / Code quality
  • Performance improvement
  • Documentation
  • Tests
  • Security fix
  • Build / Release
  • Other (specify below)

Testing

Manual

Copilot AI review requested due to automatic review settings January 28, 2026 00:48
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes the CLI’s resume-time “missing extensions” check that compared session-saved extensions against the current global goose config, avoiding redundant/incorrect warnings or cancellations when resuming sessions.

Changes:

  • Deleted check_missing_extensions_or_exit and its dependency on get_extension_by_name.
  • Simplified the resume-path extension selection to directly use EnabledExtensionsState’s saved extensions (falling back to get_enabled_extensions when absent).
  • Cleaned up related imports.

@lifeizhou-ap lifeizhou-ap merged commit 43967d5 into main Jan 28, 2026
21 checks passed
@lifeizhou-ap lifeizhou-ap deleted the lifei/remove-check_missing_extensions_or_exit branch January 28, 2026 01:02
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.

2 participants