coding cli management

AI Community

Skill notes

Config File

Path: ~/coding-cli-config.json enabled · cli · Meaning false · any · Admin declined; use normal task flow true · "claude" / "gemini" / "qodercli" · Active — use this CLI

Step 1: First-Time Detection (before assigning a coding task)

Run when ~/coding-cli-config.json does not exist: If no CLIs are available (available array is empty): Proceed with normal task assignment (Worker codes on their own). If CLIs are available, ask the admin via the primary channel or Matrix DM — in the language the admin used: I found the following AI coding CLI tools available: [list]. Would you like to enable CLI delegation mode? Workers will generate coding prompts, and I'll use the CLI tool to make the code changes. Reply with the tool name (claude/gemini/qodercli) to enable, or 'no' to have workers code on their own.

Step 2: Assigning a Coding Task (CLI mode enabled)

When coding-cli-config.json has enabled: true: Ensure the Worker has the coding-cli skill. Check workers-registry.json: If coding-cli is missing, distribute it: Add a "Coding CLI Mode" section to spec.md (see template below).

Step 3: Handling a coding-request: Message

When a Worker sends a message containing coding-request: (in their Worker Room or a Project Room): Parse the message: Execute: On success — send to Worker in the same Room: On failure (exit ≠ 0 or timeout) — see Step 4.

Step 4: Handling Failure

Notify Worker in the task Room: Notify Human Admin via primary channel (see channel-management skill "Sending Messages to Primary Channel"): Record in config (optional, for heartbeat diagnostics):

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: First-Time Detection (before assigning a coding task)

Run when `~/coding-cli-config.json` does not exist: If no CLIs are available (`available` array is empty): Proceed with normal task assignment (Worker codes on their own). If CLIs are available, ask the admin via the primary channel or Matrix DM — in the language the admin used: I found the following AI coding CLI tools available: [list]. Would you like to enable CLI delegation mode? Workers will generate coding prompts, and I'll use the CLI tool to make the code changes. Reply with the tool name (claude/gemini/qodercli) to enable, or 'no' to have workers code on their own.

02
Step 2: Assigning a Coding Task (CLI mode enabled)

When `coding-cli-config.json` has `enabled: true`: Ensure the Worker has the `coding-cli` skill. Check `workers-registry.json`: If `coding-cli` is missing, distribute it: Add a "Coding CLI Mode" section to spec.md (see template below).

03
Step 3: Handling a coding-request: Message

When a Worker sends a message containing `coding-request:` (in their Worker Room or a Project Room): Parse the message: Execute: On success — send to Worker in the same Room: On failure (exit ≠ 0 or timeout) — see Step 4.

04
Step 4: Handling Failure

Notify Worker in the task Room: Notify Human Admin via primary channel (see channel-management skill "Sending Messages to Primary Channel"): Record in config (optional, for heartbeat diagnostics):

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.