Skip to content

fix: display the leash active notification in status bar for pi - #2

Open
bge-kernel-panic wants to merge 1 commit into
mainfrom
add-pi-status-bar
Open

fix: display the leash active notification in status bar for pi#2
bge-kernel-panic wants to merge 1 commit into
mainfrom
add-pi-status-bar

Conversation

@bge-kernel-panic

Copy link
Copy Markdown

Extensions such as ponytail interfere with the leash message and it's super important to view the leash status icon to make sure it's actually started before using the agent.

Extensions such as ponytail interfere with the leash message and
it's super important to view the leash status icon to make sure it's
actually started before using the agent.
Copilot AI review requested due to automatic review settings July 10, 2026 21:47

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Pi extension to make Leash’s “active” signal visible in the status bar (to avoid interference from other extensions that may hide notifications), and increments the package version.

Changes:

  • Set a Pi status-bar entry on session_start indicating “🔒 Leash active”.
  • Bump @sailthru/leash version from 1.0.17 to 1.0.18.
  • Add an allowScripts section in package.json.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File Description
packages/pi/leash.ts Adds ctx.ui.setStatus(...) on session start to show Leash as active in the status bar.
package.json Version bump and introduces allowScripts configuration.
dist/pi/leash.js Updates compiled Pi bundle to include the new status-bar call.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread package.json
Comment on lines +72 to 76
"allowScripts": {
"esbuild@0.27.7": true,
"msgpackr-extract@3.0.4": true,
"sharp@0.34.5": true
}

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

it's needed because those are build scripts and otherwise the build fails to 100% run. Since the version is locked and I checked those packages for known vulnerabilities (note I looked for any mention online, did not inspect the code), I beleive this is 100% safe.

@bge-kernel-panic

Copy link
Copy Markdown
Author

@bpediredla-mg Small QoL for Pi agent users (i.e. me right now ;) )

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