Skip to content
Back to search

manor

MarketplaceWorks with Claude CodeGitHub

Manor's plugins for building and delivering Workspaces from coding agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/manor-os/manor-ai with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/manor-os/manor-ai'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/manor-os--manor-ai/badge.svg)](/listings/manor-os--manor-ai)

HTML

<a href="/listings/manor-os--manor-ai"><img src="/api/listings/manor-os--manor-ai/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/manor-os/manor-ai.git && cd manor-ai
cp .env.example .env
docker compose up --build -d

Open **http://localhost:18080**.

Self-hosted mode seeds a local demo account by default:

demo@manor.local / manor-demo

After signing in, add your model provider keys in Settings. Manor AI is BYOK in self-hosted deployments; provider credentials stay in your deployment.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "manor",
  3. "description": "Manor's plugins for building and delivering Workspaces from coding agents.",
  4. "owner": {
  5. "name": "Manor AI",
  6. "url": "https://github.com/manor-os/manor-os"
  7. },
  8. "plugins": [
  9. {
  10. "name": "manor",
  11. "source": "./plugins/manor",
  12. "description": "Build, version, test and deliver Manor Workspaces for your customers."
  13. }
  14. ]
  15. }
README.md · README · 257 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <img src="./docs-site/static/img/content.png" width="750" alt="Manor AI logo" style="max-width: 100%" />
  3. </p>
  4. <h1 align="center">Manor AI</h1>
  5. <p align="center">
  6. <strong>English</strong> | <a href="README.zh-CN.md">简体中文</a>
  7. </p>
  8. <p align="center">
  9. <strong>Self-hosted AI workspace for governed agents, tasks, tools, and knowledge.</strong>
  10. </p>
  11. <p align="center">
  12. Run agents against team knowledge and scoped tools, require human approval
  13. before sensitive actions, and keep operational data inside infrastructure
  14. you control.
  15. </p>
  16. <p align="center">
  17. <a href="https://github.com/manor-os/manor-ai"><strong>⭐ Star Manor AI</strong></a>
  18. ·
  19. <a href="#5-minute-quickstart"><strong>🚀 Run with Docker Compose</strong></a>
  20. ·
  21. <a href="https://github.com/manor-os/manor-ai/issues/new/choose"><strong>💬 Open an issue</strong></a>
  22. </p>
  23. <p align="center">
  24. <a href="https://manor-os.github.io/docs/manor-ai/quickstart"><strong>5-minute Quickstart</strong></a>
  25. ·
  26. <a href="https://manor-os.github.io/docs/manor-ai/"><strong>Docs</strong></a>
  27. ·
  28. <a href="https://github.com/manor-os/manor-ai"><strong>GitHub</strong></a>
  29. ·
  30. <a href="https://discord.gg/De6fg5Swnw"><strong>Discord</strong></a>
  31. ·
  32. <a href="https://x.com/CalvinLin173676"><strong>Twitter</strong></a>
  33. ·
  34. <a href="https://manorai.xyz/"><strong>Website</strong></a>
  35. </p>
  36. <p align="center">
  37. <a href="LICENSE"><img alt="License" src="https://img.shields.io/badge/license-Sustainable%20Use-lightgrey"></a>
  38. <a href="https://github.com/manor-os/manor-ai/stargazers"><img alt="GitHub stars" src="https://img.shields.io/github/stars/manor-os/manor-ai?style=flat&logo=github"></a>
  39. <a href="https://discord.gg/De6fg5Swnw"><img alt="Discord" src="https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white"></a>
  40. <a href="https://x.com/CalvinLin173676"><img alt="Follow on X" src="https://img.shields.io/badge/X-Follow-000000?logo=x&logoColor=white"></a>
  41. <a href="https://manorai.xyz/"><img alt="Website" src="https://img.shields.io/badge/Website-manorai.xyz-0f766e"></a>
  42. </p>
  43. <div align="center">
  44. <video src="https://github.com/user-attachments/assets/89aac5f8-3fbb-405b-81e0-6522e8df1513" width="900" controls poster="./docs-site/static/img/social-card.png"></video>
  45. </div>
  46. ## Why Manor AI
  47. Most AI products stop at chat. Real teams need an operating layer around AI:
  48. shared context, durable tasks, scoped tools, approvals, audit trails, and a way
  49. to keep sensitive data inside infrastructure they control.
  50. Manor AI is built for that layer: the product surface where model choice,
  51. workspace memory, tasks, permissions, and human review all meet.
  52. ### Own the runtime, not just the chat box
  53. Manor AI brings the core surfaces of an AI workspace into one runtime: chat,
  54. documents, agents, goals, workflows, reports, integrations, settings, and the
  55. infrastructure around them. Self-host the app, database, files, agent runtime,
  56. and integration surfaces; bring your own model keys instead of handing your
  57. workspace to a hosted black box. Model provider keys are configured in your
  58. deployment, and operational data stays inside your infrastructure.
  59. ### Turn prompts into accountable work
  60. Agents operate through goals, tasks, workspace context, tool permissions, and
  61. human approval gates. Important automation leaves durable status, evidence, and
  62. review points instead of disappearing into a one-off chat transcript. Goals
  63. break work into linked execution steps that teams can inspect and improve.
  64. ### Make governance part of the product
  65. Approval gates, scoped tools, audit logs, workspace permissions, and runtime
  66. signals make automation inspectable before it touches critical workflows. Rules
  67. are visible to operators and mapped to enforcement patterns in the runtime.
  68. ## How Manor AI works
  69. Manor AI is organized around a workspace. A workspace is the boundary where
  70. people, agents, documents, tasks, goals, tools, credentials, and governance
  71. rules come together.
  72. ```text
  73. Browser workspace
  74. |
  75. v
  76. React web app
  77. |
  78. v
  79. FastAPI control plane <----> PostgreSQL + pgvector
  80. | | Redis
  81. | | MinIO / JuiceFS
  82. v
  83. Worker runtime
  84. |
  85. +-- Agent task execution
  86. +-- Skills and scoped tools
  87. +-- Sandbox service
  88. +-- Webhooks / OAuth / Nango integrations
  89. +-- Human approval checkpoints
  90. ```
  91. | Concept | What it means in Manor AI |
  92. | --- | --- |
  93. | Workspace | The operating boundary for people, agents, documents, tasks, knowledge, credentials, and audit history. |
  94. | Agent | A reusable AI worker with instructions, model preferences, tool bindings, skills, and governance rules. |
  95. | Goal / task | Durable work objects that turn prompts into trackable execution, evidence, comments, approvals, and status. |
  96. | Knowledge | Uploaded documents and extracted text indexed for workspace retrieval with PostgreSQL and pgvector. |
  97. | Tools / skills | Bounded capabilities and instruction packages that define what an agent can do and how it should do it. |
  98. | HITL governance | Approval and deny policies that pause sensitive actions before agents affect external systems or critical data. |
  99. | Integrations | Webhooks, OAuth/Nango connectors, API keys, and external callbacks for connecting Manor AI to your stack. |
  100. ## Core capabilities
  101. | Capability | What you get |
  102. | --- | --- |
  103. | AI workspace | Chat, goals, tasks, documents, knowledge, reports, agents, and settings in one self-hosted UI. |
  104. | Agent runtime | Tool-calling loop, model routing, skills, workspace context, task execution, and evidence logs. |
  105. | BYOK model access | Provider keys are configured in your deployment; Manor AI does not require a hosted model proxy. |
  106. | Governance | Human approval gates, scoped tools, workspace permissions, runtime signals, and audit-friendly task history. |
  107. | Knowledge and files | Document uploads, generated artifacts, pgvector-backed retrieval, MinIO object storage, and entity filesystem support. |
  108. | Integrations | Webhooks, OAuth provider configuration, optional Nango, API keys, MCP server catalog, and connector surfaces. |
  109. | Operations | Docker Compose stack, health checks, backup guidance, sandbox isolation, configuration docs, and upgrade notes. |
  110. | Extensibility | Add skills, tools, integrations, workers, model providers, and API clients without changing the core workspace model. |
  111. ## 5-minute Quickstart
  112. ```bash
  113. git clone https://github.com/manor-os/manor-ai.git && cd manor-ai
  114. cp .env.example .env
  115. docker compose up --build -d
  116. ```
  117. Open **http://localhost:18080**.
  118. Self-hosted mode seeds a local demo account by default:
  119. ```text
  120. demo@manor.local / manor-demo
  121. ```
  122. After signing in, add your model provider keys in Settings. Manor AI is BYOK in
  123. self-hosted deployments; provider credentials stay in your deployment.
  124. ## First workflow to try
  125. Use the first run to verify the whole system, not just the login page:
  126. 1. Start the Docker Compose stack and sign in with the demo account.
  127. 2. Add a model provider key in Settings.
  128. 3. Open the seeded workspace and inspect goals, tasks, documents, and rules.
  129. 4. Create or run a task so an agent uses workspace context and tools.
  130. 5. Trigger a governed action and confirm it pauses for human approval.
  131. 6. Review the resulting task status, evidence, comments, and audit trail.
  132. ## What ships in the OSS self-hosted stack
  133. | Area | Included |
  134. | --- | --- |
  135. | Workspace app | React + Vite web UI for chat, tasks, agents, knowledge, documents, workflows, reports, and settings. |
  136. | API runtime | FastAPI service with auth, RBAC, audit logging, OpenAPI docs, and workspace APIs. |
  137. | Worker runtime | Celery-backed worker for background jobs, agent execution, task runs, and integration callbacks. |
  138. | Data services | PostgreSQL 16 with pgvector, Redis, MinIO, and optional JuiceFS-backed entity storage. |
  139. | Agent runtime | Tool-calling loop, skills, scoped tools, HITL approvals, task runners, and goal workflows. |
  140. | Sandbox | Isolated execution service for code-producing tools and file-generating workflows. |
  141. | Integrations | Webhooks, OAuth provider configuration, optional Nango, API keys, MCP catalog, and connector surfaces. |
  142. | Collaboration | CRM, Team & Clients, resource permissions and authorized same-instance customer delivery. |
  143. | Blueprints | Portable JSON export/install, simulation and upgrades from a registered published source. |
  144. | Docs and operations | Docusaurus docs, Docker Compose guide, configuration guide, security notes, backup/restore, and upgrade docs. |
  145. The public OSS tree is designed for self-hosted deployments and local
  146. evaluation. Managed hosting, private deployment automation, and commercial
  147. cloud operations are separate from this repository. If you are extending Manor
  148. AI, start from the OSS surfaces above: tools, skills, workers, webhooks,
  149. OpenAPI clients, and deployment configuration.
  150. One operator manages the self-hosted deployment; multiple users and Entities
  151. retain their existing isolation. All AI entry points use your Entity's BYOK
  152. configuration, not platform keys. Chrome/CLI/Remote Coding/mobile clients,
  153. hosted marketplaces and curated commercial product packages are not included.
  154. The existing license restrictions on third-party hosted services still apply.
  155. ## Extend Manor AI
  156. - **Add skills** to teach agents domain-specific workflows and tool usage
  157. boundaries.
  158. - **Bind tools** to agents so each worker has only the capabilities it needs.
  159. - **Connect systems** through webhooks, OAuth provider configuration, Nango, API
  160. keys, and MCP servers.
  161. - **Use the API** through the same FastAPI surface that powers the web app; see
  162. the [API reference](https://manor-os.github.io/docs/manor-ai/api-reference).
  163. - **Customize deployment** with `.env`, Docker Compose profiles, storage,
  164. sandbox settings, and provider credentials.
  165. ## Deploy and operate
  166. Before sharing a deployment with real users:
  167. - Replace default secrets in `.env`.
  168. - Use HTTPS for `APP_URL` and `PUBLIC_BASE_URL`.
  169. - Keep PostgreSQL, Redis, MinIO, and sandbox services on private networks.
  170. - Back up PostgreSQL and object storage together.
  171. - Treat shell/code execution as sensitive and pair it with HITL governance.
  172. - Start with narrow agent tool scopes, then loosen only after workflows are
  173. trusted.
  174. Useful docs:
  175. - [Quickstart](https://manor-os.github.io/docs/manor-ai/quickstart)
  176. - [Configuration guide](https://manor-os.github.io/docs/manor-ai/configuration)
  177. - [Docker Compose](https://manor-os.github.io/docs/manor-ai/docker-compose)
  178. - [Architecture overview](https://manor-os.github.io/docs/manor-ai/architecture)
  179. - [Security](https://manor-os.github.io/docs/manor-ai/security)
  180. - [Backup and restore](https://manor-os.github.io/docs/manor-ai/operations/backup-restore)
  181. - [Upgrades and releases](https://manor-os.github.io/docs/manor-ai/operations/upgrade-release)
  182. ## Contributing
  183. For code changes, local development setup, tests, and style guidance, start
  184. with [CONTRIBUTING.md](CONTRIBUTING.md) and the
  185. [development docs](https://manor-os.github.io/docs/manor-ai/development). Keep
  186. changes focused, add tests for behavior changes, and update documentation when
  187. setup or user-facing behavior changes.
  188. ## Community
  189. - Join the [Discord](https://discord.gg/De6fg5Swnw).
  190. - Follow updates on [Twitter / X](https://x.com/CalvinLin173676).
  191. - Visit the [Manor AI website](https://manorai.xyz/).
  192. - Use GitHub issues for bugs and feature requests.
  193. - Report suspected vulnerabilities privately through [SECURITY.md](SECURITY.md).
  194. ## License
  195. [Sustainable Use License 1.0](LICENSE) -- Copyright (c) 2026 Manor AI.
  196. Manor AI is fair-code: source-available, self-hostable, and extensible under the
  197. Sustainable Use License 1.0. Internal business, personal, and non-commercial use
  198. are permitted. Distribution or provision to others is permitted only free of
  199. charge for non-commercial purposes under this license. Charging for hosted
  200. access or otherwise providing the software commercially requires a separate
  201. written agreement with Manor AI. Keep license and copyright notices intact and
  202. identify modifications. Commercial consulting and support
  203. around a customer's internal deployment are permitted. The Manor AI name and
  204. marks are governed separately by [TRADEMARKS.md](TRADEMARKS.md).
  205. The license text follows
  206. [n8n's published Sustainable Use License 1.0](https://github.com/n8n-io/n8n/blob/master/LICENSE.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.