​

TUI Mode

​

Input modes

​

Built-in tools

​

Slash commands

​

Advanced startup options

​

Print Mode

​

Flags

​

MCP servsers

qodercli mcp add playwright -- npx -y @playwright/mcp@latest

​

Manage MCP servers

• Use -t to set MCP server type: stdio, sse, streamable-http. Stdio servers auto-start with TUI.
• Use -s to set scope: user-level or project-level. Configure MCP servers per project if needed.
• Manage added MCP servers using the following commands:

# List servers
qodercli mcp list

# Remove a server
qodercli mcp remove playwright

​

Files of MCP servers

# Added for the current user or specific project and will not be committed.
~/.qoder.json   

# Added for the current project and will be committed usually.
${project}/.mcp.json

​

Recommended tools

• qodercli mcp add context7 -- npx -y @upstash/context7-mcp@latest
• qodercli mcp add deepwiki -- npx -y mcp-deepwiki@latest
• qodercli mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

​

Permissions

~/.qoder/settings.json
${project}/.qoder/settings.json
${project}/.qoder/settings.local.json (usually added to .gitignore)

​

Configuration

{
  "permissions": {
    "ask": [
      "Read(!/Users/qoder_user/Documents/codes/go-micro/**)",
      "Edit(!/Users/qoder_user/Documents/codes/go-micro/**)"
    ],
    "allow": [
      "Read(/Users/qoder_user/Documents/codes/go-micro/**)",
      "Edit(/Users/qoder_user/Documents/codes/go-micro/**)"
    ],
    "deny": []
  }
}

​

Types

1. Read & Edit Read rules apply to all file-reading tools such as Grep, Glob, and LS. Patterns follow gitignore-style matching. Supported pattern forms include:

2. WebFetch Restrict domains for network fetch tools.

• WebFetch(domain:example.com) restricts fetches to example.com.

3. Bash Restrict commands for shell execution tools.

• Bash(npm run build) matches the exact command npm run build
• Bash(npm run test:*) matches commands starting with npm run test
• Bash(curl http://site.com/:*) matches curl commands starting with curl http://site.com/

​

Worktree

Requirements: Ensure git is installed and usable locally.

​

Create a job

• Add -p to run non-interactively inside the container; stop the container after it finishes.
• Add --branch to set the code branch for the job.
• Other Agent options (e.g., --max-turns) are passed through to the CLI inside the container. After the job is created, TUI mode is entered by default. You can start multiple jobs in separate terminals; worktrees isolate jobs from each other.

​

View jobs

$ qodercli jobs --worktree
Qoder jobs for workspace: /Users/linus/qoder/qodercli

Worktree Jobs:
ID              INIT PROMPT    PATH                                STATUS      CREATED             
11758283139787  [I] hello        ~/.qoder/worktrees/11758283139787   running     5 minutes ago       
11758283382928  [N] hello        ~/.qoder/worktrees/11758283382928   exited      1 minute ago        
11758283399820  [N] hello        ~/.qoder/worktrees/11758283399820   exited      1 minute ago

Total: 3 worktree job(s)

• ID: Unique job ID (not the container ID)
• INIT PROMPT: Initial job description (will become an AI-generated title in future)
• PATH: git worktree directory
• STATUS: Same as container status
• CREATED: job creation time

​

Delete jobs

qodercli rm <jobId>

Note: Deletion is irreversible. Proceed with caution.

​

Memory

• Development standards and notes
• Overall system architecture
• …

# User-level, applies to all projects
~/.qoder/AGENTS.md
# Project-level, applies to the current project
${project}/AGENTS.md 

​

Automatically generate

​

Manually manage

• Create AGENTS.md in the project and edit its content.
• In TUI, type # to enter memory edit mode and use vim-style editing for the project memory file.
• In TUI, enter /memory to choose and edit user- or project-level memory files.

​

Subagent

​

Manually create

• ~/.qoder/agents/<agentName>.md : User-level, applies to all projects
• ${project}/agents/<agentName>.md : Project-level, applies to the current project

---
name: code-review
description: Code review expert for quality and security checks
tools: Read, Grep, Glob, Bash
---

You are a senior code reviewer responsible for ensuring code quality.

Checklist:
1. Readability
2. Naming conventions
3. Error handling
4. Security checks
5. Test coverage
...

​

Automatically create

​

Use subagent

> Use code-review subagent to check code issues (explicit invocation)
> Analyze this code for potential performance issues (implicit)
> Review the implementation of this API (implicit)
> First use the design subagent for system design, then use the code-review subagent for code review (chained)

​

Commands

​

Create a command

• ~/.qoder/commands/.md : User-level, applies to all projects
• ${project}/commands/.md : Project-level, applies to the current project

​

Example

---
description: "Intelligent workflow orchestrator that guides users through feature development using specialized subagents"
--
First use the design subagent for system design, then use the code-review subagent to complete code review.

​

Use commands

​

Hooks

​

Configuration

• ~/.qoder/settings.json ： User-level, applies to all projects
• ${project}/.qoder/settings.json ： Project-level, applies to the current project
• ${project}/.qoder/settings.local.json ： Project-level, highest precedence (usually added to .gitignore)

{
  "hooks": {
    "Notification": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "~/notification.sh"
          }
        ]
      }
    ]
  }
}

#!/bin/bash

input=$(cat)

sessionId=$(echo $input | jq -r '.session_id')
messageInfo=$(echo $input | jq -r '.message')
workspacePath=$(echo $input | jq -r '.cwd')

if [[ "$messageInfo" =~ ^Agent ]]; then
  osascript -e 'display notification "✅ Your task has completed." with title "QoderCLI"'
else
  osascript -e 'display notification "⌛️ Your task requires authorization." with title "QoderCLI"'
fi

exit 0

Currently, Qoder CLI supports Notification hooks only. Different hook stages can intervene in the Agent’s main execution flow and remain decoupled from the CLI. More hook types (e.g., tool invocation, session intervention) are planned to broaden integration scenarios.