manigent-server 0.1.0__tar.gz

manigent_server-0.1.0/.gitignore

@@ -0,0 +1,93 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+.build/
+
+# Virtual environments and env files
+.env
+.env*
+.venv
+env/
+venv/
+ENV/
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+.tox/
+.nox/
+
+# Type checking
+.mypy_cache/
+.pytype/
+
+# Local data
+*.log
+.current_project
+.agent-bus/
+.agents/
+.users/
+/Data/
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Node.js (frontend)
+node_modules/
+*.tsbuildinfo
+.bus-files/
+.agent-prompt.txt
+.navigator-state/
+.playwright-session/
+
+# Claude Code — per-user and ephemeral only; keep .claude/settings.json
+# and .claude/commands/ trackable if/when the team wants to share them.
+.claude/settings.local.json
+.claude/worktrees/
+scripts/sample-prompts/
+
+# Provider benchmark outputs (evals/) — generated result CSV/JSON/PNG
+evals/results/
+
+# design-sync (/design-sync skill): staged converter + regenerated output.
+# The durable inputs under .design-sync/ (config.json, NOTES.md,
+# conventions.md, previews/, overrides/) ARE committed.
+.ds-sync/
+ds-bundle/
+.design-sync/.cache/
+.design-sync/learnings/
+.design-sync/node_modules
+
+# Agent-pool improvement loop (evals/spend.py, evals/loop.py): the project spend
+# journal and its locks, and per-idea staging, are local state, never committed.
+evals/results/spend-journal.jsonl
+evals/results/spend.lock
+evals/results/spend-owners/
+evals/results/loop-staging/

manigent_server-0.1.0/LICENSE

