Skip to content

fix: correct log message when releasing browser with reuse=false#112

Merged
tnsardesai merged 1 commit intomainfrom
fix/browser-pool-release-log-message
Feb 13, 2026
Merged

fix: correct log message when releasing browser with reuse=false#112
tnsardesai merged 1 commit intomainfrom
fix/browser-pool-release-log-message

Conversation

@tnsardesai
Copy link
Contributor

@tnsardesai tnsardesai commented Feb 13, 2026

Summary

  • When releasing a browser with reuse=false, the CLI now logs "Deleted browser X from pool Y" instead of the misleading "Released browser X back to pool Y"
  • The original "Released" message is preserved when reuse is not set or is true

Test plan

  • Run kernel browser-pools release <pool> --session-id <id> --reuse=false and verify it says "Deleted browser ... from pool ..."
  • Run kernel browser-pools release <pool> --session-id <id> (no reuse flag) and verify it says "Released browser ... back to pool ..."

🤖 Generated with Claude Code


Note

Low Risk
Only changes CLI logging text based on an existing flag; no behavior, API calls, or data handling are modified.

Overview
Adjusts the browser-pools release CLI success output to reflect actual behavior when --reuse=false.

When reuse is explicitly set to false, the command now prints "Deleted browser … from pool …"; otherwise it keeps the existing "Released browser … back to pool …" message.

Written by Cursor Bugbot for commit 43ab9a8. This will update automatically on new commits. Configure here.

When a browser is released with reuse=false it gets deleted, but the
CLI still logged "Released browser back to pool". Now logs "Deleted
browser from pool" when reuse is explicitly set to false.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tnsardesai tnsardesai requested review from Sayan- and rgarcia and removed request for Sayan- February 13, 2026 17:06
@tnsardesai tnsardesai merged commit 477c6df into main Feb 13, 2026
2 checks passed
@tnsardesai tnsardesai deleted the fix/browser-pool-release-log-message branch February 13, 2026 18:36
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