Pi Ampersand
Integrating an AI collaborator into an existing workflow
The problem
The problem
Running two separate AI tools side by side usually means picking one: either a second assistant gets full control, or it's cut off from what's actually happening and can't contribute anything useful.
The approach
Pi Ampersand reads the user and assistant messages from an existing Pi session (each message clipped to a fixed length) and forwards them to a separate Ampersand session, which can respond with commentary surfaced back in the original conversation via a small set of commands. It's opt-in and off by default.
Implementation
Implemented
- Message forwarding from a Pi session to an Ampersand session
- /amp, /amp on/off and /amp <text> commands
- Off by default — sends nothing without an explicit API key and opt-in
Engineering decisions
Engineering decisions
Observation only, by design
The integration deliberately can't see tool calls, commands or file edits, and can't act on the session it's attached to — "it can talk but can't act," as the project's own documentation puts it. That's a scope boundary chosen on purpose, not a missing feature.
Results and status
Results and status
41 GitHub stars at time of review — a real, directly verifiable public engagement signal, not a business outcome. No commercial deployment or customer claim is made for this project.
Contributors & attribution
Contributors and attribution
Built by Sami Ansari, on top of the earendil-works/pi session platform.
Built on: earendil-works/pi
Have a similar operational challenge?
Tell us what's happening and we'll tell you honestly whether it's something we can help with.