open-edison 0.1.19__tar.gz → 0.1.29__tar.gz

{open_edison-0.1.19 → open_edison-0.1.29}/.gitignore

@@ -216,4 +216,7 @@ src/frontend_dist/
 frontend_dist/
 frontend/node_modules/
 frontend/package-lock.json
-.vscode
+.vscode
+install_id
+dev_config_dir/
+sessions.db

{open_edison-0.1.19 → open_edison-0.1.29}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: open-edison
-Version: 0.1.19
+Version: 0.1.29
 Summary: Open-source MCP security, aggregation, and monitoring. Single-user, self-hosted MCP proxy.
 Author-email: Hugo Berg <hugo@edison.watch>
 License-File: LICENSE
@@ -25,24 +25,45 @@ Requires-Dist: pytest>=8.3.3; extra == 'dev'
 Requires-Dist: ruff>=0.12.3; extra == 'dev'
 Description-Content-Type: text/markdown
 
-# OpenEdison
+# OpenEdison 🔒⚡️
 
-Open-source single-user MCP security gateway that prevents data exfiltration—via direct access or tool chaining—with full monitoring for local single‑user deployments. Provides core functionality of <https://edison.watch> for local use.
+> The secure MCP proxy gateway
+
+Connect AI to your data/software securely without risk of data exfiltration. Gain visibility, block threats, and get alerts on the data your agent is reading/writing. No more "approve fatigue" with the MCP tool-call approvals.
+
+OpenEdison solves the [lethal trifecta problem](https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/), which can cause agent hijacking & data exfiltration by malicious actors.
+
+<p align="center">
+  <img src="media/trifecta520p.gif" alt="Trifecta Security Risk Animation" width="520">
+</p>
 
 <div align="center">
-  <h2>📧 Interested in connecting AI to your business software with proper access controls? <a href="mailto:hello@edison.watch">Contact us</a> to discuss.</h2>
+  <h2>📧 To get visibility, control and exfiltration blocker into AI's interaction with your company software, systems of record, DBs, <a href="mailto:hello@edison.watch">Contact us</a> to discuss.</h2>
 </div>
 
-## Features
+<p align="center">
+  <img alt="Project Version" src="https://img.shields.io/pypi/v/open-edison?label=version&color=blue">
+  <img alt="Python Version" src="https://img.shields.io/badge/python-3.12-blue?logo=python">
+  <img src="https://img.shields.io/badge/License-GPLv3-blue" alt="License">
+
+</p>
+
+---
+
+## Features ✨
+
+- 🛑 **Data leak blocker** - Edison automatically blocks any data leaks, even if your AI gets jailbroken
+- 🕰️ **Deterministic execution** - Deterministic execution. Guaranteed data exfiltration blocker.
+- 🗂️ **Easily configurable** - Easy to configure and manage your MCP servers
+- 📊 **Visibility into agent interactions** - Track and monitor your agents and their interactions with connected software/data via MCP calls
+- 🔗 **Simple API** - REST API for managing MCP servers and proxying requests
+- 🐳 **Docker support** - Run in a container for easy deployment
 
-- **Single-user MCP proxy** - No multi-user complexity, just a simple proxy for your MCP servers
-- **JSON configuration** - Easy to configure and manage your MCP servers
-- **Simple local frontend** - Track and monitor your MCP interactions, servers, and sessions.
-- **Session tracking** - Track and monitor your MCP interactions
-- **Simple API** - REST API for managing MCP servers and proxying requests
-- **Docker support** - Run in a container for easy deployment
+## About Edison.watch 🏢
 
-## Quick Start
+Edison helps you gain observability, control, and policy enforcement for all AI interactions with systems of records, existing company software and data. Prevent AI from causing data leakage, lightning-fast setup for cross-system governance.
+
+## Quick Start 🚀
 
 The fastest way to get started:
 
