Skip to main content

Quick Start

This guide creates the smallest useful OmniCoreAgent: one model, one harness runtime, one task, one local tool, and one stable session. The core install stays light. Redis, PostgreSQL, MongoDB, S3/R2, OmniServe, and background scheduling install as extras when the agent needs them.
1

Install

2

Set API Key

Export the model key for the provider you choose:
OmniCoreAgent uses LLM_API_KEY as the single public API-key variable. Choose the provider with model_config["provider"]. See Model Support for supported provider names.
3

Create Your First Agent

Create hello_agent.py:
4

Run It

You now have an agent with the core harness loop, session memory, workspace files, guardrails, events, metrics, and cleanup lifecycle.

Add Local Tools

Local tools are normal Python functions registered through ToolRegistry.

Keep Continuity With Session IDs

Agents keep continuity when you provide a stable session_id:
The default memory backend is in-memory and works for local development. Use Redis, MongoDB, or SQL database storage when conversation history must survive process restarts.

Common First-Run Errors

Export the model key before running your script:
OmniCoreAgent examples use LLM_API_KEY as the single public model API-key variable.
Set both fields:
See Models for supported provider names.
Install the extra for the backend you are using:
The base quickstart does not require these extras.

Next: Add MCP Tools

MCP servers are external tool providers. OmniCoreAgent connects to them and loads their tools into the same runtime view as local tools. This optional example uses Node.js and npx because the filesystem MCP server is published as an npm package:
MCP connects external MCP server tools into OmniCoreAgent’s tool runtime. Those tools run beside local tools, workspace tools, artifact tools, skills, and harness tools.

Next: Turn On Heavier Harness Features

For longer tasks, enable the heavier harness features explicitly: automatic context control before each model call, tool output offloading into the workspace, BM25 tool retrieval, subagents, and skills.
When enable_subagents is true, workspace files are enabled automatically so workers write outputs that the lead agent reads back.

Next Steps

Local Tools

Register Python functions as tools.

Workspace Files

Store notes, artifacts, scratchpads, and tool offloads.

OmniServe

Serve this agent through REST and SSE.

Configuration

Configure context, tool offload, memory, events, and workspace storage.

Use Docs With AI Tools

Ask questions against the official docs from your editor or AI tool.

Architecture

Understand the runtime layers and request flow.