Entry points
CLI, gateway, ACP, batch runner, API server, and library usage offer different ways into the agent foundation.
02 / INSIDE THE SYSTEM
Follow a request.
See the moving parts.
Entry points connect people and applications to the agent runtime. The runtime assembles context, resolves a provider, calls tools, and returns a response. Explore the layers below.
NEDURA / AGENT ARCHITECTUREOne runtime.
One runtime.
A connected ecosystem.
Context, models, tools, and sessions arranged around a central agent runtime.
PEOPLE & APPLICATIONSStart a requestCLI · Gateway · API / ACP
Memory & skillsRelevant context.
Reusable procedures.
Reusable procedures.
Dispatch tools · Return response Agent orchestration
Model providersYour configured model
and API connection.
and API connection.
Session storageSQLite + searchable history
Tool backendsTerminal · Browser · Web · MCP
01
Illustrative request flowA request arrives
The selected entry point passes a task into the agent runtime.
One runtime. Multiple entry points.
Start from the CLI, a configured messaging platform, an API client, or an ACP-compatible editor. The gateway handles platform events and routes messages into sessions.
Simplified from the Nedura architecture documentation. Connections are conceptual; model and external tool requests follow your configured providers.
REQUEST LIFECYCLE
A response can lead to another step.
- Receive the request
A CLI, gateway, API, batch runner, or editor integration supplies the task. Messaging adapters route platform events into the gateway.
- Assemble the context
The prompt builder combines instructions and context. Memory, skills, compression, and caching support the conversation loop.
- Resolve a provider
The runtime selects the configured provider and API mode. External model calls follow that provider’s configuration and service.
- Dispatch tools
The registry connects tool calls to handlers. Tool results return to the agent loop, which can request further work or produce a response.
- Return and retain
A response returns through the originating surface. Session storage preserves history; curated memory carries selected facts forward.
SYSTEM BOUNDARIES
Separate the runtime from its connections.
Execution backends
Terminal, browser, web, and MCP backends provide capabilities behind the tool interface. Choose them for your environment.
Persistent state
SQLite-backed sessions and searchable history support continuity. Profiles separate configuration and persistent agent state.
EXTENSION POINTS
Build on the right interface.
Use MCP when an external tool server already provides a capability. Use plugins for custom tools, hooks, or integrations without changing core code. ACP connects compatible editors; the API server supports OpenAI-compatible frontends.
These diagrams simplify the documented architecture. They illustrate relationships and request flow, not live traffic or a claim that external requests stay within a private network.
Read the architecture reference ↗