@@ -52,10 +73,10 @@ The fastest way to get started:
 curl -fsSL https://raw.githubusercontent.com/Edison-Watch/open-edison/main/curl_pipe_bash.sh | bash
 ```
 
-Run locally with uvx: `uvx open-edison --config-dir ~/edison-config`
+Run locally with uvx: `uvx open-edison`
 
 <details>
-<summary>Install Node.js/npm (optional for MCP tools)</summary>
+<summary>⬇️ Install Node.js/npm (optional for MCP tools)</summary>
 
 If you need `npx` (for Node-based MCP tools like `mcp-remote`), install Node.js as well:
 
@@ -75,6 +96,7 @@ If you need `npx` (for Node-based MCP tools like `mcp-remote`), install Node.js
 - Node/npx: `winget install -e --id OpenJS.NodeJS`
 
 After installation, ensure that `npx` is available on PATH.
+</details>
 
 <details>
 <summary><img src="https://img.shields.io/badge/pypi-3775A9?style=for-the-badge&logo=pypi&logoColor=white" alt="PyPI"> Install from PyPI</summary>
@@ -85,11 +107,11 @@ After installation, ensure that `npx` is available on PATH.
 
 ```bash
 # Using uvx
-uvx open-edison --help
+uvx open-edison
 
 # Using pipx
 pipx install open-edison
-open-edison --help
+open-edison
 ```
 
 Run with a custom config directory:
@@ -109,18 +131,18 @@ There is a dockerfile for simple local setup.
 
 ```bash
 # Single-line:
-git clone https://github.com/GatlingX/open-edison.git && cd open-edison && make docker_run
+git clone https://github.com/Edison-Watch/open-edison.git && cd open-edison && make docker_run
 
 # Or
 # Clone repo
-git clone https://github.com/GatlingX/open-edison.git
+git clone https://github.com/Edison-Watch/open-edison.git
 # Enter repo
 cd open-edison
 # Build and run
 make docker_run
 ```
 
-The MCP server will be available at `http://localhost:3000` and the api + frontend at `http://localhost:3001`.
+The MCP server will be available at `http://localhost:3000` and the api + frontend at `http://localhost:3001`. 🌐
 
 </details>
 
@@ -130,7 +152,7 @@ The MCP server will be available at `http://localhost:3000` and the api + fronte
 1. Clone the repository:
 
 ```bash
-git clone https://github.com/GatlingX/open-edison.git
+git clone https://github.com/Edison-Watch/open-edison.git
 cd open-edison
 ```
 
@@ -161,12 +183,12 @@ make run
 open-edison run
 ```
 
-The server will be available at `http://localhost:3000`.
+The server will be available at `http://localhost:3000`. 🌐
 
 </details>
 
 <details>
-<summary>MCP Connection</summary>
+<summary>🔌 MCP Connection</summary>
 
 Connect any MCP client to Open Edison (requires Node.js/npm for `npx`):
 
@@ -190,20 +212,20 @@ Or add to your MCP client config:
 </details>
 
 <details>
-<summary>Usage</summary>
+<summary>🧭 Usage</summary>
 
 ### API Endpoints
 
 See [API Reference](docs/quick-reference/api_reference.md) for full API documentation.
 
 <details>
-<summary>Development</summary>
+<summary>🛠️ Development</summary>
 
-### Setup
+### Setup 🧰
 
 Setup from source as above.
 
-### Run
+### Run ▶️
 
 Server doesn't have any auto-reload at the moment, so you'll need to run & ctrl-c this during development.
 
