lfg

lfg is a Bun/TypeScript Grok Build plugin workspace for an OMO-like agent hierarchy. The active plugin package is plugins/lfg/. Shared agent/runtime building blocks are vendored under plugins/lfg/vendor/omo-standalone/, then re-exported into this workspace through plugins/lfg/vendor-links/* and the root TypeScript path aliases.

The repo goal is straightforward: ship lfg and ulw as Grok-facing CLI/plugin surfaces while keeping the underlying orchestration model close to OMO semantics—Sisyphus orchestration, Prometheus planning, Atlas checklist execution, Hephaestus deep work, category routing, hooks, MCP tools, and durable .lfg/ state—without pretending unfinished Grok-native host behavior is already complete.

Current product shape

• Runtime: Bun/TypeScript only. The old Python packaging/runtime layer has been removed.
• Plugin package: plugins/lfg/ contains the CLI entrypoints, MCP server, hook registration, skills, smoke runner, and runtime implementation.
• Vendored OMO source: plugins/lfg/vendor/omo-standalone/ is the pinned upstream TypeScript workspace used as the shared logic base.
• Workspace bridges: plugins/lfg/vendor-links/* re-export vendored packages so the root workspace can import @oh-my-opencode/* consistently.
• Command surface: lfg is the main CLI; ulw is the ultrawork-oriented alias.
• State: runtime and execution state lives under .lfg/.

Workspace layout

./
  package.json
  tsconfig.json
  README.md
  ROADMAP.md
  docs/
  tests/
  plugins/lfg/
    bin/
    hooks/
    skills/
    src/
    vendor-links/
    vendor/omo-standalone/

Important paths:

• plugins/lfg/bin/lfg.ts — active TypeScript CLI gateway
• plugins/lfg/bin/ulw — ultrawork wrapper alias
• plugins/lfg/bin/lfg-mcp.ts — MCP stdio server
• plugins/lfg/src/runtime-ts/index.ts — runtime router
• plugins/lfg/src/mcp-ts/ — MCP implementation
• plugins/lfg/src/hooks-ts/ — hook implementation
• plugins/lfg/bin/self-test.ts — canonical local self-test

Install and local development

Grok marketplace path

Primary product path:

1. Open Grok Build.

2. Open /plugins.

3. Add the marketplace source:

   https://raw.githubusercontent.com/islee23520/lfg/main/.grok/plugins/marketplace.json
   

4. Install lfg.

5. Enable the plugin.

Local workspace path

For repository development, use the Bun workspace directly.

bun install
bun run --filter './plugins/lfg' build

If you refresh vendored package bridges after updating plugins/lfg/vendor/omo-standalone/, run:

bun --cwd plugins/lfg run refresh:vendor-links

Runtime commands

Representative commands from the active TS runtime:

plugins/lfg/bin/lfg agents list
plugins/lfg/bin/lfg route --category quick --task "execute a bounded task"
plugins/lfg/bin/lfg spawn sisyphus-junior --category quick --task "fix the smoke gate"
plugins/lfg/bin/lfg plan create "ship docs cleanup" --steps "inspect;implement;verify"
plugins/lfg/bin/lfg atlas start-work --plan-id <plan-id>
plugins/lfg/bin/lfg hephaestus goal "stabilize vendor bridge"
plugins/lfg/bin/lfg hyperplan "review Grok spawn adapter"
plugins/lfg/bin/lfg doctor
plugins/lfg/bin/lfg doctor state schema check
plugins/lfg/bin/lfg team preflight
plugins/lfg/bin/lfg setup
plugins/lfg/bin/lfg setup check

Verification

Local TypeScript/Bun gates:

bun test plugins/lfg/src/runtime-ts plugins/lfg/src/mcp-ts plugins/lfg/src/hooks-ts plugins/lfg/src/smoke-ts plugins/lfg/test-utils
bun plugins/lfg/bin/self-test.ts
plugins/lfg/bin/lfg --json doctor

Manual/environment-specific Grok host gates remain documented in docs/SMOKE.md. Those gates should stay explicit; do not silently promote them into "done" claims without recorded evidence.

What stays intentionally explicit

• Grok-native named child spawning still depends on host/manual evidence.
• Oracle-style review and release-readiness discipline remain part of the product contract.
• Vendored OMO packages are a real implementation dependency, not a marketing footnote; docs should mention them whenever shared runtime behavior is described.

References

• ROADMAP.md — current forward roadmap from the TypeScript cutover baseline
• docs/ARCHITECTURE.md — runtime and agent-system details
• docs/SMOKE.md — smoke and manual verification procedures
• docs/TEST_RULES.md — gate classification rules