Clear docs for Harbor Node, the API surfaces, cloud flows, the public sites, and the connector catalog already shipping in the repo.

Build the operating layer that lets AI agents access real systems safely.

Ship a believable Harbor product that proves the local-first trust model and feels installable.

Harbor now has three distinct product layers. They should stay separate in both code and product scope.

An agent with full access to the same trust boundary as the secrets can often still abuse them, even if the raw values are encrypted at rest.

Harbor should feel like an appliance:

Harbor APIs should be typed, boring, and explicit.

These ports and services reflect the current Harbor stack. Some public/static surfaces are served as generated sites rather than long-running app servers, so the serving port can vary by environment.

Define what authentication and credential handling **is** and **is not** part of Harbor.

This planning document describes what is now Harbor's Action Model.

Use Harbor Node as a local capability gateway for agents and scripts.

Create Harbor integrations that are:

Lock the scope for the first real member-account milestone so signup and profile work do not sprawl into billing, production email, or broad OAuth before the foundations are stable.

This is a curated Harbor-target backlog, not a literal universal industry leaderboard.

This file turns the roadmap into a practical sequence of execution.

This roadmap answers a different question than it did earlier in the project:

Hub now serves Dock entries from a local SQLite catalog instead of reading runtime data directly from one large TypeScript array.

**Breakwater Ninja**

Breakwater Ninja

Free, self-hosted, local-first.

Add **Node-local agent tokens** so Harbor Node can require a real credential for network action calls and attach those calls to a stable per-agent identity.

This document turns Harbor's generic go-live plan into a concrete prelaunch deployment for:

This refactor split the Harbor Cloud Admin app into smaller modules without intentionally changing user-facing behavior or the generated `dist/site` output shape.

This document is the practical launch checklist for Harbor.

Harbor Node can sign async execution callbacks with an HMAC SHA-256 header pair:

Reduce agent token usage by letting Harbor return smaller action responses and, on Business nodes, persist filtered response artifacts for later readback.

We are adding a new Harbor capability: Harbor-managed MCP launcher.

This refactor split the Harbor NodeUI monolith into an app shell, page-level feature modules, and shared helpers without intentionally changing user-facing behavior.

This document inventories what Harbor already has across the monorepo, what is still weak, and what is most worth doing next while staying inside the current mission:

This pass refactored the static/browser-facing apps around clearer entrypoints and feature ownership without changing the generated site behavior:

This pass focused on high-value hardening that could land without redesigning Harbor's auth model.

Published from the repo docs set and surfaced in the Harbor documentation frontend.

You are the lead product systems engineer for Breakwater / Harbor Protocol.

This is the Harbor reference integration for the Airtable Web API.

This is the Harbor reference integration for the Asana API.

This is the Harbor reference integration for the BigQuery API.

This is the Harbor reference integration for the Box API.

This is the Harbor reference integration for the Calendly API.

This is the reference integration for Harbor `http_api` Action Model authoring for Cloudflare.

This is the reference integration for Harbor `http_api` Action Model authoring for Cohere.

This is the Harbor reference integration for the Confluence Cloud REST API.

This is the reference integration for Harbor `http_api` Action Model authoring for DigitalOcean.

This is the Harbor reference integration for the Discord Bot API.

This is the Harbor reference integration for the Dropbox API.

This is the reference integration for Harbor `http_api` Action Model authoring for Figma.

This is the Harbor reference integration for the GitHub REST API and Harbor's Action Model.

This is the Harbor reference integration for the GitLab REST API.

This is the reference integration for Harbor `http_api` Action Model authoring.

This is the reference integration for the Google Calendar API and Harbor's Action Model.

This is the Harbor reference integration for the Google Drive API.

This is the reference integration for the Google Sheets API and Harbor's Action Model.

This is the Harbor reference integration for the HubSpot CRM API.

This is the Harbor reference integration for the Jenkins Remote API.

This is the Harbor reference integration for the Jira Cloud REST API.

This is the Harbor reference integration for Microsoft Graph Calendar.

This is the Harbor reference integration for Microsoft Graph Mail.

This is the reference integration for Harbor `http_api` Action Model authoring for Mistral.

This is the reference integration for Harbor `http_api` Action Model authoring for Netlify.

This is the reference integration for Harbor `http_api` Action Model authoring for OpenAI.

This is the Harbor reference integration for the Salesforce REST API.

This is the Harbor reference integration for the Sentry REST API.

This is the Harbor reference integration for the Slack Web API.

This is the reference integration for Harbor `http_api` Action Model authoring for Tavily.

This is the Harbor reference integration for the Todoist REST API.

This is the reference integration for Harbor `http_api` Action Model authoring for Vercel.

This is the Harbor reference integration for the Zendesk Ticketing API.

This is the Harbor reference integration for the Zoom API.