@@ -211,7 +233,7 @@ Server doesn't have any auto-reload at the moment, so you'll need to run & ctrl-
 make run
 ```
 
-### Tests/code quality
+### Tests/code quality ✅
 
 We expect `make ci` to return cleanly.
 
@@ -224,7 +246,7 @@ make ci
 <details>
 <summary>⚙️ Configuration (config.json)</summary>
 
-## Configuration
+## Configuration ⚙️
 
 The `config.json` file contains all configuration:
 
@@ -246,18 +268,20 @@ Each MCP server configuration includes:
 
 </details>
 
+## 🔐 How Edison prevents data leakages
+
 <details>
-<summary>Security & Permissions System</summary>
+<summary>🔱 The lethal trifecta, agent lifecycle management</summary>
 
 Open Edison includes a comprehensive security monitoring system that tracks the "lethal trifecta" of AI agent risks, as described in [Simon Willison's blog post](https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/):
 
-<img src="media/lethal-trifecta.png" alt="The lethal trifecta diagram showing the three key AI agent security risks" width="30%">
+<img src="media/lethal-trifecta.png" alt="The lethal trifecta diagram showing the three key AI agent security risks" width="70%">
 
 1. **Private data access** - Access to sensitive local files/data
 2. **Untrusted content exposure** - Exposure to external/web content  
 3. **External communication** - Ability to write/send data externally
 
-<img src="media/pam-diagram.png" alt="Privileged Access Management (PAM) example showing the lethal trifecta in action" width="60%">
+<img src="media/pam-diagram.png" alt="Privileged Access Management (PAM) example showing the lethal trifecta in action" width="90%">
 
 The configuration allows you to classify these risks across **tools**, **resources**, and **prompts** using separate configuration files.
 
@@ -265,7 +289,7 @@ In addition to trifecta, we track Access Control Level (ACL) for each tool call,
 that is, each tool has an ACL level (one of PUBLIC, PRIVATE, or SECRET), and we track the highest ACL level for each session.
 If a write operation is attempted to a lower ACL level, it is blocked.
 
-### Tool Permissions (`tool_permissions.json`)
+### 🧰 Tool Permissions (`tool_permissions.json`)
 
 Defines security classifications for MCP tools. See full file: [tool_permissions.json](tool_permissions.json), it looks like:
 
@@ -283,7 +307,7 @@ Defines security classifications for MCP tools. See full file: [tool_permissions
 ```
 
 <details>
-<summary>Resource Permissions (`resource_permissions.json`)</summary>
+<summary>📁 Resource Permissions (`resource_permissions.json`)</summary>
 
 ### Resource Permissions (`resource_permissions.json`)
 
