Agents One
Menu
Chinese Follow releases
HUMAN INTENT × AGENT CAPABILITYAI WORKSPACE / PRE-RELEASE
A robotic hand and a human hand reach toward each other, where human intent meets agent capability

Many agents.
One workspace.

Bring scattered capabilities into one place.
Local and remote agents. Start with a conversation.

YOUR TOOLS.
YOUR CONTEXT.
ONE WORKSPACE.

Keep each tool and its permissions.
Keep the process and the work within reach.

AI AGENT MANAGEMENT & COLLABORATION
Pi / Codex / Claude Code / OpenCode / Hermes

Follow the first release Explore the workspace

01 / CAPABILITIES

Different strengths,one shared workspace.

Keep the agents you know.
Bring conversations, tools and artifacts
together in one place.

I. LOCAL

Native tools. Familiar power.

Connect familiar local tools and the Hermes adapter. Build on existing capabilities without starting over.

II. REMOTE

Remote power. Within reach.

Connect remote agents through a gateway, with local and remote conversations in one workspace.

III. CONTEXT

Give every task a context.

Link a project to its working folder. Give tasks, files and context a clear place to belong.

IV. TRACE

Keep more than the answer.

See conversations, tool calls, history and artifacts together, so you can trace the work and continue it.

02 / THE WORKSPACE

A conversation is the start,not the end of the work.

One request. A traceable process.
An artifact you can keep working with.
Connect the work through conversation.

AGENTS ONE / RESEARCH WORKSPACECONVERSATION → WORK

01 / THE CONVERSATION

Your goal

Organize the project files.
Create a research brief.

Let capabilities serve your work.

Choose the right agent and bring your project context. Replies, tool calls and artifacts stay connected to the conversation.

Project contextNative toolsClear permissions

02 / THE PROCESS

See the answer. See how it happened.

  1. 01
    Read the working files

    Organize context in the linked project folder.

  2. 02
    Inspect tool activity

    See tool activity alongside streaming replies.

  3. 03
    Trace the work back

    Conversations, tasks and artifacts leave a trail you can return to.

03 / THE ARTIFACT

MARKDOWN

Research brief

research-brief.md

Turn a conversation
into work you can build on.

Keep artifacts connected to the conversation. Revisit the sources, make changes, or bring the work into your next task.

  • Background and goals
  • Sources and findings
  • Next steps
Your goal at the center. Your tools within reach.ONE WORKSPACE.
Workspace feature illustration · From one request to work you can continue.Explore the project & source

03 / KEEP YOUR TOOLS

Distinct tools,shared ground.

Connect existing capabilities.
Keep the way you work.

I / LOCAL TOOLS

Familiar tools. Native access.

  • Pi
  • Codex
  • Claude Code
  • OpenCode
  • Hermes

CLI tools keep their models, tools, project instructions and permissions. Hermes connects through its installed local adapter.

II / REMOTE GATEWAY

Remote agents. One connection.

Workspace
Gateway
Remote agent
  • Capabilities
  • Workspace access
  • Run boundaries

Negotiate capabilities through the protocol. Keep remote execution within explicitly authorized workspace boundaries.

Two connection paths. One conversation experience.

Logos identify the respective tools, not partnerships or endorsements.Logo sources & usage notes ↗

04 / HUMAN FIRST

Human intent.Always first.

A good workspace connects capabilities
and respects the boundaries of every task.

YOUR INTENT. YOUR WORK.
I

One interface. Clear permissions.

Local agents retain their permission modes. Project folders define the workspace; remote access follows the authorization granted for the run.

II

Know where your data goes.

Desktop state is stored locally. Your chosen agent and model process requests in their own way. Not all data is guaranteed to stay on your device.

III

Keep the work. Continue it.

Revisit conversation history and artifacts. Backup and restore include validation and rollback safeguards, but user content may still contain sensitive information.

05 / START HERE

Start with the tools you know.

The first public release is in preparation.
Get to know the product. Then start a task.

  1. 01

    Follow the first release.

    The first release is planned for Windows x64. Official Releases are the source for published installers and verification details.

    Check release progress
  2. 02

    Bring your agents.

    Prepare your local tools or a compatible remote gateway. Probe the connection before starting a conversation.

    Read the getting-started guide
  3. 03

    Give the work a context.

    Create a project and link its folder. Choose an agent and bring files, conversations and artifacts together around the task.

    Revisit the workspace

06 / QUESTIONS

Clear answers. Clear boundaries.

Connections, releases and licensing.

Is Agents One a new AI model?

No. It is an AI agent management and collaboration platform, bringing existing local tools and remote agents into one workspace. The selected agent provides the models and tools.

Do I need to give up my existing agents?

No. Pi, Codex, Claude Code and OpenCode keep their CLI capabilities; Hermes connects through a local adapter or a compatible remote gateway. Agents One provides a shared entry point for conversations and tasks. Remote Hermes multi-turn continuation and recall after restart remain experimental.

How do local and remote agents differ?

Local tools run through native CLIs or the Hermes local adapter. Remote agents connect through a compatible Gateway and negotiate capabilities through the protocol. Remote workspace access requires explicit authorization; connecting to the workspace does not grant access to every file.

Can I download a stable release now?

Agents One is currently in pre-release, with no public Release yet. The first public installer is planned for Windows x64. Features and data formats may change. Check the official Releases page ↗ for the latest published information.

Does all data stay on my device?

Desktop state is stored locally, but requests sent to your chosen agent or an external model follow that service's execution model. Project folders and local CLI data also have their own storage locations. Assess data boundaries using the services and permission modes you choose.

Does visible source mean I can ignore the license?

No. Use, modification, distribution and commercial-use conditions are governed by the LICENSE included with the version you use. Third-party components and assets retain their own terms. Please read the project license ↗ and related notices before using the source.

ONE WORKSPACE. MANY AGENTS.

Bring capabilities together,
keep creation human.

Agents One · AI agent management & collaboration

Follow the first release View the GitHub project
WINDOWS x64 / PRE-RELEASE