Agents
Define an agent with instructions, a model, and tools, or connect an existing external agent CLI.
AGW · A self-hosted agent workspace
Connect a model or an existing Claude Code, Codex, or Pi setup. Organize conversations and files by project, assign work to different agents, and schedule tasks after verifying them.
Custom agents · Claude Code · Codex · Pi
From a conversation to recurring work
Start with one working agent. Add projects, tools, and automation as you need them.
Define an agent with instructions, a model, and tools, or connect an existing external agent CLI.
Organize conversations, files, and Git working directories around projects. Handle approvals and input during execution.
Connect steps such as collecting material, summarizing results, and human review. Run them in order, choose a branch, or process work in parallel.
Run agents and workflows once, at fixed intervals, or on Cron schedules. Inspect records for each attempt.
Equip agents with tools, Skills, MCP, and configured integration connections for the task at hand.
Connect to your Server from a browser, an independent desktop client, or mobile. Choose the entry point that fits your work.
Execution you organize
WORKSPACE / EXECUTION
◇ Files, conversations, and execution records stay organized
You host the Server, data, and workspaces. Model requests go to the provider you configure.
PROJECT / Working directory + context
↓
AGENT / Model · Tools · Skills
↓
CHAT / Execution · Approval · History
↓
AGENTFLOW + JOB / Orchestrate + schedule
Choose your entry point
Choose an installation, initialize the Server, and complete your first model conversation.
From Standalone to Control/Data Plane, learn configuration, authentication, and backups.
Run from source, understand module boundaries, and extend tools and integrations.
Before you start
AGW connects to your configured model providers or invokes external agent CLIs you have set up. Model credits are not included; remote model usage follows the provider’s billing rules.
Full includes a current-user Server daemon and suits a local start. Client connects to an existing Server. Both share an application identity, so install one variant.
Jobs support scheduled and recurring execution, and Agentflows orchestrate multiple steps. Verify the target agent, tool permissions, and inputs first, then inspect execution records. Unattended jobs cannot automatically complete steps requiring human approval or input; adjust the task and permissions before scheduling.
AGW is in active development before 1.0. Database schemas, APIs, and interfaces may change between releases. Read the release notes and back up your data before upgrading.
Get your first agent running.Start with a simple conversation. Bring in your work from there.