Each integration has a specific role. Connecting one service does not connect the others or grant access to a project.
Desktop and Platform connections
| Integration | Purpose | Setup |
|---|---|---|
@blockbite/astro |
Island fields, generated types and native page-content validation | Astro integration |
| GitHub | Import a repository, review local changes, receive and send updates | Integrations → GitHub; use your own account |
| OpenRouter | Built-in model chat and supported AI editing | OpenRouter guide |
| ChatGPT / OpenAI | Experimental chat with eligible ChatGPT plan access | OpenAI guide; local demo build only |
| Desktop MCP | Local clients using the open project’s tools | MCP setup and tool reference |
| BlockBite Platform | Team membership, managed project access and shared reviews | Team setup and client setup |
| Stripe | Read agency client invoices and open their original documents | Account owner connects the read-only Stripe App through Platform; create and send invoices in Stripe |
GitHub permissions and branch rules govern repository operations. BlockBite project roles govern managed editor access. Keep both in place for a managed client project.
Provider credentials use their connection’s storage: Desktop AI and GitHub connections stay on the device; the Stripe connection is owned by Platform. Project files are not the place to store service keys.
Local preview sharing
ngrok live preview sharing is unavailable in the current Desktop build. Adding an ngrok account or token does not enable it.
For feedback, an authorized agency member can use Project → Cloud → Published review to prepare and publish selected pages as a read-only Wireframe, then invite reviewers from Platform’s Sharing page. Follow client review setup. The review shows one published version with its approved images and fonts; it does not run the Astro website or stream local preview changes.
CMS and deployment
Native Astro sites use their project’s normal build and deployment workflow.
Adding @blockbite/astro does not select a host or publish the site.
WordPress export/import and Twig delivery remain legacy code outside active native-Astro development. The EmDash package interface is a bounded offline pilot; its Desktop integration is coming soon. Neither is a general-purpose importer for arbitrary Astro projects.
Public release availability is tracked on the download page and in documentation status.