@daomar/agentfleet
Advanced tools
Distributed agent orchestration, without a control plane.
AgentFleet is a decentralized, multi-machine coding agent fabric built on top of OneDrive sync. Any enrolled machine can dispatch work. Every machine can execute it. There is no central scheduler, broker, or control plane to keep alive.
AgentFleet lets you fan out coding tasks across all of your machines simultaneously. Submit a task from any machine, and every machine running AgentFleet will see the same task, execute it locally with its installed coding agent, and write back machine-scoped results.
How it works:
~/.agentfleet/.tasks/ directory.agentfleet run picks up that task independently.output/ directory with hostname-prefixed files to avoid collisions.No servers, no databases, no control plane — just distributed coordination through sync.
npx -y @daomar/agentfleet run
On first run, AgentFleet automatically creates agentfleet and dma shortcut commands in your npm global directory, so you can use either command directly without restarting the terminal. If you've already installed globally via npm install -g @daomar/agentfleet, shortcut creation is skipped.
Or install globally:
npm install -g @daomar/agentfleet
agentfleet run
Start AgentFleet on this machine. On first use, it auto-detects OneDrive and creates the necessary symlinks and config. On subsequent runs, it loads the existing config and starts the task watcher. Only tasks that arrive after AgentFleet starts will be processed — existing tasks are never replayed, even after a restart or on a new machine.
agentfleet run
Options:
--poll-interval <seconds> — Polling interval (default: 10)--concurrency <number> — Maximum concurrent agent processes (default: 1)--daemon or -d — Run as a background daemon process (detached from the terminal)--log-file <path> — Log file path when running as a daemon (default: ~/.agentfleet/agentfleet.log)Run AgentFleet in the background so it persists after you close the terminal:
agentfleet run --daemon
This spawns a detached process, writes its PID to ~/.agentfleet/agentfleet.pid, and redirects all output to ~/.agentfleet/agentfleet.log. Only one daemon instance is allowed at a time.
To use a custom log file:
agentfleet run --daemon --log-file /tmp/agentfleet.log
Note: Only one AgentFleet instance is allowed at a time, whether foreground, daemon, or auto-start.
For machines that need AgentFleet to run permanently, set up auto-start on login:
npx -y @daomar/agentfleet install
This installs a platform-appropriate auto-start registration that runs npx -y @daomar/agentfleet run -d using the latest published version. The daemon starts immediately after installation. No administrator privileges are required on supported platforms.
AgentFleet, starts on login, and re-triggers after wake from sleep or hibernation.dev.daomar.agentfleet, starts on login, and starts the daemon immediately after installation.Uninstall auto-start:
npx -y @daomar/agentfleet uninstall
This stops the running instance and removes the current platform's auto-start registration.
Stop the running AgentFleet instance:
agentfleet stop
This sends SIGTERM to the running process and cleans up the PID file. Works for all run modes (foreground, daemon, auto-start). If auto-start is configured, AgentFleet will restart on the next login. On Windows, Scheduled Task mode also restarts after wake from sleep or hibernation.
AgentFleet checks both OneDrive for Business and personal OneDrive accounts.
~/Library/CloudStorage/OneDrive* first, then legacy ~/OneDrive* paths.This creates ~/.agentfleet/ and points its tasks/ and output/ directories at your selected OneDrive workspace under AgentFleet/.
Create a task that every enrolled machine will execute:
agentfleet submit --prompt "Add error handling to all API endpoints" --title "Error handling" --working-dir "C:\work\myproject"
Options:
--prompt <text> — The instruction for the coding agent (required)--title <text> — Short task title--working-dir <path> — Working directory for the agent (default: current directory)--agent <command> — Override the default agent command templateShow version info, running AgentFleet process info (PID, mode, log file), and list all tasks with their machine results:
agentfleet status
The status output shows:
View details for a specific task:
agentfleet status task-20260402120000-abc123
~/.agentfleet/
├── config.json # Local machine config (not synced)
├── processed.json # IDs of tasks already executed on this machine
├── agentfleet.pid # PID file (present when running in any mode)
├── agentfleet.log # Log file (daemon and auto-start modes)
├── tasks/ → OneDrive # Symlink to the selected <OneDrive>\AgentFleet\tasks
│ ├── task-001.json
│ └── task-002.json
└── output/ → OneDrive # Symlink to the selected <OneDrive>\AgentFleet\output
├── task-001/
│ ├── DESKTOP-A-result.json
│ ├── DESKTOP-A-stdout.log
│ ├── LAPTOP-B-result.json
│ └── LAPTOP-B-stdout.log
└── task-002/
└── ...
Platform-specific auto-start files live outside ~/.agentfleet/:
~/.agentfleet/start-agentfleet.vbs~/Library/LaunchAgents/dev.daomar.agentfleet.plistAgentFleet is designed with a zero-infrastructure security model:
This architecture means AgentFleet inherits the security, compliance, and data residency guarantees of your existing OneDrive and Microsoft 365 environment — with nothing additional to audit, secure, or maintain.
{
"id": "task-20260402120000-abc123",
"title": "Add error handling",
"prompt": "Add try-catch blocks to all API route handlers...",
"workingDirectory": "C:\\work\\myproject",
"createdAt": "2026-04-02T12:00:00Z",
"createdBy": "DESKTOP-A"
}
Task files are immutable once written. AgentFleet only processes tasks that arrive after the daemon starts — old tasks are never replayed, ensuring safe restarts and new machine onboarding.
Build the CLI:
npm run build
Run the automated test suite:
npm test
The test suite covers task-watcher startup behavior, shortcut registration, Windows scheduled-task and macOS LaunchAgent auto-start behavior, daemon management, run/install/stop/uninstall commands, CLI branding, bootstrap, OneDrive detection, provider selection, result writing, and legacy workspace migration.
A browser-based dashboard is available at https://agentfleet.daomar.dev/.
Open https://agentfleet.daomar.dev/ in your browser and sign in with the Microsoft account that owns the OneDrive where AgentFleet is installed.
Important: Sign in with the same Microsoft account used by your machines' OneDrive sync. If your OneDrive is linked to
user@example.com, log in with that account.
localStorage for persistent login across browser sessions and PWA reopensFiles.Read, Files.ReadWrite, and User.Read (delegated — only the signed-in user's files are accessible)workingDirectory field is not exposed in the UI; an optional agent command can be specified by power usersiOS (Safari): Open https://agentfleet.daomar.dev/ → tap the Share button → Add to Home Screen
Android (Chrome): Open https://agentfleet.daomar.dev/ → tap the ⋮ menu → Add to Home screen (or wait for the install prompt)
The web dashboard uses a pre-registered Microsoft Entra ID application:
| Property | Value |
|---|---|
| Client ID | b94f9687-adcf-48ea-9861-c4ce4b5c01a0 |
| Tenant | 91dde955-43a9-40a9-a406-694cffb04f28 (multi-tenant) |
| Sign-in audience | AzureAD and personal Microsoft accounts |
| Redirect URIs | https://agentfleet.daomar.dev/, http://localhost:5173/ |
| Permissions | Files.Read, Files.ReadWrite, User.Read (delegated) |
To self-host the dashboard, register your own Entra ID app and update web/public/config.js with your clientId. See Microsoft documentation for app registration steps.
cd web
npm install
npm run dev # Start dev server at http://localhost:5173
npm run build # Production build to web/dist/
npm test # Run unit tests (Vitest)
AgentFleet is free and open-source. If it helps your workflow, consider supporting the project:
| PayPal (international) | WeChat Pay (国内用户) |
 |  |
 hjunxu |
All supporters will be recognized on this page.
ISC
FAQs
Distributed agent orchestration, without a control plane.
The npm package @daomar/agentfleet receives a total of 13 weekly downloads. As such, @daomar/agentfleet popularity was classified as not popular.
We found that @daomar/agentfleet demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket Firewall blocks malicious VS Code and Open VSX extensions before install, protecting developers from compromised editor marketplaces.
Research
More than 140 Mastra npm packages were compromised in a supply chain attack that used a typosquatted dependency to deliver a cross-platform infostealer during installation.
Research
/Security News
A new npm package tests AI malware scanners with prompt injection, safety-triggering comments, context flooding, and obfuscated JavaScript.