Paperclip plugin: bidirectional GitHub Issues sync
TypeScript
30
3 commits
updated Mar 20, 2026
Bidirectional GitHub Issues sync for Paperclip.
This is the first external Paperclip plugin built as a standalone npm package, created to validate the plugin developer experience.
repo scope (or fine-grained token with Issues read/write)# From the Paperclip CLI
pnpm paperclipai plugin install paperclip-plugin-github-issues
Or for development:
git clone https://github.com/mvanhorn/paperclip-plugin-github-issues.git
cd paperclip-plugin-github-issues
npm install
npm run build
After installation, configure the plugin in Paperclip Settings > GitHub Issues Sync:
owner/repo for agent tool searchesFor real-time sync, configure a webhook on your GitHub repository:
https://your-paperclip-instance/api/plugins/paperclip-plugin-github-issues/webhooks/github-eventsapplication/jsonAgents in Paperclip can use these tools during runs:
src/
manifest.ts # Plugin manifest (capabilities, tools, webhooks, UI slots)
worker.ts # Plugin worker (event handlers, sync logic, tool registration)
constants.ts # Shared constants
github.ts # GitHub REST API client
sync.ts # Sync state management and bidirectional logic
index.ts # Package exports
Built with the Paperclip Plugin SDK (@paperclipai/plugin-sdk).
This plugin was built ahead of the plugin runtime landing on master (PR #821). It implements the full SDK contract based on the plugin spec and example plugins. Testing against a live Paperclip instance will happen once the plugin runtime ships.
The githubTokenRef field now requires a secret UUID rather than a raw token string. If you configured this plugin before v0.1.1 by pasting a raw GitHub personal access token directly into the field, you must re-configure:
Plugins that were already storing a secret UUID (the intended usage) are unaffected.
MIT
3 commits
TypeScript
100.0%
Paperclip plugin: bidirectional GitHub Issues sync
TypeScript
30
3 commits
updated Mar 20, 2026
Bidirectional GitHub Issues sync for Paperclip.
This is the first external Paperclip plugin built as a standalone npm package, created to validate the plugin developer experience.
repo scope (or fine-grained token with Issues read/write)# From the Paperclip CLI
pnpm paperclipai plugin install paperclip-plugin-github-issues
Or for development:
git clone https://github.com/mvanhorn/paperclip-plugin-github-issues.git
cd paperclip-plugin-github-issues
npm install
npm run build
After installation, configure the plugin in Paperclip Settings > GitHub Issues Sync:
owner/repo for agent tool searchesFor real-time sync, configure a webhook on your GitHub repository:
https://your-paperclip-instance/api/plugins/paperclip-plugin-github-issues/webhooks/github-eventsapplication/jsonAgents in Paperclip can use these tools during runs:
src/
manifest.ts # Plugin manifest (capabilities, tools, webhooks, UI slots)
worker.ts # Plugin worker (event handlers, sync logic, tool registration)
constants.ts # Shared constants
github.ts # GitHub REST API client
sync.ts # Sync state management and bidirectional logic
index.ts # Package exports
Built with the Paperclip Plugin SDK (@paperclipai/plugin-sdk).
This plugin was built ahead of the plugin runtime landing on master (PR #821). It implements the full SDK contract based on the plugin spec and example plugins. Testing against a live Paperclip instance will happen once the plugin runtime ships.
The githubTokenRef field now requires a secret UUID rather than a raw token string. If you configured this plugin before v0.1.1 by pasting a raw GitHub personal access token directly into the field, you must re-configure:
Plugins that were already storing a secret UUID (the intended usage) are unaffected.
MIT
3 commits
TypeScript
100.0%