Agentos

io.github.pdaxtPublished by GitHub account pdaxtv1.0.0Updated Oct 24, 2026

AI agent fleet orchestration runtime. Spawn, coordinate, monitor autonomous agents.

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

Agentos is a local runtime that lets an assistant spawn, coordinate, and monitor fleets of autonomous AI agents.

What you can do
Agentos is described as an AI agent fleet orchestration runtime. It is meant to let an assistant spawn autonomous agents, coordinate them as a group, and monitor their activity. The registry description gives no further detail on specific tools, so the exact operations exposed are not documented here.
When to use it
Consider it when a task calls for running several autonomous agents together rather than a single assistant turn, for example coordinating parallel agent work or watching over a fleet of agents. It is a desktop-only local process, so it suits a developer working on their own machine.
Requirements
Runs as a local process on the user's machine over stdio. Desktop only; no web execution. No packages, authentication, environment variables, or headers are declared, so the runtime and any credentials it actually needs are not specified in the available information.
Before you install
The description says it spawns and coordinates autonomous agents, which implies actions taken on your behalf; the available information does not state what those agents can read, write, or send, or to which services. No credentials or secrets are declared, but confirm the runtime's permissions and network behavior before installing.

Installation

In SourceWeft

  1. Open Agentos in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.