Repository navigation
docs: Add 100-star launch playbook, interactive make demo, and Enterprise README header #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,42 +1,49 @@ | ||
| # 🐒 CortexForge — toy project, not production-safe | ||
| # ⚡ CortexForge — Enterprise Multi-Tenant Control Plane for Hermes Agent | ||
|
|
||
| <p align="center"> | ||
| <img src="assets/banner.jpg" alt="CortexForge — isolated AI personas for every team member" width="1200"/> | ||
| <img src="assets/banner.jpg" alt="CortexForge — isolated Hermes Agent personas for every team member" width="1200"/> | ||
| </p> | ||
|
|
||
| > **Experimental / entertainment project. Do not use in production.** | ||
| > CortexForge is a Docker Compose playground for trying isolated AI assistant instances, quota proxies, message routing, and personal personas. It is **not audited**, **not hardened enough for real employee data**, and includes intentionally powerful local-admin capabilities such as Docker socket access and project write mounts. Treat it as a lab, not an enterprise security product. | ||
| > | ||
| > **Language / Язык:** English | [Русский](README.ru.md) | ||
| <p align="center"> | ||
| <b>One Cortex. Many Minds. Zero API Key Leakage.</b><br/> | ||
| Run from 1 to 1,000+ isolated <a href="https://github.com/NousResearch/hermes-agent">Hermes Agent</a> instances with per-user & per-department token quotas (including live SSE streams), inter-agent messaging, and zero-trust credential isolation — on pure Docker Compose. | ||
| </p> | ||
|
|
||
| [](https://github.com/example-org/cortex-forge/releases) | ||
| [](https://github.com/example-org/cortex-forge/actions/workflows/security.yml) | ||
| [](LICENSE) | ||
| <p align="center"> | ||
| <a href="https://github.com/rekurt/cortex-forge/stargazers"><img src="https://img.shields.io/github/stars/rekurt/cortex-forge?style=social" alt="GitHub Stars"/></a> | ||
| <a href="https://github.com/rekurt/cortex-forge/releases"><img src="https://img.shields.io/github/v/tag/rekurt/cortex-forge?label=version&color=blue" alt="Version"/></a> | ||
| <a href="https://github.com/rekurt/cortex-forge/actions/workflows/security.yml"><img src="https://github.com/rekurt/cortex-forge/actions/workflows/security.yml/badge.svg" alt="CI Security"/></a> | ||
| <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-green" alt="License: MIT"/></a> | ||
| <a href="docs/ENTERPRISE_1000_USERS.md"><img src="https://img.shields.io/badge/scale-1,000%20users%20%40%20355%20RPS-blueviolet" alt="1000-User Benchmark"/></a> | ||
| </p> | ||
|
|
||
| CortexForge is an experimental AI-assistant infrastructure sandbox built on [Hermes Agent](https://github.com/NousResearch/hermes-agent). | ||
| > **Language / Язык:** English | [Русский](README.ru.md) · [Project website](https://rekurt.github.io/cortex-forge/) · [Enterprise 1,000-User Guide](docs/ENTERPRISE_1000_USERS.md) | ||
|
|
||
| [Project website](https://rekurt.github.io/cortex-forge/) · [All projects by rekurt](https://rekurt.github.io/projects/) | ||
| --- | ||
|
|
||
| The idea is simple: run several isolated Telegram-bot assistant instances on one host, each with its own workspace, persona, token quota, and message inbox. | ||
| ## ⚡ Try It in 10 Seconds (Zero Docker / Zero API Keys Needed) | ||
|
|
||
| --- | ||
| Want to see `quota-proxy` (with live SSE streaming token accounting), `message-broker` (with instant broadcast), and multi-tenant quota enforcement in action right now? | ||
|
|
||
| ## What This Project Is | ||
| ```bash | ||
| git clone https://github.com/rekurt/cortex-forge.git && cd cortex-forge | ||
| make demo | ||
| ``` | ||
|
|
||
| This repository is useful for: | ||
| --- | ||
|
|
||
| - experimenting with per-user AI assistant containers | ||
| - testing quota enforcement in front of model APIs | ||
| - trying a simple broker for inter-assistant messages | ||
| - exploring persona/workspace-based assistant behavior | ||
| - prototyping internal automation skills behind a small HTTP service | ||
| ## Why CortexForge? | ||
|
|
||
| This repository is **not** suitable for: | ||
| [Hermes Agent](https://github.com/NousResearch/hermes-agent) gives you a powerful self-improving autonomous agent. **CortexForge** turns it into a multi-tenant team & enterprise platform where **no agent container ever sees your real upstream `ANTHROPIC_API_KEY`**. | ||
|
|
||
| - production employee assistants | ||
| - regulated data, secrets, customer data, or confidential documents | ||
| - multi-tenant deployments with real trust boundaries | ||
| - environments where Docker socket access, broad bind mounts, or OAuth proxy experiments are unacceptable | ||
| | Capability | Raw Single-Agent Setup | CortexForge v2.0 Enterprise | | ||
| |---|---|---| | ||
| | **Upstream API Key Isolation** | API key stored inside agent `.env` | **Zero exposure:** agents only see opaque `QUOTA_KEY_<NAME>` tokens; `quota-proxy` swaps keys on the fly | | ||
| | **SSE Streaming Token Quotas** | Unmetered or post-hoc billing | **Real-time `SSEUsageParser`:** meters Anthropic & OpenAI `text/event-stream` chunks on the fly + hard cutoff (`429`) | | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
For a request admitted with some quota remaining, Useful? React with 👍 / 👎. |
||
| | **Hierarchical Quotas** | None | **Per-user & per-department caps** with thread-safe concurrent admission guards | | ||
| | **Hot Key Registration** | Restart required | **Zero-downtime `POST /quota/register-key` & `POST /admin/register-key`** | | ||
| | **Inter-Agent Collaboration** | Isolated silos | **SQLite WAL `message-broker`:** P2P `/send`, priority queues, `peek=1`, and 1,000-agent `/broadcast` in 14 ms | | ||
| | **Fleet Scale** | Manual per-bot setup | **`scripts/bulk-users.py`:** provision 1,000 users in 0.5s with Compose shard profiles (`shard-0..shard-9`) | | ||
|
|
||
| --- | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the default Compose deployment,
assistant-adminexplicitly receives the realANTHROPIC_API_KEYandOPENAI_API_KEY(docker-compose.yml:135–137), mounts the project directory, and has writable Docker socket access. Consequently, the new guarantee that no agent container ever sees the upstream key is false for a shipped agent configuration. Qualify this claim in both READMEs and the launch copy to cover generated user instances, and retain an explicit warning about the privileged admin trust boundary so operators do not rely on nonexistent credential isolation.Useful? React with 👍 / 👎.