Slash Commands

Inside the Flowly TUI, type / to run a command instead of sending a message to the agent. Type ? in an empty composer for a quick cheat sheet, or open the full help modal with /help (or F1).

Session

Standing goals

A standing goal keeps the agent working across turns until it is achieved, needs you, or exhausts its budget. Setting one starts the work in the same turn.

Pausing or ending a goal also stops the goal turn that is streaming at that moment. A turn you typed yourself is never stopped by these commands.

Model & persona

Tools & integrations

/learn

Create or update a reusable skill from source material you provide:

/learn [source]
/learn --dry-run [source]

[source] can be a local path, directory, URL, pasted notes, or a phrase such as "what we just did". With no source, Flowly uses the current conversation as the material to distill.

Examples:

/learn the release checklist workflow from this conversation
/learn ~/work/internal-sdk/docs/auth.md
/learn https://example.com/api-guide and these notes: ...
/learn --dry-run ./runbooks/customer-escalation.md

Normal mode saves the skill through skill_manage: it lists existing agent-authored skills to avoid obvious duplicates, creates or updates the skill, writes supporting files when needed, and verifies the result. New or updated skills appear in the TUI slash palette automatically after a successful skill_manage or skill_improve write in the active session.

Dry run mode previews the same plan without writing. It may inspect sources and list existing skills, but it must not call persistent skill_manage actions such as create, patch, edit, write_file, or delete. The reply includes the proposed skill name, create/update decision, full SKILL.md draft, supporting file drafts, verification check, and the command to run when you want to apply it.

Short alias: -n is accepted as a dry-run flag.

Permissions & activity

/plan

Turn on plan mode: the agent decomposes the task into steps, shows you the plan, and runs no side-effecting tool until you approve it.

/plan                 # toggle the standing mode on/off
/plan on              # turn it on
/plan off             # turn it off AND abort the active plan
/plan status          # is it on? what's the active plan's progress?
/plan <task>          # plan THIS task only, without entering the standing mode

Bare /plan is a mode, not a one-shot: while it's on, every message plans first. It's the same mode Shift+Tab cycles to (▣ Plan), and it works on every surface that sends text — the TUI, Desktop, iOS, and chat channels. Approving a plan ends the mode — the work runs under whatever permission level was underneath, and the next message is a normal one. Rejecting or revising keeps you planning.

/plan <task> is the exception: it forces plan-first for that message only.

Aliases: /plan stop and /plan cancel behave like /plan off; /plan ? behaves like /plan status.

Account

Keybindings

Shell escape

Prefix a line with ! to run a bash command locally — it is never sent to the LLM. Output appears as a code block in the transcript.

!ls
!git status
!pwd

There is a 30-second timeout and a 4000-character output cap.

Related

• CLI commands
• Standing goals
• Tools
• Sessions