af server

Run the Agentfield control plane locally

af server

Start the Agentfield control plane with APIs, identity, memory, and orchestration

Usage

af server [options]

Description

The af server command runs the Agentfield control plane locally. It powers service discovery, memory coordination, workflow orchestration, and observability for your agents.

Key Flags

FlagDescription
--port <number>Port for the HTTP interface (default: 8080)
--uiLaunch the Agentfield UI alongside the control plane
--config <path>Path to a custom server configuration file
--vc-executionForce-enable generating Verifiable Credentials for all executions
--no-vc-executionDisable generating Verifiable Credentials for all executions
--storage-mode <mode>Override the storage backend (local or postgres)
--postgres-url <url>PostgreSQL connection URL (implies --storage-mode=postgres)

Examples

# Start the control plane with the default configuration
af server

# Run on a custom port
af server --port 9090

# Boot the control plane with a specific config file
af server --config ./agentfield-server.yaml

# Force-enable Verifiable Credentials for all executions
af server --vc-execution

# Disable Verifiable Credentials for all executions
af server --no-vc-execution

# Start with PostgreSQL storage backend
af server --postgres-url postgresql://user:password@localhost:5432/agentfield

Verifiable Credentials

By default, Agentfield generates Verifiable Credentials (VCs) for all reasoner and skill executions. You can control this behavior at three levels:

  1. Server Level - Use --vc-execution or --no-vc-execution flags to set the platform-wide default
  2. Agent Node Level - Set vc_enabled parameter when creating an Agent instance
  3. Function Level - Use vc_enabled parameter in @app.reasoner() or @app.skill() decorators

Priority: decorator → agent node → server flag → platform default (enabled)

Previousaf init
Nextaf dev