ODEI App is the macOS-first runtime and builder workspace for ODEI, a local-first system for graph-based memory, governed agent execution, and auditable AI workflows.
This repository contains the desktop shell, supporting services, MCP servers, deployment assets, and test infrastructure used to build and operate the application.
app-main/andsrc/: Electron application shell and frontend modulesservers/: MCP servers and service runtimespackages/: shared packages and plugin integrationsdeploy/andapps/: public surface assets and deployment-specific codetests/: unit, integration, and end-to-end coverage
This repository is the clean public application repository for ODEI App. It intentionally excludes private operator workspaces, local agent configs, drafts, generated media, and historical monorepo debris.
- macOS
- Node.js 22+
- npm
- Neo4j Community Edition 5.x running on
bolt://127.0.0.1:7687
git clone https://github.com/odei-ai/odei-app.git
cd odei-app
npm ci
cp .env.example .env
cp .mcp.json.example .mcp.jsonThe example .mcp.json wires the core local servers shipped in this repository:
odei-neo4j, odei-history, and odei-worldmodel. Optional external
integrations can be added later without changing the baseline setup.
Build the workspace:
npm run buildStart the desktop application in development mode:
npm run devStart the Electron app directly:
npm startBefore first launch, update .env with at least your Neo4j credentials and any
API keys required for the flows you want to exercise. Electron expects a root
.mcp.json; without it the app cannot resolve local MCP servers.
npm run build
npm run dev
npm start
npm run test:unit
npm run test:unit:root
npm run test:integration
npm run test:playwright
npm run check:domain-docs
npm run check:api-site-static-assets
npm run typecheck
npm run lintUse the deterministic repo checks first:
npm run test:unit:rootnpm run check:domain-docsnpm run check:api-site-static-assetsnpm run typechecknpm run lint
Live boundary checks target deployed first-party surfaces and are intended for release or operations validation, not baseline local setup:
npm run check:api-site-contractnpm run check:app-subdomain-contractnpm run check:public-foundationnpm run check:api-ops-gate
The main GitHub CI pipeline stays deterministic. Live boundary validation runs separately as an operations workflow.
- ODEI is designed around a local-first operating model.
- Secrets and local operator tooling must stay out of version control.
- Review docs/SECURITY.md before running operational or deployment workflows.
- Use
.env.exampleas the starting point for local configuration. - Use
.mcp.json.exampleas the starting point for local MCP wiring.
MIT. See LICENSE.