
Product
Socket Firewall Now Blocks Malicious VS Code and Open VSX Extensions
Socket Firewall blocks malicious VS Code and Open VSX extensions before install, protecting developers from compromised editor marketplaces.
@daomar/agentfleet
Advanced tools
Fan out coding tasks across all your machines — no servers, no config, no infrastructure.
Demo GIF coming soon — see Quick Start to try it now
Most distributed task systems need servers, brokers, or cloud infrastructure. AgentFleet needs none of that — it uses OneDrive sync as the coordination layer.
| AgentFleet | SSH Scripts | Ansible | Cloud CI | |
|---|---|---|---|---|
| Infrastructure | None (OneDrive) | SSH server per machine | Control node + SSH | Cloud provider account |
| Network | No inbound connections | Open SSH ports | Open SSH ports | Internet access |
| Security | Inherits M365 policies | Key management | Key management | Cloud IAM |
| Setup Time | < 1 minute | Hours | Hours | Minutes to hours |
| AI Agent Support | Built-in (any CLI agent) | Manual scripting | Custom playbooks | Custom pipelines |
| Works Behind Firewalls | Yes | No | No | Depends |
Zero Servers — No schedulers, no brokers, no databases. OneDrive is the only moving part.
Zero Config — Run one command and you're live. AgentFleet auto-detects OneDrive and sets up everything.
Enterprise Security — No tunnels, no open ports, no data leaves your Microsoft 365 tenant. Your IT policies already cover it.
# 1. Start AgentFleet on each machine (auto-detects OneDrive)
npx -y @daomar/agentfleet run
# 2. Submit a task from any machine
agentfleet submit --prompt "Add error handling to all API endpoints" --title "Error handling"
# 3. Results appear on every machine — check them
agentfleet status
That's it. Every machine running agentfleet run picks up the task, executes it with its locally installed coding agent, and writes back results.
Machine A Machine B Machine C
┌──────────┐ ┌──────────┐ ┌──────────┐
│agentfleet│ │agentfleet│ │agentfleet│
│ run │ │ run │ │ run │
└────┬─────┘ └────┬─────┘ └────┬─────┘
│ │ │
└───────────┐ ┌──────────┘ ┌──────────────────────┘
▼ ▼ ▼
┌─────────────────────────────┐
│ OneDrive Sync Layer │
│ ┌───────┐ ┌──────────┐ │
│ │tasks/ │ │ output/ │ │
│ └───────┘ └──────────┘ │
└─────────────────────────────┘
~/.agentfleet/.tasks/ directory.agentfleet run picks up that task independently.output/ with hostname-prefixed files — no collisions.Run the same coding agent prompt on a project across all your development machines simultaneously. Each machine applies its own agent (Claude Code, GitHub Copilot CLI, Cursor, etc.) and writes independent results, so you can compare outputs side by side.
agentfleet submit \
--prompt "Review this codebase for security vulnerabilities and suggest fixes" \
--title "Security audit" \
--working-dir /path/to/project
Fan out a large refactoring task across multiple machines, each working on its own local clone of the project. Useful when you have multiple workstations or want to try different agent configurations in parallel.
agentfleet submit \
--prompt "Migrate all class components to functional components with hooks" \
--title "React migration" \
--working-dir /path/to/project
A browser-based dashboard at agentfleet.daomar.dev lets you submit tasks, monitor nodes, and view results from any device — including mobile (installable as PWA).
npx -y @daomar/agentfleet run
On first run, AgentFleet creates an agentfleet shortcut in your npm global directory.
npm install -g @daomar/agentfleet
agentfleet run
Start AgentFleet on this machine:
agentfleet run
Options:
--poll-interval <seconds> — Polling interval (default: 10)--concurrency <number> — Max concurrent agent processes (default: 1)--daemon or -d — Run as background daemon--log-file <path> — Log file path for daemon mode (default: ~/.agentfleet/agentfleet.log)agentfleet run --daemon
Spawns a detached process, writes PID to ~/.agentfleet/agentfleet.pid. Only one instance allowed at a time.
npx -y @daomar/agentfleet install # Install auto-start
npx -y @daomar/agentfleet uninstall # Remove auto-start
AgentFleet, triggers on login and wakedev.daomar.agentfleetagentfleet submit --prompt "..." --title "..." --working-dir /path
Options:
--prompt <text> — Instruction for the coding agent (required)--title <text> — Short task title--working-dir <path> — Working directory (default: cwd)--agent <command> — Override agent command templateagentfleet status # Overview of all tasks
agentfleet status task-20260402-abc123 # Detail for one task
agentfleet stop
~/.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)
├── agentfleet.log # Log file (daemon and auto-start modes)
├── tasks/ → OneDrive # Symlink to <OneDrive>\AgentFleet\tasks
│ ├── task-001.json
│ └── task-002.json
└── output/ → OneDrive # Symlink to <OneDrive>\AgentFleet\output
├── task-001/
│ ├── DESKTOP-A-result.json
│ ├── DESKTOP-A-stdout.log
│ └── LAPTOP-B-result.json
└── task-002/
└── ...
Platform-specific auto-start files:
~/.agentfleet/start-agentfleet.vbs~/Library/LaunchAgents/dev.daomar.agentfleet.plist{
"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. Only tasks arriving after the daemon starts are processed.
AgentFleet checks both OneDrive for Business and personal accounts:
~/Library/CloudStorage/OneDrive* is checked first, then ~/OneDrive*.Sign in at agentfleet.daomar.dev with the Microsoft account that owns the OneDrive.
localStorageFiles.Read, Files.ReadWrite, User.Read (delegated)| 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) |
iOS: Safari → Share → Add to Home Screen
Android: Chrome → ⋮ → Add to Home Screen
cd web
npm install
npm run dev # Dev server at http://localhost:5173
npm run build # Production build to web/dist/
npm test # Unit tests (Vitest)
npm run build # Build CLI
npm test # Run CLI tests
cd web && npm test # Run web tests
See CONTRIBUTING.md for full development setup.
AgentFleet is free and open-source. If it helps your workflow, consider supporting the project:
| PayPal (international) | WeChat Pay (国内用户) |
![]() | ![]() |
![]() hjunxu |
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.