“Check this branch, fix the failing test, and open a pull request.”
OpenCode edits the code and runs the test.
Pipa sends the result and pull request link back to Slack.
Pipa is a Slack integration that sends requests to OpenCode on your computer and returns replies to the same thread.
# trusted-agent-channel
YOU - 9:42 AM
@Pipa Fix the broken signup test and open a pull request.
PIPA - 9:47 AM
Fixed the test. All tests pass. Pull request #76 is ready.
You need Node.js 22+, OpenCode v1, and permission to create a Slack app. Pipa uses the OpenCode setup you already have.
npm install --global @usepipa/pipaInstall Pipa.
pipa initSet up Pipa in the folder where OpenCode should work.
pipa startStart Pipa, then mention it in Slack.
“Check this branch, fix the failing test, and open a pull request.”
OpenCode edits the code and runs the test.
Pipa sends the result and pull request link back to Slack.
“Review today's work and tell me what is blocked.”
OpenCode reviews your work and tools.
Pipa sends the brief back to Slack.
“Turn these notes into a launch checklist and save it with the project.”
OpenCode reads the notes and writes the checklist.
Pipa sends the file and a short summary back to Slack.
Free and open source. It runs on your computer, so you manage the setup and keep the computer running.
Read the full install guideSchedule OpenCode work to SlackGet a daily business brief in SlackUse OpenCode remotely from SlackWe set it up, host it, and keep it working for your company.
Explore Pipa ManagedNeed more help? Read the OpenCode Slack tutorial.
Pipa not replying in Slack? Check the OpenCode Slack troubleshooting guide for allowlists, app setup, and the local process.
Pipa is a Slack integration for OpenCode. You install Pipa Local as a standalone command-line tool (CLI), not an OpenCode plugin. It runs on your computer, sends Slack messages to OpenCode, and replies in the same thread.
Slack MCP tools let OpenCode access Slack data and take actions in Slack, depending on the connected server's tools and permissions. Pipa brings requests from Slack into OpenCode and returns replies to the same thread. Pipa's Slack bridge does not require a Slack MCP server.
No. Pipa Local only works while pipa start is running and your computer is on. Pipa Managed runs on a hosted computer.
During setup, you choose the folder where Pipa opens OpenCode. That becomes the Slack agent's working folder, so files and commands start there. Pipa does not prevent OpenCode from accessing other folders if your OpenCode permissions allow it.
Yes. During pipa init, you can choose which Slack users and channels are allowed. Pipa only handles a message when both the user and channel are allowed. An empty list allows any user or channel.
Pipa can use whatever your OpenCode setup can use, including its models, skills, MCP servers, and tools.
Pipa Local saves its Slack tokens on your computer. Keep them private. If someone gets them, revoke them in Slack.