nexi-workflow-dialogue

Diagnose stuck or misbehaving autonomous workflow runs in the Nexi agency engine.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill nexi-workflow-dialogue-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexi-workflow-dialogue
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/.opencode/skills/nexi-workflow-dialogue
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill nexi-workflow-dialogue-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous workflow runs in Nexi's agency engine can get stuck in pending, stop reasoning, misreport progress to the UI, or lose their history, and this Skill provides the mental model and debugging checklist to pinpoint whether the cause is autonomy gating, event wiring, persistence, or an actual bug. ## Core Features & Use Cases - Pass Pipeline Map: Documents the Planner, Research, ToolOperator, Verifier, Reflection, and Report passes implemented as (run, ctx) functions in workflow_engine.py, so you upgrade a pass in place instead of restructuring. - Autonomy Gating Reference: Explains NEXI_AGENCY_AUTONOMY and NEXI_AGENCY_MODE (locked | manual | supervised | autonomous_safe) so you check intended gates before assuming a crash. - Run Lifecycle & Persistence: Covers WorkflowRun status transitions, JSONL persistence at data/nexi/agency/workflow_runs.jsonl, register_workflow_type(), and the EVENT_SINK HUD hook. - Use Case: A run appears stuck in pending — instead of digging through the runner, you check autonomy_mode() first and discover the mode is manual, meaning the run is intentionally waiting for a human decision. ## Quick Start Ask the assistant to debug why a Nexi agency workflow run is stuck in pending and not reasoning, using the workflow engine's autonomy flags and event sink wiring.

Frequently Asked Questions about nexi-workflow-dialogue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is my Nexi agency workflow run stuck in pending?

A run stuck in pending is usually gated by autonomy_mode(), not crashed. Check NEXI_AGENCY_MODE: locked and manual modes intentionally wait for a human decision before the runner proceeds.

Why is the Nexi workflow engine not reasoning with the Gemini brain?

When NEXI_AGENCY_AUTONOMY is unset or false, passes use deterministic stubs instead of the Gemini brain, keeping runs safe, offline, and test-stable. Set the flag to 1, true, yes, or on to enable real reasoning.

How do I add a new workflow type to the Nexi agency engine?

Register it with register_workflow_type() by providing a WorkflowDefinition with runner, continuer, canceller, and restart_policy. Built-in types include router_audit, codebase_research, test_generation, and integration_plan.

Why is the Nexi UI not showing workflow run progress?

Check that EVENT_SINK is wired to engine/ui_event_bridge.py; it is a no-op callable by default. Events still fire regardless, since _publish_event prints [NEXI_AGENCY] lines even when the HUD hook is disconnected.

Where does the Nexi workflow engine persist run history?

Runs persist to JSONL at data/nexi/agency/workflow_runs.jsonl via _persist(run), so state survives process restarts. A run that lost its history usually means this file was never written, not that memory was cleared.