ARCHITECTURE
Architecture
Desktop, CLI and mobile share one agent kernel. Subscription requests route through the Neox gateway; BYOK requests go directly to the provider.
0system layers
0client platforms
0+model providers
01SYSTEM MAP
Five system layers
Each layer serves the one above it through a defined contract.
Neox implementationEmbeddable / documentedExternal serviceRequest flow
02AGENT LOOP
The agent loop
Plan, gate, act and observe until done. Interruptible at every step.
03REQUEST LIFECYCLE
The path of a single request
The full path from instruction to result.
- 01L2Understand & planreads the code; plans multi-step work
- 02L2CheckpointShadow Git rollback point
- 03L2Run toolsedits files, runs commands; optional OS sandbox
- 04L3Gatewayverify, route, limit, break
- 05L1Streamlive and interruptible
- 06L5Usageusage counted against quota
04ENGINEERING PRINCIPLES
Engineering principles
Local execution
Tools and commands run on your machine. BYOK requests go direct.
Reversible changes
A checkpoint precedes every turn.
Encrypted keys
Keys are stored encrypted, never in plaintext.
Traceable
Every tool call is logged.
Agent SDK
Embed the kernel in your product with the Agent SDK, open source under Apache-2.0 as part of OpenNeox.



