Skip to main content
An agent is an AI system that reasons through problems and executes tasks autonomously. Agents are configured by specifying models, tools, instructions, and reasoning approach—providing everything needed to accomplish tasks from simple workflows to complex, open-ended objectives.

Agents UI guide

Create and manage agents through the SeekrFlow web interface.

Agents SDK guide

Create and manage agents programmatically with the Python SDK.

Agent primitives

Agents are built from two core primitives:

Models

A model serves as the agent’s cognitive engine, providing the reasoning capabilities needed to understand tasks, determine the best course of action, and generate responses. SeekrFlow supports both base models and fine-tuned models.

Tools

Tools are modular components that extend an agent’s capabilities beyond built-in reasoning. With tools, agents can take actions, access external systems, or query knowledge stores.

Agent configuration

When creating an agent, you configure several key properties:
PropertyDescription
NameIdentifier for the agent
InstructionsSystem prompt that guides how the agent operates and generates its response (also called developer message)
ModelWhich model to use for generating responses (can be a base model or fine-tuned model)
Tools (optional)Which tools the agent can access
Reasoning effort (optional)Controls how much reasoning the agent uses. Default is medium.
Temperature (optional)Controls the predictability of the agent’s reasoning. Lower values produce more consistent results, and higher values introduce more variation. Default is 0.6.

Reasoning effort

Reasoning effort controls how much reasoning the agent uses when working through a request. The default is medium.
LevelDescription
LowPrioritizes speed. Best for simple, latency-sensitive tasks with a small tool set.
MediumBalances speed and thoroughness. A good starting point for most use cases.
HighPrioritizes thoroughness. Best for complex workflows with many tools where accuracy matters more than speed.

Agent status

Each agent has a status that indicates its deployment state:
StatusDescription
ActiveReady to serve requests
PendingTransitioning between states. Either recently promoted and moving to active, or recently demoted and moving to inactive.
UpdatingAn update is in progress. Returns to active once changes take effect.
InactiveNot currently deployed, requires activation before serving requests
FailedDeployment failed. The agent cannot serve requests. To recover, address the issue and promote the agent manually.

Multi-agent workflows

Agents can delegate subtasks to other agents using the agent-as-tool pattern. A supervisor agent remains in control throughout a run, invoking sub-agents as callable tools to handle specialized tasks and then integrating their results into a unified response. This enables composable, multi-agent systems where each agent focuses on a specific capability. For implementation details, see Agent as tool.
Last modified on July 7, 2026