Agw

中文文档 | Documentation

Agw is an AssS (Agent as a Service) platform and agent gateway that allows users to create custom agents and integrate existing external agents (such as Claude Code and Codex).

In addition, Agw offers Cron Job and Agent Workflow capabilities, which can be used to create scheduled tasks, recurring tasks, and orchestrate Agents (currently, only simple orchestration is supported).

This project is primarily based on MAF.

Tech Stack

Backend:

• .NET 10
• ASP.NET Core
• Entity Framework Core
• Microsoft.Agents.AI
• Serilog + OpenTelemetry

Frontend:

• Next.js 16 App Router
• React 19
• Tailwind CSS 4
• Shadcn 4 （Radix UI）

Usage

Start the backend from the repository root:

dotnet restore Agw.slnx
dotnet run --project src/backend/Agw.Host

The development backend listens on http://localhost:5015. On the first run, open http://localhost:5015/setup to choose the database provider, connection string, and optional API key. The setup process seeds the database and writes the local appsettings.setup.json file. If an API key is configured, backend /api requests must include the X-API-Key header.

Start the frontend in another terminal:

cd src/frontend/web
pnpm install
pnpm dev

Open http://localhost:3000 after both services are running. The Next.js dev server proxies /api/* and /openapi/* to the backend, using BACKEND_API_BASE_URL, then NEXT_PUBLIC_API_BASE_URL, then http://localhost:5015.

Typical local workflow:

1. Complete the first-run setup page if the backend redirects to /setup.
2. Configure providers, models, and model-provider links under Providers, Models, and Model Providers.
3. Create agents under Agents, then attach MCP tool servers, tools, skills, or integration-backed apps as needed.
4. Use Chat or Projects to run agent sessions and review persisted task history.
5. Use Agentflows for multi-agent orchestration and Jobs for scheduled or recurring task execution.

Screenshots

Below are screenshots of the main Agw UI pages:

Providers

Agents

Tools & MCP

Skills

Integrations

Chat Conversation

Chat Workspace Files

Projects

Jobs

Agentflows

Architecture

Agw uses a domain-based, modular monolithic architecture. src/backend/Agw.Host serves as the entry point for the ASP.NET Core application and is responsible for assembling the various modules; the frontend is located in the src/frontend/web directory.

A typical backend flow is:

Controller -> AppService / RuntimeService -> DomainService -> IRepository / IUnitOfWork -> EF Core

Module Overview:

flowchart BT
    Agw.Host
    Agw.Infrastructure

    subgraph Core
        direction BT
        Agw.Jobs
        Agw.A2A
        Agw.Agents
        Agw.Providers
        Agw.Skills
        Agw.Tools
        Agw.Integrations
        Agw.Tasks

        %% Relationships
        Agw.Agents --> Agw.Jobs
        Agw.Agents --> Agw.A2A


        Agw.Providers --> Agw.Agents
        Agw.Skills --> Agw.Agents
        Agw.Tools --> Agw.Agents
        Agw.Integrations --> Agw.Agents


        Agw.Tasks --> Agw.Agents
        Agw.Tasks --> Agw.Jobs
        Agw.Tasks --> Agw.A2A

    end

    subgraph Support
        Agw.Setup[Agw.Setup]
    end

    Agw.Shared 

    Agw.Shared --> Core

    Core --> Agw.Infrastructure
    Support --> Agw.Infrastructure

    Agw.Infrastructure --> Agw.Host


    %% styles
    style Core fill:none,stroke:#333,stroke-dasharray: 5 5
    style Support fill:none,stroke:#333,stroke-dasharray: 5 5

Loading

• Agw.Providers
  Used to manage models and their providers.

• Agw.Agents
  Integrate external agents (such as Claude Code and Codex) and manage custom agents. Custom agents can support the integration of tools, MCPs, and skills.

• Agw.Tools
  Includes built-in Tool and MCP Tool management modules.

• Agw.Skills
  Skill Management Module.

• Agw.Integrations
  External App Integration Module.

• Agw.Tasks
  Agent Conversation and Session Management Module. In AGW, each session corresponds to a task, and each task is associated with a project.

• Agw.Jobs
  Provides the ability to schedule recurring, periodic, and one-time tasks, with support for Cron expressions.

  • One-time task: Once created, it will be disabled after being executed once.

  • Scheduled task: Runs at a specified time and is disabled after execution.

  • Scheduled tasks: Tasks that are repeated at specified times on a regular basis.

• Agw.A2A

Provides an interface for the A2A protocol to external systems.

Documentation

The detailed project docs live under docs/:

• Development Guide: local setup, build/test/lint/format commands, and git hook configuration.
• Architecture: system overview, backend/frontend structure, and core domain concepts.
• Module Organization: layering principles used inside modules.

Configuration

Primary backend settings are in src/backend/Agw.Host/appsettings.json:

{
  "Database": {
    "Provider": "sqlite",
    "ConnectionString": "Data Source=agw.db"
  },
  "OpenTelemetry": {
    "ServiceName": "Agw",
    "ServiceVersion": "1.0.0",
    "OtlpEndpoint": "http://localhost:4317"
  }
}

• Supported database providers are sqlite, postgres, and mysql.
• Keep secrets out of committed config files; prefer environment-variable overrides.
• After backend contract changes, regenerate src/frontend/web/src/api/openapi.d.ts with pnpm gen:openapi.