Next Command Hints

Updated on Oct 1, 2026

After a workflow command finishes, Forge suggests logical follow-up commands in a Next Steps section. The hints help you learn the typical progression from issue to code to pull request.

How it works

The hints appear after the completion summary.

Example output (abbreviated):

text

Outputs written to: .forge/work/job_123/issue/

Next Steps:
 → frg issue draft --edit - Edit and refine the drafted issue
 → frg issue review - Review the draft for completeness
 → frg issue plan - Create implementation plan from this issue
 → frg issue split - Split this issue into smaller work items
 → frg issue ask - Ask questions about this issue

Command progressions

Issue commands

After running	Suggested next commands
`frg issue triage`	`frg issue draft`, `frg issue ask`
`frg issue draft`	`frg issue draft --edit`, `frg issue review`, `frg issue plan`, `frg issue split`, `frg issue ask`
`frg issue review`	`frg issue plan`, `frg issue ask`
`frg issue plan`	`frg issue plan --edit`, `frg code create`, `frg code ask`

Code commands

After running	Suggested next commands
`frg code create`	`frg code create --fix`, `frg code test`, `frg code review`, `frg code ask`
`frg code test`	`frg code create`, `frg code create --fix`, `frg code review`, `frg code ask`
`frg code review`	`frg code review --auto-fix issues`, `frg code create`, `frg code create --fix`, `frg pr draft`, `frg docs create`, `frg code ask`

PR commands

After running	Suggested next commands
`frg pr draft`	`frg pr draft --edit`, `frg pr review`, `frg pr ask`
`frg pr review`	`frg pr merge`, `frg pr merge --fix`

Backlog commands

After running	Suggested next commands
`frg backlog create`	`frg backlog review`, `frg backlog ask`
`frg backlog rank`	`frg backlog create`, `frg backlog review`, `frg backlog ask`

Documentation commands

After running	Suggested next commands
`frg docs create`	`frg docs create --edit`, `frg docs ask`

Security commands

After running	Suggested next commands
`frg sec audit`	`frg config set-issue <id>`, `frg sec patch`, `frg sec ask`
`frg sec patch`	`frg code review`, `frg pr draft`, `frg sec audit`, `frg sec ask`

Terminal operations, such as frg pr merge and frg docs build, show no hints.

Disable hints

Set show_command_hints in the [ui] section of the project configuration:

toml

# .forge/config/project.toml
[ui]
show_command_hints = false

When disabled, Forge omits the Next Steps section. Hints are enabled by default.

Notes

Hints appear only after a successful run, not after a cancelled or failed one.
frg app commands also show hints.