@@ -299,7 +323,7 @@ Defines security classifications for resource access patterns. See full file: [r
 </details>
 
 <details>
-<summary>Prompt Permissions (`prompt_permissions.json`)</summary>
+<summary>💬 Prompt Permissions (`prompt_permissions.json`)</summary>
 
 ### Prompt Permissions (`prompt_permissions.json`)
 
@@ -314,7 +338,7 @@ Defines security classifications for prompt types. See full file: [prompt_permis
 
 </details>
 
-### Wildcard Patterns
+### Wildcard Patterns ✨
 
 All permission types support wildcard patterns:
 
@@ -322,7 +346,7 @@ All permission types support wildcard patterns:
 - **Resources**: `scheme:*` (e.g., `file:*` matches all file resources)  
 - **Prompts**: `type:*` (e.g., `template:*` matches all template prompts)
 
-### Security Monitoring
+### Security Monitoring 🕵️
 
 **All items must be explicitly configured** - unknown tools/resources/prompts will be rejected for security.
 
@@ -330,20 +354,17 @@ Use the `get_security_status` tool to monitor your session's current risk level
 
 </details>
 
-<details>
-<summary>Documentation</summary>
+## Documentation 📚
 
 📚 **Complete documentation available in [`docs/`](docs/)**
 
-- **[Getting Started](docs/quick-reference/config_quick_start.md)** - Quick setup guide
-- **[Configuration](docs/core/configuration.md)** - Complete configuration reference
-- **[API Reference](docs/quick-reference/api_reference.md)** - REST API documentation
-- **[Development Guide](docs/development/development_guide.md)** - Contributing and development
-
-</details>
+- 🚀 **[Getting Started](docs/quick-reference/config_quick_start.md)** - Quick setup guide
+- ⚙️ **[Configuration](docs/core/configuration.md)** - Complete configuration reference
+- 📡 **[API Reference](docs/quick-reference/api_reference.md)** - REST API documentation
+- 🧑‍💻 **[Development Guide](docs/development/development_guide.md)** - Contributing and development
 
 <details>
-<summary>License</summary>
+<summary>📄 License</summary>
 
 GPL-3.0 License - see [LICENSE](LICENSE) for details.
 

{open_edison-0.1.19 → open_edison-0.1.29}/README.md

@@ -1,21 +1,42 @@
-# OpenEdison
+# OpenEdison 🔒⚡️
 
-Open-source single-user MCP security gateway that prevents data exfiltration—via direct access or tool chaining—with full monitoring for local single‑user deployments. Provides core functionality of <https://edison.watch> for local use.
+> The secure MCP proxy gateway
+
+Connect AI to your data/software securely without risk of data exfiltration. Gain visibility, block threats, and get alerts on the data your agent is reading/writing. No more "approve fatigue" with the MCP tool-call approvals.
+
+OpenEdison solves the [lethal trifecta problem](https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/), which can cause agent hijacking & data exfiltration by malicious actors.
+
+<p align="center">
+  <img src="media/trifecta520p.gif" alt="Trifecta Security Risk Animation" width="520">
+</p>
 
 <div align="center">
-  <h2>📧 Interested in connecting AI to your business software with proper access controls? <a href="mailto:hello@edison.watch">Contact us</a> to discuss.</h2>
+  <h2>📧 To get visibility, control and exfiltration blocker into AI's interaction with your company software, systems of record, DBs, <a href="mailto:hello@edison.watch">Contact us</a> to discuss.</h2>
 </div>
 
-## Features
+<p align="center">
+  <img alt="Project Version" src="https://img.shields.io/pypi/v/open-edison?label=version&color=blue">
+  <img alt="Python Version" src="https://img.shields.io/badge/python-3.12-blue?logo=python">
+  <img src="https://img.shields.io/badge/License-GPLv3-blue" alt="License">
+
+</p>
+
+---
+
+## Features ✨
+
+- 🛑 **Data leak blocker** - Edison automatically blocks any data leaks, even if your AI gets jailbroken
+- 🕰️ **Deterministic execution** - Deterministic execution. Guaranteed data exfiltration blocker.
+- 🗂️ **Easily configurable** - Easy to configure and manage your MCP servers
+- 📊 **Visibility into agent interactions** - Track and monitor your agents and their interactions with connected software/data via MCP calls
+- 🔗 **Simple API** - REST API for managing MCP servers and proxying requests
+- 🐳 **Docker support** - Run in a container for easy deployment
 
-- **Single-user MCP proxy** - No multi-user complexity, just a simple proxy for your MCP servers
-- **JSON configuration** - Easy to configure and manage your MCP servers
-- **Simple local frontend** - Track and monitor your MCP interactions, servers, and sessions.
-- **Session tracking** - Track and monitor your MCP interactions
-- **Simple API** - REST API for managing MCP servers and proxying requests
-- **Docker support** - Run in a container for easy deployment
+## About Edison.watch 🏢
 
-## Quick Start
+Edison helps you gain observability, control, and policy enforcement for all AI interactions with systems of records, existing company software and data. Prevent AI from causing data leakage, lightning-fast setup for cross-system governance.
+
+## Quick Start 🚀
 
 The fastest way to get started:
 
@@ -25,10 +46,10 @@ The fastest way to get started:
 curl -fsSL https://raw.githubusercontent.com/Edison-Watch/open-edison/main/curl_pipe_bash.sh | bash
 ```
 
-Run locally with uvx: `uvx open-edison --config-dir ~/edison-config`
+Run locally with uvx: `uvx open-edison`
 
 <details>
-<summary>Install Node.js/npm (optional for MCP tools)</summary>
+<summary>⬇️ Install Node.js/npm (optional for MCP tools)</summary>
 
 If you need `npx` (for Node-based MCP tools like `mcp-remote`), install Node.js as well:
 
@@ -48,6 +69,7 @@ If you need `npx` (for Node-based MCP tools like `mcp-remote`), install Node.js
 - Node/npx: `winget install -e --id OpenJS.NodeJS`
 
 After installation, ensure that `npx` is available on PATH.
+</details>
 
 <details>
 <summary><img src="https://img.shields.io/badge/pypi-3775A9?style=for-the-badge&logo=pypi&logoColor=white" alt="PyPI"> Install from PyPI</summary>
@@ -58,11 +80,11 @@ After installation, ensure that `npx` is available on PATH.
 
 ```bash
 # Using uvx
-uvx open-edison --help
+uvx open-edison
 
 # Using pipx
 pipx install open-edison
-open-edison --help
+open-edison
 ```
 
 Run with a custom config directory:
@@ -82,18 +104,18 @@ There is a dockerfile for simple local setup.
 
 ```bash
 # Single-line:
-git clone https://github.com/GatlingX/open-edison.git && cd open-edison && make docker_run
+git clone https://github.com/Edison-Watch/open-edison.git && cd open-edison && make docker_run
 
 # Or
 # Clone repo
-git clone https://github.com/GatlingX/open-edison.git
+git clone https://github.com/Edison-Watch/open-edison.git
 # Enter repo
 cd open-edison
 # Build and run
 make docker_run
 ```
 
-The MCP server will be available at `http://localhost:3000` and the api + frontend at `http://localhost:3001`.
+The MCP server will be available at `http://localhost:3000` and the api + frontend at `http://localhost:3001`. 🌐
 
 </details>
 
@@ -103,7 +125,7 @@ The MCP server will be available at `http://localhost:3000` and the api + fronte
 1. Clone the repository:
 
 ```bash
-git clone https://github.com/GatlingX/open-edison.git
+git clone https://github.com/Edison-Watch/open-edison.git
 cd open-edison
 ```
 
@@ -134,12 +156,12 @@ make run
 open-edison run
 ```
 
-The server will be available at `http://localhost:3000`.
+The server will be available at `http://localhost:3000`. 🌐
 
 </details>
 
 <details>
-<summary>MCP Connection</summary>
+<summary>🔌 MCP Connection</summary>
 
 Connect any MCP client to Open Edison (requires Node.js/npm for `npx`):
 
@@ -163,20 +185,20 @@ Or add to your MCP client config:
 </details>
 
 <details>
-<summary>Usage</summary>
+<summary>🧭 Usage</summary>
 
 ### API Endpoints
 
 See [API Reference](docs/quick-reference/api_reference.md) for full API documentation.
 
 <details>
-<summary>Development</summary>
+<summary>🛠️ Development</summary>
 
-### Setup
+### Setup 🧰
 
 Setup from source as above.
 
-### Run
+### Run ▶️
 
 Server doesn't have any auto-reload at the moment, so you'll need to run & ctrl-c this during development.
 
@@ -184,7 +206,7 @@ Server doesn't have any auto-reload at the moment, so you'll need to run & ctrl-
 make run
 ```
 
-### Tests/code quality
+### Tests/code quality ✅
 
 We expect `make ci` to return cleanly.
 
@@ -197,7 +219,7 @@ make ci
 <details>
 <summary>⚙️ Configuration (config.json)</summary>
 
-## Configuration
+## Configuration ⚙️
 
 The `config.json` file contains all configuration:
 
@@ -219,18 +241,20 @@ Each MCP server configuration includes:
 
 </details>
 
+## 🔐 How Edison prevents data leakages
+
 <details>
-<summary>Security & Permissions System</summary>
+<summary>🔱 The lethal trifecta, agent lifecycle management</summary>
 
 Open Edison includes a comprehensive security monitoring system that tracks the "lethal trifecta" of AI agent risks, as described in [Simon Willison's blog post](https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/):
 
-<img src="media/lethal-trifecta.png" alt="The lethal trifecta diagram showing the three key AI agent security risks" width="30%">
+<img src="media/lethal-trifecta.png" alt="The lethal trifecta diagram showing the three key AI agent security risks" width="70%">
 
 1. **Private data access** - Access to sensitive local files/data
 2. **Untrusted content exposure** - Exposure to external/web content  
 3. **External communication** - Ability to write/send data externally
 
-<img src="media/pam-diagram.png" alt="Privileged Access Management (PAM) example showing the lethal trifecta in action" width="60%">
+<img src="media/pam-diagram.png" alt="Privileged Access Management (PAM) example showing the lethal trifecta in action" width="90%">
 
 The configuration allows you to classify these risks across **tools**, **resources**, and **prompts** using separate configuration files.
 
@@ -238,7 +262,7 @@ In addition to trifecta, we track Access Control Level (ACL) for each tool call,
 that is, each tool has an ACL level (one of PUBLIC, PRIVATE, or SECRET), and we track the highest ACL level for each session.
 If a write operation is attempted to a lower ACL level, it is blocked.
 
-### Tool Permissions (`tool_permissions.json`)
+### 🧰 Tool Permissions (`tool_permissions.json`)
 
 Defines security classifications for MCP tools. See full file: [tool_permissions.json](tool_permissions.json), it looks like:
 
@@ -256,7 +280,7 @@ Defines security classifications for MCP tools. See full file: [tool_permissions
 ```
 
 <details>
-<summary>Resource Permissions (`resource_permissions.json`)</summary>
+<summary>📁 Resource Permissions (`resource_permissions.json`)</summary>
 
 ### Resource Permissions (`resource_permissions.json`)
 
@@ -272,7 +296,7 @@ Defines security classifications for resource access patterns. See full file: [r
 </details>
 
 <details>
-<summary>Prompt Permissions (`prompt_permissions.json`)</summary>
+<summary>💬 Prompt Permissions (`prompt_permissions.json`)</summary>
 
 ### Prompt Permissions (`prompt_permissions.json`)
 
@@ -287,7 +311,7 @@ Defines security classifications for prompt types. See full file: [prompt_permis
 
 </details>
 
-### Wildcard Patterns
+### Wildcard Patterns ✨
 
 All permission types support wildcard patterns:
 
@@ -295,7 +319,7 @@ All permission types support wildcard patterns:
 - **Resources**: `scheme:*` (e.g., `file:*` matches all file resources)  
 - **Prompts**: `type:*` (e.g., `template:*` matches all template prompts)
 
-### Security Monitoring
+### Security Monitoring 🕵️
 
 **All items must be explicitly configured** - unknown tools/resources/prompts will be rejected for security.
 
@@ -303,20 +327,17 @@ Use the `get_security_status` tool to monitor your session's current risk level
 
 </details>
 
-<details>
-<summary>Documentation</summary>
+## Documentation 📚
 
 📚 **Complete documentation available in [`docs/`](docs/)**
 
-- **[Getting Started](docs/quick-reference/config_quick_start.md)** - Quick setup guide
-- **[Configuration](docs/core/configuration.md)** - Complete configuration reference
-- **[API Reference](docs/quick-reference/api_reference.md)** - REST API documentation
-- **[Development Guide](docs/development/development_guide.md)** - Contributing and development
-
-</details>
+- 🚀 **[Getting Started](docs/quick-reference/config_quick_start.md)** - Quick setup guide
+- ⚙️ **[Configuration](docs/core/configuration.md)** - Complete configuration reference
+- 📡 **[API Reference](docs/quick-reference/api_reference.md)** - REST API documentation
+- 🧑‍💻 **[Development Guide](docs/development/development_guide.md)** - Contributing and development
 
 <details>
-<summary>License</summary>
+<summary>📄 License</summary>
 
 GPL-3.0 License - see [LICENSE](LICENSE) for details.
 

{open_edison-0.1.19 → open_edison-0.1.29}/config.json

@@ -54,7 +54,7 @@
                 "./test.db"
             ],
             "env": {},
-            "enabled": false,
+            "enabled": true,
             "roots": []
         },
         {

{open_edison-0.1.19 → open_edison-0.1.29}/desktop_ext/README.md

@@ -146,7 +146,7 @@ This extension operates securely:
 1. **Clone the repository**:
 
    ```bash
-   git clone https://github.com/GatlingX/open-edison
+   git clone https://github.com/Edison-Watch/open-edison
    cd open-edison/desktop_ext
    ```
 
@@ -181,11 +181,11 @@ desktop_ext/
 ## Contributing
 
 This extension is part of the Open Edison project. See the main repository for contribution guidelines:
-<https://github.com/GatlingX/open-edison>
+<https://github.com/Edison-Watch/open-edison>
 
 ## Related Resources
 
-- [Open Edison Main Repository](https://github.com/GatlingX/open-edison)
+- [Open Edison Main Repository](https://github.com/Edison-Watch/open-edison)
 - [mcp-remote Package](https://www.npmjs.com/package/mcp-remote)
 - [Model Context Protocol](https://modelcontextprotocol.io/)
 - [Anthropic Desktop Extensions](https://support.anthropic.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop)

{open_edison-0.1.19 → open_edison-0.1.29}/docs/deployment/local.md

@@ -24,7 +24,7 @@ This guide covers installing and running Open Edison directly on your local mach
 
 ```bash
 # Clone the repository
-git clone https://github.com/GatlingX/open-edison.git
+git clone https://github.com/Edison-Watch/open-edison.git
 cd open-edison
 ```
 

{open_edison-0.1.19 → open_edison-0.1.29}/docs/development/contributing.md

@@ -24,7 +24,7 @@ Open Edison is designed to be:
 
 ```bash
 # Clone the repository
-git clone https://github.com/GatlingX/open-edison.git
+git clone https://github.com/Edison-Watch/open-edison.git
 cd open-edison
 
 # Install dependencies
@@ -177,7 +177,7 @@ git clone https://github.com/your-username/open-edison.git
 cd open-edison
 
 # Add upstream remote
-git remote add upstream https://github.com/GatlingX/open-edison.git
+git remote add upstream https://github.com/Edison-Watch/open-edison.git
 ```
 
 ### 2. **Create Feature Branch**

{open_edison-0.1.19 → open_edison-0.1.29}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "open-edison"
-version = "0.1.19"
+version = "0.1.29"
 description = "Open-source MCP security, aggregation, and monitoring. Single-user, self-hosted MCP proxy."
 readme = "README.md"
 authors = [

{open_edison-0.1.19 → open_edison-0.1.29}/src/cli.py

@@ -177,6 +177,7 @@ def _spawn_frontend_dev(  # noqa: C901 - pragmatic complexity for env probing
 
 
 async def _run_server(args: Any) -> None:
+    # TODO check this works as we want it to
     # Resolve config dir and expose via env for the rest of the app
     config_dir_arg = getattr(args, "config_dir", None)
     if config_dir_arg is not None:
@@ -184,7 +185,7 @@ async def _run_server(args: Any) -> None:
     config_dir = get_config_dir()
 
     # Load config after setting env override
-    cfg = Config.load()
+    cfg = Config(config_dir)
 
     host = getattr(args, "host", None) or cfg.server.host
     port = getattr(args, "port", None) or cfg.server.port