Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qoder.com/llms.txt

Use this file to discover all available pages before exploring further.

TUI Mode

Run qodercli from any project root to enter the default TUI (interactive) mode. You can chat with the CLI by text or execute special functions via slash commands.

Input modes

Multiple input modes are available in the TUI:
CommandDescription
>Dialog mode (default). Type any text to chat with the CLI.
!Bash mode. From dialog mode, enter ! to run shell commands directly.
/Slash mode. From dialog mode, type / to open and run built-in commands.
\ Enter to start multiline input.

Built-in tools

Qoder CLI ships with tools like Grep, Read, Write, and Bash for file/directory operations and shell command execution.

Slash commands

Quickly access features and settings with these built-in slash commands:
CommandDescription
/loginLog in to your Qoder account
/helpShow TUI help
/initInitialize or update the AGENTS.md memory file in the project
/memoryOpen the memory manager for user, project, and local memory files
/questSpec-driven delegated task
/reviewCode review for local changes
/resumeList and resume sessions
/clearClear the current session context history
/compactSummarize the current session’s context history
/usageShow your current credit usage
/statusShow CLI status: version, model, account, API connectivity, tool status, etc.
/configShow system configuration of Qoder CLI
/agentsSubagent commands: list, create, manage subagents
/tasksList running background tasks
/release-notesShow Qoder CLI release notes
/vimOpen an external editor to edit input
/feedbackSend feedback about Qoder CLI
/quitExit TUI
/logoutLog out of your Qoder account

Advanced startup options

When launching the CLI, use the following options to control its behavior:
CommandDescriptionExample
-wSpecify the workspace directoryqodercli -w /Users/demo/projects/nacos
-cContinue the last sessionqodercli -c
-rResume a specific sessionqodercli -r *******-c09a-40a9-82a7-a565413fa39
--allowed-toolsAllow only specified toolsqodercli --allowed-tools=Read,Write
--disallowed-toolsDisallow specified toolsqodercli --disallowed-tools=Read,Write
--max-turnsMaximum dialog turnsqodercli --max-turns=10
--yoloSkip permission checksqodercli --yolo
For permission-related flags and settings, see Permissions. Print mode is non-interactive. Run qodercli --print to enter. Output is printed according to --output-format.

Flags

Global options can be used with any command:
OptionDescriptionExample
-pRun the Agent non-interactivelyqodercli -q -p hi
--output-formatOutput format: text, json, stream-jsonqodercli --output-format=json
-wSpecify the workspace directoryqodercli -w /Users/qoder_user/projects/qoder_demo
-cContinue the last sessionqodercli -c
-rResume a specific sessionqodercli -r ********-c09a-40a9-82a7-a565413fa393
--allowed-toolsAllow only specified toolsqodercli --allowed-tools=Read,Write
--disallowed-toolsDisallow specified toolsqodercli --disallowed-tools=Read,Write
--max-turnsMaximum dialog turnsqodercli --max-turns=10
--yoloSkip permission checksqodercli --yolo

Worktree

Use --worktree [name] to start a Qoder CLI session in a separate Git worktree. This is useful when you want to run parallel sessions against the same repository without sharing the same working directory.
Requirements: run the command inside a Git repository and make sure Git is installed locally.

Start in a worktree

qodercli --worktree feature-a
qodercli --worktree feature-a "Implement the login fix"
qodercli --worktree
If you omit the worktree name, Qoder CLI generates one automatically. After the worktree is prepared, Qoder CLI changes into that worktree and starts the session normally. When the session ends, Qoder CLI prints the worktree path and the command for resuming the session:
cd <worktree-path> && qodercli --resume <session-id>
To remove the worktree manually, run:
git worktree remove <worktree-path>

Memory

Qoder CLI uses AGENTS.md as a memory file, the content of which is auto-loaded into CLI as context to guide development. Typical content:
  • Development standards and notes
  • Overall system architecture
local files path:
# User-level, applies to all projects
~/.qoder/AGENTS.md
# Project-level, applies to the current project
${project}/AGENTS.md
# Local project-level, private to your machine
${project}/AGENTS.local.md

Automatically generate

Start TUI in the target project and enter /init to generate AGENTS.md in the project directory.

Manually manage

  • Create AGENTS.md in the project and edit its content.
  • In TUI, enter /memory to manage user, project, and local memory files.