Nexus Workflow Studio

Nexus is a visual workflow editor for designing, composing, and exporting AI workflows. You build workflows on a drag-and-drop canvas, connect agents and control-flow nodes, then generate runnable command files for tools such as OpenCode, PI, and Claude Code.

Features

🎨 Visual Workflow Canvas

• Drag-and-drop workflow editing on an infinite canvas
• Auto-layout for quick graph cleanup
• Multi-select, copy/paste, and keyboard shortcuts
• Nested sub-workflows with breadcrumb navigation

🤖 AI-Powered Generation

• AI workflow generation from natural-language descriptions
• AI prompt generation and prompt editing for agent nodes
• Dynamic model discovery from connected providers
• Dynamic tool discovery from the connected OpenCode server

📚 Library, Import, and Export

• Save workflows locally and reload them later
• Save reusable node configurations to the library
• Import and export workflow JSON files
• Generate runnable workflow artifacts for OpenCode, PI, and Claude Code
• Export generated files as a ZIP or write them directly into a target folder

📝 Content and Agent Authoring

• Fullscreen editing for prompts and documents
• Skill, document, and script attachments for richer agent behavior
• Variable mapping and positional parameter mapping for generated workflows
• Agent configuration for model, memory, tools, and temperature

Available nodes

Nexus currently supports 13 workflow node types.

Basic nodes

Node	Purpose
Start	Entry point of the workflow
Prompt	Plain natural-language instruction block used in generated workflow output
Script	Attaches custom script content for skill execution
Agent	Delegates work to an AI agent with model, memory, tools, variables, and parameter mappings
Parallel Agent	Fans work out across multiple downstream agent branches in parallel
Skill	Reusable skill definition that can be attached to agents
Document	Attaches inline or linked documents to agents
Sub Workflow	Embeds a nested workflow, either in same-context mode or agent mode
MCP Tool	Represents an MCP tool call in the workflow
End	Terminal node of the workflow

Control flow nodes

Node	Purpose
If / Else	Conditional branching
Switch	Multi-way branching
Ask User Question	Human-in-the-loop branch selection

Getting started

Requirements

• Node.js >= 18.18

Install and run

npm install
npm run dev

Open the app in your browser at the local Next.js URL shown in the terminal, usually:

http://localhost:3000

Other useful commands

npm run build
npm run start
npm run lint
npm run typecheck

Usage

1. Build a workflow

1. Create or rename your workflow in the header.
2. Drag nodes from the palette onto the canvas.
3. Connect the nodes to define execution flow.
4. Select a node to edit its properties in the properties panel.
5. Use auto-layout to organize larger graphs.

2. Add agent resources

• Attach Skill nodes to agents for reusable capabilities.
• Attach Document nodes to agents for reference material.
• Attach Script nodes to skills when the generated skill should include runnable script files.
• Use parameter mappings when an agent should receive positional arguments such as $1, $2, and $3.

3. Use AI features (optional)

AI features require a running OpenCode server.

npm i -g opencode-ai
opencode serve --cors http://localhost:3000

Then connect from the Nexus header.

OpenCode is only required for AI-powered features such as:

• AI workflow generation
• AI prompt generation and editing
• Dynamic model discovery
• Dynamic tool discovery

The editor itself still works offline for workflow design and export.

Generate workflow files

When your canvas is ready, open the generate/export flow from the app and choose a target:

• OpenCode
• PI
• Claude Code

Nexus generates files based on your workflow name and node connections.

Generated output structure

Depending on the selected target, Nexus writes files under one of these root folders:

• .opencode
• .pi
• .claude

Typical generated files include:

• commands/<workflow-name>.md
• agents/<agent-name>.md
• skills/<skill-name>/SKILL.md
• skills/<skill-name>/scripts/<script-file>
• docs/<document-file>

You can also:

• import workflow JSON back into Nexus for editing
• save workflow layouts and reusable nodes into the library
• preview generated output before exporting

The workflow command name is generated from the workflow title by:

• converting it to lowercase
• replacing spaces with -
• removing unsupported characters

So a workflow named:

My Workflow

becomes:

my-workflow

Run a generated workflow

After exporting the generated files into the target tool's command directory, run the workflow by its generated command name:

/my-workflow [params]

Examples:

/my-workflow
/my-workflow customer-123
/my-workflow customer-123, high-priority, en

Workflow parameters are comma-separated and trimmed.

For example:

/my-workflow 2, 5, 10

maps to:

• $1 = 2
• $2 = 5
• $3 = 10

These positional values can then be passed through agent parameter mappings inside the workflow.

Recommended workflow authoring flow

1. Create the main execution path from Start to End
2. Add Agent, Prompt, and control-flow nodes
3. Attach Skill, Document, and Script nodes where needed
4. Save reusable pieces to the library when they can be reused
5. Generate files for your target environment
6. Run the generated command using /<workflow-name> [params]

Keyboard shortcuts

Shortcut	Action
Ctrl/Cmd + S	Save workflow
Ctrl/Cmd + Z	Undo
Ctrl/Cmd + Shift + Z	Redo
Ctrl/Cmd + A	Select all
Ctrl/Cmd + D	Duplicate
Ctrl/Cmd + Alt + E	Export workflow JSON
Ctrl/Cmd + Alt + G	Open generate/export dialog
Ctrl/Cmd + Alt + A	AI generate workflow
Ctrl/Cmd + Alt + P	Preview generated output
H / V	Hand tool / Selection tool
?	View all shortcuts
Delete / Backspace	Delete selected
Escape	Close panel

Contributing

Contributions are welcome. Please read CONTRIBUTING.md before opening a pull request.

License

MIT © Nexus Workflow Studio Contributors