From 83ec3cd69ac25defc6ee68cb90781a3245e0b7d2 Mon Sep 17 00:00:00 2001 From: AsafGolombek Date: Thu, 12 Nov 2026 20:48:55 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20ecosystem=20map=20=E2=80=94=20current?= =?UTF-8?q?=20repositories,=20retired=20scaffolds,=20derived=20counts?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Lists nimbus-mcp, nimbus-mcp-servers and nimbus-trust, retires the five scaffold repositories with where each one's work went, derives the connector count from the gateway, and links the recorded direction as planned. Co-Authored-By: Claude Fable 5.2 Claude-Session: https://claude.ai/code/session_01JmSjrFKyPDdZkezWFQzqTs --- ECOSYSTEM.md | 36 +++++++++++++++++++++++++----------- profile/README.md | 18 +++++++++++------- 2 files changed, 36 insertions(+), 18 deletions(-) diff --git a/ECOSYSTEM.md b/ECOSYSTEM.md index 39742f1..8cbbf17 100644 --- a/ECOSYSTEM.md +++ b/ECOSYSTEM.md @@ -8,6 +8,11 @@ That single constraint shapes the whole ecosystem: there is one gateway that owns your data, one contract that everything speaks, and a set of surfaces that reach you where you already work. +Where this is heading is recorded in the gateway's roadmap, +[§ Direction](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md#direction): +Nimbus as the trust layer between AI agents and engineering systems. That is a +planned direction; this document describes what exists. + ## The shape ```text @@ -17,8 +22,8 @@ reach you where you already work. ──────── │ ┌──────────────────────┐ │ ────────── VS Code ─────┐ │ │ Nimbus Gateway │ │ ┌── Google, Microsoft web clipper ────┼──►│ │ · private SQLite │──►│──┼── GitHub, GitLab, Jira - Raycast ─────┤ │ │ · agent engine │ │ ├── Slack, Notion, … - CLI / TUI ─────┘ │ │ · HITL consent gate │ │ └── ~80 services, MCP only + MCP clients ────┤ │ │ · agent engine │ │ ├── Slack, Notion, … + CLI / TUI ─────┘ │ │ · HITL consent gate │ │ └── about 95 services, MCP only │ └──────────────────────┘ │ │ JSON-RPC 2.0 IPC │ └──────────────────────────────┘ @@ -50,7 +55,7 @@ arrow pointing in the only direction that works. | Repo | Role | License | | --- | --- | --- | | [`Nimbus`](https://github.com/nimbus-agent/Nimbus) | The gateway daemon, connectors, index, agents and the JSON-RPC surface | AGPL-3.0 | -| [`nimbus-sdk`](https://github.com/nimbus-agent/nimbus-sdk) | **The contract.** Dependency-free TypeScript types for authoring connectors and extensions | MIT | +| [`nimbus-sdk`](https://github.com/nimbus-agent/nimbus-sdk) | **The contract.** A language-neutral authoring contract for connectors and extensions, with TypeScript, Python and Go bindings | MIT | | [`nimbus-client`](https://github.com/nimbus-agent/nimbus-client) | Typed JSON-RPC IPC client — the only supported path from a client to the gateway | MIT | ### Surfaces @@ -61,14 +66,11 @@ Where the capability reaches a human. | --- | --- | | [`nimbus-vscode`](https://github.com/nimbus-agent/nimbus-vscode) | VS Code / Open VSX extension — ask, search, chat participant, SCM tooling | | [`nimbus-web-clipper`](https://github.com/nimbus-agent/nimbus-web-clipper) | Chrome + Firefox MV3 extension, over the gateway's paired HTTP surface | -| [`nimbus-raycast`](https://github.com/nimbus-agent/nimbus-raycast) | Raycast quick-ask (scaffold) | -| [`nimbus-statuspage`](https://github.com/nimbus-agent/nimbus-statuspage) | On-call and status pages from indexed incidents, alerts and DORA metrics (scaffold) | -| [`nimbus-postmortem`](https://github.com/nimbus-agent/nimbus-postmortem) | Incident postmortem drafts from indexed incidents, deploys and implicated changes (scaffold) | +| [`nimbus-mcp`](https://github.com/nimbus-agent/nimbus-mcp) | Launcher for the Nimbus MCP server: gives any MCP client your local index and the built-in agents | The CLI and TUI ship inside the `Nimbus` repo rather than separately. -Surfaces marked *(scaffold)* hold a vision README and a build prompt but no -implementation yet. They are sequenced in the gateway's +Which surface comes next is decided in the gateway's [roadmap](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md), not here — this document says what exists, not what happens next. @@ -77,9 +79,7 @@ here — this document says what exists, not what happens next. | Repo | Role | | --- | --- | | `create-nimbus-connector` | Scaffolding generator for first-party-style MCP connectors | -| `nimbus-mcp-servers` | Standalone MCP servers derived from Nimbus connectors, usable by any MCP client | -| `nimbus-connector-registry` | Signed index and publisher-key directory for the connector marketplace | -| `nimbus-recipes` | Community hub for shareable, signed recipes (`.nimbus-recipe.yaml`) | +| [`nimbus-mcp-servers`](https://github.com/nimbus-agent/nimbus-mcp-servers) | The first-party connectors, published as one package; each also runs standalone for any MCP client | | [`awesome-nimbus`](https://github.com/nimbus-agent/awesome-nimbus) | Curated list of connectors, recipes, extensions and resources | ### Distribution @@ -99,6 +99,20 @@ Windows also ships through winget; installers are built in the `Nimbus` repo. | [`.github`](https://github.com/nimbus-agent/.github) | Org profile, shared community-health defaults, CLA, this document | | [`nimbus-security`](https://github.com/nimbus-agent/nimbus-security) | Public security model, invariant catalogue, vulnerability disclosure | | [`nimbus-benchmarks`](https://github.com/nimbus-agent/nimbus-benchmarks) | Public performance benchmarks and trend dashboards | +| [`nimbus-trust`](https://github.com/nimbus-agent/nimbus-trust) | The signed trust feed every install applies: key revocations, takedowns and verified publishers | + +### Retired + +Five repositories held only a vision and a build prompt, and were retired on +2026-11-12. Each row says where its work went. + +| Repo | What happened | +| --- | --- | +| `nimbus-statuspage` | Became a gateway row: the status page draft, [Phase 17](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md#phase-17--the-on-call-copilot) | +| `nimbus-postmortem` | Became the gateway's post-mortem rows, [Phase 10](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md#phase-10--the-autonomous-agent) and Phase 17 | +| `nimbus-connector-registry` | The registry shipped inside the gateway instead, [Phase 9.5](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md#phase-95--marketplace-registry) | +| `nimbus-raycast` | Not planned; see [Rejected Directions](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md#rejected-directions) | +| `nimbus-recipes` | Not planned as a gallery; recipes remain a share kind in the gateway. See [Rejected Directions](https://github.com/nimbus-agent/Nimbus/blob/main/docs/roadmap.md#rejected-directions) | ## Where planning lives diff --git a/profile/README.md b/profile/README.md index 5d18a3e..8a24ef4 100644 --- a/profile/README.md +++ b/profile/README.md @@ -2,7 +2,7 @@ **A local-first AI agent framework.** Your machine is the source of truth; the cloud is just a connector. -Nimbus is a headless agent runtime that builds a private, on-device index of your work across ~80 cloud services, then executes multi-step agentic workflows on your behalf — without your data ever leaving your machine unless *you* approve it. +Nimbus is a headless agent runtime that builds a private, on-device index of your work across about 95 cloud services, then executes multi-step agentic workflows on your behalf — without your data ever leaving your machine unless *you* approve it. --- @@ -16,11 +16,11 @@ Nimbus is a headless agent runtime that builds a private, on-device index of you ## What it connects to -A growing roster of ~80 first-party connectors across Google, Microsoft 365, GitHub, GitLab, Slack, Jira, and Notion — plus observability, CI/CD, security & quality, feature-flags, GitOps, data & BI, deployment, finance, and support tools. Optional local-filesystem indexing rounds it out. +A growing roster of about 95 first-party connectors across Google, Microsoft 365, GitHub, GitLab, Slack, Jira, and Notion — plus observability, CI/CD, security & quality, feature-flags, GitOps, data & BI, deployment, finance, and support tools. Optional local-filesystem indexing rounds it out. ## How you talk to it -Clients — the CLI, a [VS Code extension](https://github.com/nimbus-agent/nimbus-vscode), and a Tauri 2.0 desktop app — talk to the headless Gateway over local JSON-RPC 2.0 IPC. A [browser web clipper](https://github.com/nimbus-agent/nimbus-web-clipper) (Chrome + Firefox) saves what you read straight into your index over the gateway's paired, local HTTP surface. Install the gateway + CLI via Homebrew, Scoop, or native installers (`.msi` / `.pkg` / `.rpm`). +Clients — the CLI, a [VS Code extension](https://github.com/nimbus-agent/nimbus-vscode), and a Tauri 2.0 desktop app (built, not yet released) — talk to the headless Gateway over local JSON-RPC 2.0 IPC. A [browser web clipper](https://github.com/nimbus-agent/nimbus-web-clipper) (Chrome + Firefox) saves what you read straight into your index over the gateway's paired, local HTTP surface. Any MCP client, a coding agent for example, reaches your index and the built-in agents through the [MCP launcher](https://github.com/nimbus-agent/nimbus-mcp). Install the gateway + CLI via Homebrew, Scoop, or native installers (`.msi` / `.pkg` / `.rpm`). ```bash # Homebrew (macOS / Linux) @@ -37,16 +37,20 @@ Local inference is supported through Ollama, so `nimbus ask` can run entirely of | Repo | What it is | | --- | --- | -| [**Nimbus**](https://github.com/nimbus-agent/Nimbus) | The monorepo — Gateway, CLI, desktop UI, and first-party MCP connectors | +| [**Nimbus**](https://github.com/nimbus-agent/Nimbus) | The gateway — Gateway, CLI and desktop UI; it bundles the first-party connectors | +| [**nimbus-mcp-servers**](https://github.com/nimbus-agent/nimbus-mcp-servers) | `@nimbus-dev/connectors` — the first-party MCP connectors in one package; each also runs standalone for any MCP client | +| [**nimbus-mcp**](https://github.com/nimbus-agent/nimbus-mcp) | `@nimbus-dev/mcp` — launcher for the Nimbus MCP server, so any MCP client reaches your index and agents | | [**nimbus-sdk**](https://github.com/nimbus-agent/nimbus-sdk) | `@nimbus-dev/sdk` — MIT, dependency-free authoring contract for MCP connectors & extensions (published to npm) | | [**nimbus-client**](https://github.com/nimbus-agent/nimbus-client) | `@nimbus-dev/client` — MIT typed JSON-RPC 2.0 IPC client for the gateway, used by the CLI & extensions (published to npm) | | [**nimbus-vscode**](https://github.com/nimbus-agent/nimbus-vscode) | VS Code / Open VSX extension — ask + search your index from the editor | -| [**nimbus-web-clipper**](https://github.com/nimbus-agent/nimbus-web-clipper) | Chrome + Firefox (MV3) browser extension — clip articles & selections into your index | +| [**nimbus-web-clipper**](https://github.com/nimbus-agent/nimbus-web-clipper) | Chrome + Firefox (MV3) browser extension — recognises the page you are on and runs the agents against it; also clips articles & selections into your index | +| [**create-nimbus-connector**](https://github.com/nimbus-agent/create-nimbus-connector) | Scaffolding generator for first-party-style MCP connectors | | [**homebrew-tap**](https://github.com/nimbus-agent/homebrew-tap) | Homebrew distribution channel | | [**scoop-bucket**](https://github.com/nimbus-agent/scoop-bucket) | Scoop distribution channel | | [**linux-repo**](https://github.com/nimbus-agent/linux-repo) | Linux (apt / yum) package distribution channel | | [**awesome-nimbus**](https://github.com/nimbus-agent/awesome-nimbus) | Curated connectors, recipes, extensions & community resources | -| [**nimbus-security**](https://github.com/nimbus-agent/nimbus-security) | Security model, invariant catalogue & vulnerability disclosure | +| [**nimbus-security**](https://github.com/nimbus-agent/nimbus-security) | Security model & vulnerability disclosure | +| [**nimbus-trust**](https://github.com/nimbus-agent/nimbus-trust) | The signed trust feed every install applies: key revocations, takedowns & verified publishers | | [**nimbus-benchmarks**](https://github.com/nimbus-agent/nimbus-benchmarks) | Public performance benchmarks & trend dashboards | ## Architecture at a glance @@ -59,7 +63,7 @@ Local inference is supported through Ollama, so `nimbus ask` can run entirely of ## Security -Security is enforced as code, not convention: a numbered set of **security invariants**, each with a production wiring site, a docs entry, and an enforcement test that all land in the same commit. Secret scanning with push protection, Dependabot, SHA-pinned GitHub Actions, and protected release branches & tags back the supply chain. +Security is enforced as code, not convention: a numbered set of **security invariants**, each with a production wiring site, a docs entry, and an enforcement test that all land in the same commit. Secret scanning with push protection, Dependabot security alerts, SHA-pinned GitHub Actions, and protected release branches & tags back the supply chain. Found something? Please report it responsibly via a private security advisory on the [Nimbus repo](https://github.com/nimbus-agent/Nimbus/security/advisories).