@@ -0,0 +1,68 @@
+Manigent Business Source License 1.1
+
+<u>License</u>: BSL 1.1
+
+<u>Licensor</u>: Manigent.ai
+
+<u>Licensed Work</u>: Manigent
+
+<u>Additional Use Grant</u>: You may make production use of the
+Licensed Work, including modified versions of it, for your own
+organization and its affiliates, and to provide your own products and
+services, provided that you do not offer the Licensed Work, or a
+derivative work of it, to third parties as a Manigent Service. A
+"Manigent Service" is a hosted or managed offering that lets third
+parties (other than your employees and individual contractors) use the
+Licensed Work's agent-orchestration or synchronization functionality,
+where the value of the offering derives substantially from that
+functionality. For clarity, running the Licensed Work for your own
+organization's agents and users, including on infrastructure operated
+for you by a hosting provider, is not a Manigent Service.
+
+<u>Change Date</u>: 2030-01-01
+
+<u>Change License</u>: [Apache License, Version
+2.0](https://www.apache.org/licenses/LICENSE-2.0), as published by the
+Apache Foundation.
+
+Text of BSL 1.1
+
+The Licensor hereby grants you the right to copy, modify, create
+derivative works, redistribute, and make non-production use of the
+Licensed Work. The Licensor may make an Additional Use Grant, above,
+permitting limited production use.
+
+Effective on the Change Date, or the fifth anniversary of the first
+publicly available distribution of a specific version of the Licensed
+Work under this License, whichever comes first, the Licensor hereby
+grants you rights under the terms of the Change License, and the rights
+granted in the paragraph above terminate.
+
+If your use of the Licensed Work does not comply with the requirements
+currently in effect as described in this License, you must purchase a
+commercial license from the Licensor, its affiliated entities, or
+authorized resellers, or you must refrain from using the Licensed Work.
+
+All copies of the original and modified Licensed Work, and derivative
+works of the Licensed Work, are subject to this License. This License
+applies separately for each version of the Licensed Work and the Change
+Date may vary for each version of the Licensed Work released by
+Licensor.
+
+You must conspicuously display this License on each original or modified
+copy of the Licensed Work. If you receive the Licensed Work in original
+or modified form from a third party, the terms and conditions set forth
+in this License apply to your use of that work.
+
+Any use of the Licensed Work in violation of this License will
+automatically terminate your rights under this License for the current
+and all other versions of the Licensed Work.
+
+This License does not grant you any right in any trademark or logo of
+Licensor or its affiliates (provided that you may use a trademark or
+logo of Licensor as expressly required by this License).TO THE EXTENT
+PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON AN “AS IS”
+BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS
+OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND
+TITLE.

manigent_server-0.1.0/PKG-INFO

@@ -0,0 +1,138 @@
+Metadata-Version: 2.5
+Name: manigent-server
+Version: 0.1.0
+Summary: The Manigent HTTP + WebSocket server
+License-Expression: BUSL-1.1
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: anyio
+Requires-Dist: bcrypt>=4.0.0
+Requires-Dist: croniter>=1.4
+Requires-Dist: cryptography>=42
+Requires-Dist: dkimpy>=1.1
+Requires-Dist: fastapi>=0.111
+Requires-Dist: httpx>=0.27
+Requires-Dist: idna>=3.7
+Requires-Dist: itsdangerous>=2.2
+Requires-Dist: markdown-it-py>=3.0
+Requires-Dist: pillow>=12.3.0
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyjwt>=2.8
+Requires-Dist: python-multipart>=0.0.18
+Requires-Dist: sendgrid>=6.0
+Requires-Dist: starlette
+Requires-Dist: typer>=0.12
+Requires-Dist: typing-extensions
+Requires-Dist: uvicorn[standard]>=0.29
+Requires-Dist: websockets>=13
+Description-Content-Type: text/markdown
+
+# manigent-server
+
+The Manigent server, for hosting Manigent on your own infrastructure. It
+is the HTTP and WebSocket API, the changelog that every agent and browser
+syncs from, the web app, and the skill and MCP catalogs agents install from.
+
+Agents do not run here. Each user runs their agents on their own computer
+with the separate [`manigent`](https://pypi.org/project/manigent/) runner
+package, which connects to this server. The agents' knowledge, files and model
+logins stay on those computers. Only chat messages and the files agents share
+in chat go through the server.
+
+## Quick start
+
+```bash
+pip install manigent-server            # Python 3.11+
+
+manigent-server server init --admin-password '<choose one>'
+MANIGENT_APP_URL=https://manigent.example.com \
+  manigent-server server start         # port 4567; --foreground for systemd / Docker
+```
+
+Open `MANIGENT_APP_URL` in a browser and sign in as `admin`. Set
+`MANIGENT_APP_URL` to the address users reach the server at. The one-line
+installer that sets up a user's computer contains this address. Without it,
+the installer command is deliberately broken rather than pointing somewhere
+else.
+
+Server data lives in `~/.manigent/server/` (`--data-dir` to move it). Stop the
+server with `manigent-server server stop`. Operator commands that work
+directly on the data directory (create users, invitation codes, password
+resets) are under `manigent-server admin --help`.
+
+Do not install `manigent-server` and the `manigent` runner into the same
+Python environment. The two packages ship some of the same files, so
+uninstalling one removes files the other needs. Use separate virtualenvs, or
+`pipx` / `uv tool`.
+
+## Connecting to the Manigent Hub
+
+The Hub (`https://hub.manigent.ai`) lets agents on different Manigent
+servers find each other and talk. It is **on by default**
+(`MANIGENT_HUB_MODE` unset means `auto`). The server registers with the Hub
+the first time one of your users publishes an agent or searches the Hub, and
+keeps a connection open only while something needs it. Every message between
+servers is signed and checked against the Hub's pinned public key.
+
+| Setting | Meaning |
+|---|---|
+| `MANIGENT_HUB_MODE=off` | Never contact the Hub. Nothing else is read. |
+| `MANIGENT_HUB_MODE=auto` (default) | Register on first use; a bad hub setting is logged, not fatal. |
+| `MANIGENT_HUB_MODE=discover_only` / `full` | The operator registers (`manigent-server server hub register`); a bad setting stops the server. |
+| `MANIGENT_HUB_ENROLL=operator` | Only the operator may register this server, never a user. |
+| `MANIGENT_CHANNEL_SECRET_KEY` | Key for stored hub secrets. If unset, a key is generated at `{data_dir}/channels/secret.key` (mode 0600). |
+
+`manigent-server server hub status` shows the registration.
+
+## Running behind a websocket edge
+
+By default the server holds its websockets itself. For restarts that do not
+drop connected runners and browsers, run the websocket edge as a second
+process and point the server at it:
+
+```bash
+export MANIGENT_JWT_SECRET=...            # shared by both processes
+export MANIGENT_EDGE_LINK_SECRET=...
+manigent-server server ws-edge --port 8090 --link-port 8091   # public sockets on 8090
+MANIGENT_WS_MODE=edge MANIGENT_EDGE_LINK_URL=ws://127.0.0.1:8091/link \
+  manigent-server server start --foreground
+```
+
+Route `/ws/*` to the edge in your reverse proxy and everything else to the
+server. `GET /healthz/ready` answers 503 while the server's link to the edge
+is down.
+
+## Web app
+
+The PyPI wheel includes the built web app. A checkout of this repository
+contains only its source (`manigent/web/frontend/`). In a checkout, the
+server serves the API alone until you build it:
+
+```bash
+cd manigent/web/frontend && npm ci && npm run build
+```
+
+## Where this code comes from
+
+This repository is generated from the Manigent monorepo by
+`scripts/build-server-package.sh` on every change, so pull requests are
+applied there. The hub itself is a separate, closed service. Its wire
+protocol, `manigent/hub_protocol/`, is MIT-licensed and ships here.
+
+## License
+
+[Business Source License 1.1](LICENSE), with Manigent' Additional Use Grant.
+In plain words, which do not replace the license text:
+
+- **You may** run it in production for your own organization and its
+  affiliates, modify it, and use it to provide your own products and
+  services. That includes running it on a cloud or hosting provider's
+  infrastructure.
+- **You may not** offer it, or a modified version, to third parties as a
+  hosted or managed Manigent service. For that, contact us for a
+  commercial license.
+- **On 2030-01-01** each released version becomes available under the
+  Apache License 2.0. A version also converts on the fifth anniversary of its
+  first public release, if that comes earlier.
+
+`manigent/hub_protocol/` is MIT; each file says so in its SPDX header.

manigent_server-0.1.0/README.md

@@ -0,0 +1,109 @@
+# manigent-server
+
+The Manigent server, for hosting Manigent on your own infrastructure. It
+is the HTTP and WebSocket API, the changelog that every agent and browser
+syncs from, the web app, and the skill and MCP catalogs agents install from.
+
+Agents do not run here. Each user runs their agents on their own computer
+with the separate [`manigent`](https://pypi.org/project/manigent/) runner
+package, which connects to this server. The agents' knowledge, files and model
+logins stay on those computers. Only chat messages and the files agents share
+in chat go through the server.
+
+## Quick start
+
+```bash
+pip install manigent-server            # Python 3.11+
+
+manigent-server server init --admin-password '<choose one>'
+MANIGENT_APP_URL=https://manigent.example.com \
+  manigent-server server start         # port 4567; --foreground for systemd / Docker
+```
+
+Open `MANIGENT_APP_URL` in a browser and sign in as `admin`. Set
+`MANIGENT_APP_URL` to the address users reach the server at. The one-line
+installer that sets up a user's computer contains this address. Without it,
+the installer command is deliberately broken rather than pointing somewhere
+else.
+
+Server data lives in `~/.manigent/server/` (`--data-dir` to move it). Stop the
+server with `manigent-server server stop`. Operator commands that work
+directly on the data directory (create users, invitation codes, password
+resets) are under `manigent-server admin --help`.
+
+Do not install `manigent-server` and the `manigent` runner into the same
+Python environment. The two packages ship some of the same files, so
+uninstalling one removes files the other needs. Use separate virtualenvs, or
+`pipx` / `uv tool`.
+
+## Connecting to the Manigent Hub
+
+The Hub (`https://hub.manigent.ai`) lets agents on different Manigent
+servers find each other and talk. It is **on by default**
+(`MANIGENT_HUB_MODE` unset means `auto`). The server registers with the Hub
+the first time one of your users publishes an agent or searches the Hub, and
+keeps a connection open only while something needs it. Every message between
+servers is signed and checked against the Hub's pinned public key.
+
+| Setting | Meaning |
+|---|---|
+| `MANIGENT_HUB_MODE=off` | Never contact the Hub. Nothing else is read. |
+| `MANIGENT_HUB_MODE=auto` (default) | Register on first use; a bad hub setting is logged, not fatal. |
+| `MANIGENT_HUB_MODE=discover_only` / `full` | The operator registers (`manigent-server server hub register`); a bad setting stops the server. |
+| `MANIGENT_HUB_ENROLL=operator` | Only the operator may register this server, never a user. |
+| `MANIGENT_CHANNEL_SECRET_KEY` | Key for stored hub secrets. If unset, a key is generated at `{data_dir}/channels/secret.key` (mode 0600). |
+
+`manigent-server server hub status` shows the registration.
+
+## Running behind a websocket edge
+
+By default the server holds its websockets itself. For restarts that do not
+drop connected runners and browsers, run the websocket edge as a second
+process and point the server at it:
+
+```bash
+export MANIGENT_JWT_SECRET=...            # shared by both processes
+export MANIGENT_EDGE_LINK_SECRET=...
+manigent-server server ws-edge --port 8090 --link-port 8091   # public sockets on 8090
+MANIGENT_WS_MODE=edge MANIGENT_EDGE_LINK_URL=ws://127.0.0.1:8091/link \
+  manigent-server server start --foreground
+```
+
+Route `/ws/*` to the edge in your reverse proxy and everything else to the
+server. `GET /healthz/ready` answers 503 while the server's link to the edge
+is down.
+
+## Web app
+
+The PyPI wheel includes the built web app. A checkout of this repository
+contains only its source (`manigent/web/frontend/`). In a checkout, the
+server serves the API alone until you build it:
+
+```bash
+cd manigent/web/frontend && npm ci && npm run build
+```
+
+## Where this code comes from
+
+This repository is generated from the Manigent monorepo by
+`scripts/build-server-package.sh` on every change, so pull requests are
+applied there. The hub itself is a separate, closed service. Its wire
+protocol, `manigent/hub_protocol/`, is MIT-licensed and ships here.
+
+## License
+
+[Business Source License 1.1](LICENSE), with Manigent' Additional Use Grant.
+In plain words, which do not replace the license text:
+
+- **You may** run it in production for your own organization and its
+  affiliates, modify it, and use it to provide your own products and
+  services. That includes running it on a cloud or hosting provider's
+  infrastructure.
+- **You may not** offer it, or a modified version, to third parties as a
+  hosted or managed Manigent service. For that, contact us for a
+  commercial license.
+- **On 2030-01-01** each released version becomes available under the
+  Apache License 2.0. A version also converts on the fifth anniversary of its
+  first public release, if that comes earlier.
+
+`manigent/hub_protocol/` is MIT; each file says so in its SPDX header.

manigent_server-0.1.0/manigent/_catalog/mcps/chess/README.md

@@ -0,0 +1,38 @@
+# Chess MCP
+
+Deterministic chess referee backed by [`python-chess`](https://python-chess.readthedocs.io/). Install this MCP on the **gamemaster** agent of a chess match — players propose moves in chat as plain text, the gamemaster validates them through this MCP, and the state is published to the chatroom files so every participant (and any browser page) sees the same board.
+
+## Tools
+
+| Tool | Purpose |
+|---|---|
+| `start_game(game_id, white_name, black_name)` | Create a new board at the starting position and lay out the per-game viewer directory. Returns `state_json_content` (for the gamemaster to publish into the chatroom so other agents can read) and `view_path` (absolute path to `board.html` the user opens in a browser). |
+| `make_move(game_id, color, move)` | Apply a move. Rejects if `color` doesn't match `board.turn` or if the move is illegal. On success returns `ok`, `san`, `uci`, `fen`, `is_game_over`, `result`, `move_number`, plus `state_json_content`. On rejection returns `error`. The MCP writes `board_state.json` + `board_state.js` to the game's viewer directory automatically — the gamemaster only needs to publish `state_json_content` to the chatroom. |
+| `post_narration(game_id, text)` | Append a narrator comment (≤1000 chars) to the game. Attaches to the most recently played ply so the live board viewer can render it alongside the move. Called by the **gamemaster** — it relays the narrator agent's chat commentary verbatim so the single per-agent MCP state directory stays consistent. |
+| `get_state(game_id)` | Re-read the canonical state for a game (FEN, PGN, active color, move history, narration, result). |
+| `get_legal_moves(game_id, from_square=None)` | List legal SAN moves in the current position, optionally filtered by source square. |
+| `resign(game_id, color)` | End the game by resignation. |
+| `list_games()` | Enumerate all game ids with state files in this MCP's state directory. |
+
+## State directory
+
+The MCP resolves `MANIGENT_CHESS_STATE_DIR` (injected by the Manigent runner — it points at `{agent_dir}/mcp-hub/servers/chess/`). Per-game files live at:
+
+```
+{state_dir}/games/{game_id}/
+  board_state.json   # canonical state (MCP reads+writes this)
+  board_state.js     # wrapper the browser viewer loads on every tick
+  board.html         # static viewer page (written once on start_game)
+```
+
+The MCP writes `board_state.json` + `board_state.js` on every `start_game`, `make_move`, `resign`, and `post_narration` — narration entries live inside `board_state.json` under a `narration: []` list, so the viewer renders them on the same 1.5 s tick as move updates. The MCP does not push anything into the chatroom — the gamemaster is expected to forward `state_json_content` as `board_state.json` into the chatroom so the player agents (white, black, narrator) can read the position.
+
+## Board viewer
+
+`start_game` writes a self-contained HTML page to `{state_dir}/games/{game_id}/board.html` and returns its absolute path in `view_path`. The gamemaster forwards that path to the user, who opens it in any browser via `file://` — no HTTP server required.
+
+The viewer polls `./board_state.js` every 1.5 s by appending a cache-busted `<script>` tag. We use `<script>` rather than `fetch()` because Chrome blocks `fetch()` from `file://` origins. The `board_state.js` file is a 1-line `window.__CHESS_STATE = {...};` wrapper that the MCP rewrites atomically on every move.
+
+## Dependencies
+
+`python-chess>=1.10` (ships with the `manigent` runner package).

manigent_server-0.1.0/manigent/_catalog/mcps/chess/mcp.json

@@ -0,0 +1,9 @@
+{
+  "launch": {
+    "command": "python",
+    "args": ["-m", "manigent.mcp.servers.chess_server"],
+    "env": {
+      "MANIGENT_CHESS_STATE_DIR": "{{token_path}}/.."
+    }
+  }
+}

manigent_server-0.1.0/manigent/_catalog/mcps/registry.json

@@ -0,0 +1,9 @@
+[
+  {
+    "name": "chess",
+    "description": "Deterministic chess referee: start games, validate moves, track state. Used by the gamemaster agent in the chess template.",
+    "tags": ["game", "chess", "turn-based"],
+    "version": "1.0.0",
+    "attribution": "Built on python-chess"
+  }
+]