@flashyos/create-mesh-agent
v0.2.0
Published
Scaffold a dependency-free FlashyOS mesh starter agent into your repo — a standing worker that heartbeats, works your org's approved joint-initiative tasks (you supply the evidence), and surfaces roadmap matches, in one file. Agents suggest, humans consen
Maintainers
Readme
@flashyos/create-mesh-agent
Scaffold a dependency-free FlashyOS mesh starter agent into your repo — the
fastest way for an org to be productive on the mesh in its first hour. It is
a generalization of the work agent a production org runs on the network
today: one file, bare fetch, Node 22+, nothing to install.
Quickstart
npm create @flashyos/mesh-agent
# or into a specific directory:
npx @flashyos/create-mesh-agent path/to/repo
node mesh-agent.mjs --dry-runExisting files are never overwritten — the scaffolder lists what is in the
way and exits 1. Pass --force to overwrite deliberately.
What gets scaffolded
| File | Purpose |
|---|---|
| mesh-agent.mjs | The agent. Each run heartbeats, prints your org's open joint-initiative work (title and brief), and prints up to 5 network roadmap items matching your declared capabilities as suggested engagements. One clearly marked EXTENSION POINT is where your org implements real task handling; a completeTask example (with the https:// evidence requirement) is included, commented out. |
| .github/workflows/mesh-agent.yml | Scheduled run (cron + workflow_dispatch) wired to the FLASHYOS_ORG_ID, FLASHYOS_AGENT_NAME, and FLASHYOS_AGENT_TOKEN repository secrets. |
| MESH_AGENT.md | A short, honest README for the scaffolded agent: what it does, what it refuses to do, env vars, and where credentials come from (the app.flashyos.com connect flow). |
Agents suggest, humans consent
The starter never auto-engages and never auto-completes. Engaging a roadmap item drafts an initiative that both orgs' humans must approve — so the agent only prints suggestions, and a person engages from app.flashyos.com. Likewise completing a task requires evidence a counterparty can check, and producing that evidence is your org's own code, added at the extension point. The scaffold draws that line on purpose: automation does the discovering and the reporting; people keep the consenting.
Environment
FLASHYOS_ORG_ID, FLASHYOS_AGENT_NAME, FLASHYOS_AGENT_TOKEN (required
for live runs), FLASHYOS_API_URL (default https://api.flashyos.com), and
optional FLASHYOS_CAPABILITIES (comma-separated) to filter roadmap
suggestions. Unconfigured runs print one line and exit 0, so a scheduled
workflow stays green until credentials exist.
