How superioroil4373/unboxit works
unBoxit routes Box links to local macOS files through two user-facing entry points: a Finder button on Box.com and actionable buttons in Slack. Both produce a boxlocal:// URL handled locally; the handler resolves the Box Drive path and opens it in Finder. The Slack bot also retrieves Box metadata to build a named local path and unfurl. The browser and bot implementations are excerpted; handler behavior and cross-component links are based on the README, so details beyond its description are not inferred.
Main entry points: handler.sh Path handler · app.js Link processor · content.js Finder button
Components 12
Browser extension
- Finder button
browser-extension/content.js
macOS handler
- Local URL protocol
macos-handler/handler.sh - Path handler
macos-handler/handler.sh
Slack companion
- Link processor
slackbot/app.js - Metadata lookup
slackbot/app.js - Unfurl and actions
slackbot/app.js
External services
- Finder
- Box Drive
- Slack platform
- Box API
Other components
- Box user
- Slack user
Connections 13
- Box user → Finder button: clicks
README.md - Finder button → Local URL protocol: opens URL
browser-extension/content.js - Local URL protocol → Path handler: dispatches
README.md - Path handler → Box Drive: resolves path
README.md - Path handler → Finder: opens or reveals
README.md - Slack user → Slack platform: shares link
README.md - Slack platform → Link processor: delivers message
slackbot/app.js - Link processor → Metadata lookup: looks up item
slackbot/app.js - Metadata lookup → Box API: fetches metadata
slackbot/app.js - Link processor → Unfurl and actions: builds response
slackbot/app.js - Unfurl and actions → Slack platform: posts buttons
slackbot/app.js - Slack platform → Slack user: shows actions
README.md - Slack user → Local URL protocol: opens action URL
README.md