You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v0.4.1: New icon, simplified docs, DEVELOPER.md, version bump
- Replace app icon with new lowercase "o" design
- Rewrite AI_SETUP.md and API_REFERENCE.md as relay-only (no CLI/localhost)
- Create DEVELOPER.md for advanced users (CLI, tunnels, local API, MCP stdio/SSE)
- Add DEVELOPER.md to GitHub Actions build workflow
- Clarify SSE relay is for browser-based MCP clients only
- Fix README misleading text about n8n/Make.com standalone usage
- Bump version to 0.4.1 across all configs and source
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@@ -146,7 +146,7 @@ Run commands from inside your platform folder:
146
146
147
147
### Option 3: REST API Server
148
148
149
-
Start the server for webhooks, n8n, Make.com, or custom integrations:
149
+
Start the server for local integrations, scripting, or headless use:
150
150
151
151
```bash
152
152
./orunla_cli serve --port 3000
@@ -160,9 +160,34 @@ To secure the API when exposing to a network:
160
160
161
161
See `documentation/API_REFERENCE.md` for all endpoints.
162
162
163
+
#### API Key (v0.4.0)
164
+
165
+
When using the REST API server, you can secure it with an API key. When set, all REST API requests require the key via one of:
166
+
167
+
-`X-API-Key: your-key` header
168
+
-`Authorization: Bearer your-key` header
169
+
170
+
**MCP is not affected** — the API key only applies to REST API endpoints. Stdio MCP and SSE MCP connections are not gated by the API key.
171
+
172
+
To set the API key:
173
+
1. Pass it on the command line: `./orunla_cli serve --port 3000 --api-key "your-key"`, **or**
174
+
2. Manually edit `~/.orunla/config.json` and add `"api_key": "your-key"`
175
+
176
+
Requires a server restart to take effect.
177
+
178
+
#### Cloud REST API Relay (v0.4.0 — Windows/Tauri Desktop App)
179
+
180
+
If you use the Windows desktop app (Orunla.exe), it provides a **cloud REST API relay URL** shown in the "Remote Access" card. External services (ChatGPT Custom GPTs, n8n, Make.com) can use this URL to access your Orunla REST API without setting up tunnels or port forwarding.
181
+
182
+
- The relay URL works whenever the desktop app is open
183
+
- If an API key is set, remote requests must include it
184
+
-**File upload** (`/ingest-file`) is not supported via the relay — use the local API for file ingestion
185
+
186
+
> **Stdio MCP does not require the desktop app.** The standalone `orunla_mcp` binary works independently — you only need the REST API server (via `orunla_cli serve`) or the desktop app for REST/relay features.
The MCP server gives AI assistants direct access to your memory graph.
190
+
The MCP server gives AI assistants direct access to your memory graph. This works **independently of the desktop app** — you don't need a server running.
166
191
167
192
**Important:** All paths in MCP configs must be absolute. Replace the example paths below with the actual location of your Orunla folder.
168
193
@@ -178,9 +203,9 @@ The MCP server gives AI assistants direct access to your memory graph.
0 commit comments