Luna Foundry Multiagent

VS Code / Cursor extension that delivers Luna MacroFlow on two surfaces: Copilot Chat and Grok Build.

Luna is your Sherpa Guide — less cognitive load, clear ritual, drive home to a delivered product with proof.

What this product is (today)

Luna Foundry Multiagent is not a second chat model inside VS Code that replaces Grok or Copilot.

It is a delivery layer that:

1. Deploys one MacroFlow skill/agent pack into your workspace for Copilot Chat / Cursor (.github/ + .cursorrules).
2. Installs the same pack into Grok Build as the Luna Grok plugin.
3. Opens clean terminals so Grok Build (and the Grok CLI) start with a sane PATH — Build profiles auto-start the TUI; shell profiles do not.

After setup, MacroFlow runs where those hosts run skills/agents:

The extension does not own a separate full MacroFlow webview “app” as the primary product experience.

What you get (commands that exist)

From the Command Palette (Luna: …) — these are the registered commands:

Legacy aliases: Create MacroFlow (wsl) / older Grok Build (wsl) titles map to the Build (wsl) terminal.

Small command surface on purpose: unify the pack + get you into Grok/Copilot, not reinvent the agent host.

MacroFlow ritual (real content)

The pack deploys Luna + phase skills. The working phases you use in chat/TUI:

Constitution  →  Clarify  →  Workforce

Luna is the Sherpa/orchestrator agent in the pack (alongside Constitution, Clarify, Workforce agents).

Waypoint Check (Luna language): short collect → check → recover → move forward stop — at handoffs, after verification, when stuck, before claiming done.

On Grok Build, also use host features that already exist (e.g. /goal) alongside MacroFlow — they stack; MacroFlow is not a fork of Grok’s product.

Azure DevOps / enterprise board projection is internal dogfood for now — not part of the default public path. Public product mode: pack + Git + proof; no invent-the-plan only in ADO.

Dual surface (one pack)

SoT = skills/agents/instructions from luna-foundry-config, bundled for install. End users install VSIX or marketplace plugin; they do not need private SoT repos.

v1.0.26193+: full skill/agent parity between surfaces (no intentional “thin” Grok subset).

Pack contents (what Setup / plugin install)

Typical deploy includes (names evolve; inspect after Setup or grok plugin details luna-foundry):

• Agents: Luna, Constitution, Clarify, Workforce
• Skills: MacroFlow (+ constitution / clarify / workforce), ensure-* (incl. ensure-grok-build), content-creator*, forensic-, gnomah-, ado-wbs (when packaged), xAI bridge skills (voice / imagine / collections / agent-tools), and related pack skills

Exact set = what was last built into the VSIX / plugin. Rebuild SoT → rebundle → reinstall if you change skills.

Getting started (accurate path)

1. Install the extension (Marketplace when published, or VSIX).
2. Luna: Setup Unified Workspace.
3. Use Copilot Chat with the deployed agents/skills or open Grok Build terminal / install Luna plugin.
4. In chat/TUI: start Constitution / MacroFlow (e.g. ask Luna to start MacroFlow, or use pack slash skills such as /constitution where the host supports them).
5. Ship work with proof; use Waypoint Check before claiming done.

Grok plugin install

Marketplace (public):

grok plugin marketplace add "https://github.com/acornsoft/luna-foundry-multiagent"
grok plugin install luna-foundry --trust

Bundled from the extension: Command Palette → Install Luna Plugin for Grok.

Builders (monorepo SoT live layout):

PLUGIN="src/apps/luna-foundry-config/live/grok-plugin/luna-foundry"
grok plugin validate "$PLUGIN"
grok plugin install "$(cd "$(dirname "$PLUGIN")" && pwd)/luna-foundry" --trust

Prefer pure x.y.z in plugin.json (no -preview.N in the version string). After pack changes: npm run build:grok-plugin in luna-foundry-config, then reinstall plugin / VSIX.

Installation

VSIX (current practical path)

code --install-extension .\luna-foundry-multiagent-1.0.26195.vsix --force

Then: Setup Unified Workspace · optionally Install Luna Plugin for Grok.

Development (this monorepo)

cd src/apps/luna-foundry-multiagent
npm install
npm run package        # pure x.y.z VSIX
# optional: npm run package:pre   # vsce pre-release flag only

Architecture (as implemented)

Diagrams under images/ (phases, agents, architecture) illustrate the ritual and pack model, not a separate SaaS console.

Configuration

Settings live under lunaFoundry.* where contributed (see package.json / Settings UI). Typical concerns: API base URL, model preference, voice/video toggles when enabled, agent preference.

API keys should use VS Code Secrets — never commit keys.

Cost-aware use: Prefer focused Grok Build sessions, early Constitution, and avoid unbounded loops. Local API proxies are optional for cheap iteration when you do not need full Grok fidelity.

Design principles (grounded)

• One pack, two surfaces — Copilot and Grok Build share MacroFlow skills/agents.
• Sherpa, not tool soup — ritual first; terminals and install are how you reach the rope.
• Hosts do the agent work — we deploy and launch; Copilot/Grok execute.
• Private SoT, public install — builders change luna-foundry-config; users get VSIX/plugin.
• Honest scope — enterprise ADO mode and advanced continuity (full NAB/SIGNALS/Realm productization) are not claimed as fully shipped public UX here.

Roadmap (direction, not pretend features)

What this README is not claiming

• That every idea in older docs (full voice-first NAB product, Event Hubs Realm store, “Start MacroFlow” as a single extension chat that replaces Copilot/Grok) is fully live as the default path.
• That ADO enterprise board projection is on by default for public users.
• That install paths under private monorepo folders are required for marketplace users.

For release notes and exact deltas, see CHANGELOG.md.

Luna Foundry Multiagent — dual-surface delivery of MacroFlow so builders use Grok Build and Copilot with one Sherpa ritual.

Maintained by Acornsoft · Powered by xAI Grok

Issues: github.com/acornsoft/luna-foundry-multiagent/issues