Skip to content

pi-package: tested end to end with OAuth and with a key #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
imers merged 1 commit into from
Sep 28, 2026
Merged

pi-package: tested end to end with OAuth and with a key #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/pi-package/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Removing the package does not revoke access. In Stuga, revoke the connection or

- Stuga's tools go through the adapter's `mcp` proxy tool, not one Pi tool each: the adapter registers servers added at runtime as proxy-only. To give the model direct tools, add your own `stuga` entry to `~/.pi/agent/mcp-adapter.json` with `"directTools": true`; that entry wins over this package's registration.
- With OAuth, the workspace's conventions are not in the prompt; the model reads them with `workspaces` action `instructions` before writing.
- Built against Pi 0.87.1 and pi-mcp-adapter 3.1.0.
- Tested end to end against Pi 0.87.1 and pi-mcp-adapter 3.1.0, with OAuth sign-in and with an agent key.

## Development

Expand Down
Loading