What OpenNeko is
OpenNeko is an operator-first agent workspace. It gives teams a local control plane for AI work: users talk to an agent, the agent reads approved business context, proposes or executes governed actions, and the system keeps auditable records of the work.
A normal deployment includes the web app, worker, metadata Postgres database, GraphJin metadata API, and OpenShell sandbox runtime. The app is where operators review threads and approvals. The worker runs queues, workflows, plugins, memory extraction, watcher sweeps, and sandboxed agent jobs.
The operating model follows OUDA: observe the request and source context, understand the relevant facts, decide on a response or action, then act through the trusted control plane. The agent loop is sandboxed; approvals, audit, secrets, and durable writes stay in OpenNeko.
- Threads collect human requests, agent runs, cards, memory proposals, action requests, and workflow outputs.
- GraphJin exposes metadata and, in demo or connected deployments, governed customer-data GraphQL endpoints.
- OpenShell isolates agent execution and plugin work behind default-deny egress policies.
- Plugins add connectors, actions, SSO providers, and channel integrations without moving secrets into the browser.
Default path
- Install the OpenNeko CLI with the bootstrap installer or a platform package.
- Run the setup wizard and pick demo, production, or development mode.
- Connect a data source or start with the AdventureWorks demo database.
- Invite operators, configure action policies, and install any plugins you need.
- Use threads and workflows to turn repeated operational work into governed agent runs.
System map
| Layer | Primary responsibility | Where it runs |
|---|---|---|
| Web | Threads, approvals, integrations, signin, admin UI, and operator review | Next.js app container |
| Worker | Agent runs, workflows, plugins, memory, behavior alarms, and queues | Node worker container |
| Metadata database | Org state, threads, runs, policies, memory, audit rows, plugins, and workflow records | Postgres with pgvector |
| GraphJin | GraphQL access to metadata and governed customer data | Metadata service plus optional source services |
| OpenShell | Sandboxed execution, mTLS gateway, network policy, and model egress proxying | Gateway plus per-run boxes |
