Flocks Slash Commands

Flocks / slash commands are used in session input boxes to quickly view capabilities, switch context, refresh tools, or trigger common operations. They mainly appear in WebUI, TUI, CLI sessions, and some IM channels.

For terminal flocks <command> commands, see Flocks CLI. The difference is that CLI targets local operations and scripted actions, while / commands target the current session and help Rex, Agent, and users complete in-conversation operations quickly.

1. Entry Points

1.1 WebUI Sessions

In the WebUI session input box, you can enter / commands directly, for example:

/help
/tools
/skills
/mcp status
/new

WebUI is suitable for viewing tools, Skills, Agents, and Workflow available to the current session. It is also suitable for using /new to clear the current conversation history and start over.

1.2 TUI and CLI Sessions

After entering a terminal session with the following command, you can also use / commands:

flocks tui

TUI sessions are suitable for interacting with Rex in the local terminal while quickly viewing tool, task, Skill, and MCP status. The TUI / Node CLI source code also contains a flocks run entry point, but the current Python flocks main CLI does not register that command. Actual available entry points are determined by flocks --help.

1.3 IM Channels

Some IM channels support / commands, such as WeCom, Feishu, and DingTalk. Common commands in IM channels include:

/status
/model
/new

Not all WebUI commands are suitable for direct execution in IM channels. When a command is unsupported, the system indicates that the command cannot be executed in slash form on the current channel.

2. Usage Principles

2.1 Start with /help

Available commands may differ by entry point, Workspace, and MCP configuration. The most accurate list is always the result of entering /help in the current session.

2.2 / Commands Only Affect the Current Session

Most / commands view or adjust the current session context. For example, /new restarts the current session, /tools views tools available in the current environment, and /model views or switches the model for the current IM session.

For local operations such as service start and stop, account maintenance, and scripted task management, use Flocks CLI.

2.3 Custom Commands Appear Dynamically

Flocks also discovers project or user custom commands and commands exposed by MCP Prompts. Therefore, the commands seen by the same user after entering /help may differ across Workspaces.

3. General Commands

Command	Purpose	Entry Points
/help	View all / commands supported by the current entry point.	WebUI / TUI / IM / ACP / CLI
/tools	View currently available tools.	WebUI / TUI / ACP / CLI
/skills	View currently available Skills.	WebUI / TUI / ACP / CLI
/agents	View Agents that can currently be delegated to or selected.	WebUI / TUI / ACP / CLI
/workflows	View currently available Workflow.	WebUI / TUI / ACP / CLI
/mcp	View MCP Server and MCP tools.	WebUI / TUI / ACP / CLI
/init	Analyze the current project and create or update project-level Agent instructions.	WebUI / TUI / ACP / CLI
/compact	Summarize and compact the current session context.	WebUI / TUI / ACP
/clear	Clear current UI output. This does not delete real session data.	WebUI / TUI / ACP / CLI
/bug <description>	Prepare issue feedback.	WebUI / TUI / ACP / CLI
/plan <task>	Ask Plan Agent to create a plan for a task.	WebUI / TUI / ACP / CLI
/ask <question>	Ask a question only, without making changes.	WebUI / TUI / ACP / CLI
/tasks	View the Task Center overview.	WebUI / TUI / ACP / CLI
/queue	View task queue status.	WebUI / TUI / ACP / CLI
/new	Start a fresh session. Some entry points also support /reset as an alias.	Determined by /help in the current entry point

4. Tool-Related Commands

4.1 /tools Subcommands

Command	Purpose
/tools or /tools list	List currently available tools by category.
/tools refresh	Refresh dynamic tools.
/tools info <name>	View tool details, parameters, and whether confirmation is required.
/tools create <requirements>	Use the tool-builder Skill to create a tool from requirements.

4.2 /mcp Subcommands

Command	Purpose
/mcp or /mcp list	List MCP Server.
/mcp status	View MCP Server status, tool count, resource count, and error information.
/mcp tools	List MCP tools.
/mcp refresh <server>	Refresh tools for the specified MCP Server.

5. Skill and Agent Commands

5.1 /skills Subcommands

Command	Purpose
/skills or /skills list	List currently available Skills.
/skills refresh	Refresh the Skill list.

5.2 Agent and Workflow Queries

Command	Purpose
/agents	View Agents that can currently be delegated to or selected.
/workflows	View currently available Workflow.

If you want to select an Agent reliably, state it explicitly in the task description, such as "use the specified Agent to complete this task", or directly select or @ a sub-agent in supported entry points.

6. Task Commands

Command	Purpose
/tasks	View the Task Center overview.
/queue	View task queue status.

Bulk operations such as task creation, cancellation, rerun, and schedule configuration are better handled through Flocks CLI or the Task Center page.

7. IM Channel Commands

Command	Purpose
/status	View the Session, Agent, model, and IM conversation information bound to the current IM conversation.
/model	View the current model.
/model provider/model	Switch the model used by the current IM session.
/new	Start a fresh session for the current IM conversation and bind a new Session.
/reset	Alias for /new.

In IM channels, each IM conversation usually corresponds to one Flocks Session. You can ask in the conversation "what is your session_id" to obtain the session_id, then send messages to this fixed IM conversation from other WebUI sessions, Task Center, or Workflow.

Example:

Send to session_id: abc123: Inspection is complete, and the report has been generated.

This approach is suitable for multiple groups, multiple channels, and scheduled task scenarios. Compared with manually tracking external platform conversation identifiers across different entry points, using the Flocks session_id directly makes it easier to pass information across WebUI, Task Center, Workflow, and IM sessions.

8. Custom / Commands

Flocks supports project or user custom commands and may expose MCP Prompts as / commands. Whether custom commands appear depends on the current Workspace, project configuration, user plugins, and MCP Server.

Recommendations:

• To know what the current session supports, enter /help first.
• To view tools, Skills, Agents, and Workflow, prefer /tools, /skills, /agents, and /workflows.
• To push results to a fixed IM conversation, first use /status or ask "what is your session_id" to get the session_id.
• For local operations, batch operations, or scripted processing, prefer Flocks CLI.

9. Related Modules

• Session Management: main entry point for WebUI sessions and / commands.
• Tool Inventory: tool management page corresponding to /tools and /mcp.
• Skills: Skill management page corresponding to /skills.
• Task Center: task pages corresponding to /tasks and /queue.
• Flocks CLI: terminal CLI command reference.