Qoder Agent (Print Mode - Non-Interactive)

Use Print mode (-p) for all Qoder CLI work in OpenClaw. TUI mode is not supported in automated environments.

✅ All-Sessions Ready: This skill works in:

• - Direct 1:1 chats
• Group chats (DingTalk, Discord, Slack, etc.)
• Shared workspace sessions
• Private sessions

⚠️ Important: Print Mode Only

TUI mode is NOT supported in OpenClaw or other automated environments due to TTY requirements.

Always use Print mode with the -p flag:

CODEBLOCK0

🔐 Environment Setup (Auto-Detected)

Qoder CLI authentication is automatically available via:

CODEBLOCK1

In any session type, the environment variable is inherited from the shell, so Qoder CLI works seamlessly.

🚀 Quick Start

Basic Usage

CODEBLOCK2

🎯 Print Mode Flags

🧠 Model Selection

Qoder CLI uses automatic model routing - it selects the globally optimal model based on task characteristics. You can override this:

Recommendations:

• - Default: Use --model=auto (let Qoder choose)
• Refactoring/Architecture: INLINECODE40
• Quick fixes: INLINECODE41
• Code review: --model=performance or INLINECODE43
• Simple queries: --model=lite or INLINECODE45

🎯 Quest Mode (Spec-Driven Development)

Quest Mode allows you to write specifications while AI automatically completes development tasks using subagents.

CODEBLOCK3

Quest Mode automatically:

1. 1. Analyzes requirements
2. Routes to appropriate subagents
3. Coordinates multi-step development
4. Ensures consistency across files

🤖 Subagents

Subagents are specialized AI agents for specific tasks with their own context windows and tool permissions.

Create a Subagent (Manual)

Create markdown files in:

• - ~/.qoder/agents/<agentName>.md - User-level (all projects)
• INLINECODE47 - Project-level

Example: code-review agent
CODEBLOCK4

Use Subagents

CODEBLOCK5

🌳 Worktree (Parallel Jobs)

Worktree jobs are concurrent jobs that use Git worktrees to run tasks in parallel, avoiding read/write conflicts.

Requirements: Git installed and usable locally.

Commands

Create a Job

CODEBLOCK6

View Jobs

CODEBLOCK7

Delete Jobs

CODEBLOCK8

⚠️ Warning: Deletion is irreversible. Proceed with caution.

Parallel Issue Fixing Example

CODEBLOCK9

🔌 MCP Servers

Qoder CLI integrates with any standard MCP (Model Context Protocol) tool.

Add MCP Servers

CODEBLOCK10

Recommended MCP Tools

CODEBLOCK11

Manage MCP Servers

CODEBLOCK12

🔐 Permissions

Qoder CLI enforces precise tool execution permissions.

Configuration Files (precedence: high → low)

1. 1. ${project}/.qoder/settings.local.json - Project-level, highest (gitignore)
2. INLINECODE52 - Project-level
3. INLINECODE53 - User-level

Permission Strategies

Example Configuration

CODEBLOCK13

Permission Types

1. Read & Edit Rules

Patterns follow gitignore-style matching:

2. WebFetch Rules

Restrict domains for network fetch:

CODEBLOCK14

3. Bash Rules

Restrict commands for shell execution:

CODEBLOCK15

📝 Memory (AGENTS.md)

Qoder CLI uses AGENTS.md as memory - content is auto-loaded as context.

File Locations

• - User-level: ~/.qoder/AGENTS.md - Applies to all projects
• Project-level: ${project}/AGENTS.md - Applies to current project

Typical Content

• - Development standards and notes
• Overall system architecture
• Project-specific conventions
• API documentation
• Testing requirements

Generate/Manage

CODEBLOCK16

⚡ Advanced Options

⚠️ Rules

1. 1. Print mode only - TUI mode not supported in OpenClaw
2. Always use -p flag - Non-interactive mode required
3. Respect workdir - Qoder sees only the specified directory's context
4. Monitor with process:log - check background session progress
5. Use worktrees for parallel work - avoid read/write conflicts
6. Initialize AGENTS.md - helps Qoder understand project context
7. Configure permissions - set appropriate access rules per project
8. Leverage subagents - specialized agents for specific tasks
9. Add MCP servers - extend capabilities with external tools
10. Works in all sessions - environment variables are inherited automatically
11. Use ultimate model for complex tasks - refactoring, architecture, code review

Progress Updates (Critical)

When you spawn Qoder CLI in the background, keep the user in the loop:

• - Send 1 short message when you start (what's running + where)
• Then only update again when something changes:

• - If you kill a session, immediately say you killed it and why

This prevents the user from seeing only "Agent failed before reply" and having no idea what happened.

Auto-Notify on Completion

For long-running background tasks, append a wake trigger:

CODEBLOCK17

This triggers an immediate wake event — you get pinged in seconds, not minutes.

🌐 Cross-Session Usage

In Group Chats (DingTalk, Discord, Slack)

CODEBLOCK18

In Direct Messages

Same as group chats - works out of the box.

In Shared Workspaces

CODEBLOCK19

Privacy Note

• - Qoder CLI only accesses the specified INLINECODE95
• Environment variables are inherited from the host shell
• No credentials are exposed in chat messages
• Each session has isolated Qoder CLI state

📊 Comparison with Other Coding Agents

Qoder CLI strengths:

• - Subagents for specialized tasks
• Worktrees for parallel development
• Quest mode for spec-driven development
• Automatic model routing
• Granular permission system
• Cross-session compatibility

📋 Quick Reference Card

CODEBLOCK20

🔧 Troubleshooting

Not Logged In

CODEBLOCK21

Permission Denied

CODEBLOCK22

Model Selection Issues

CODEBLOCK23

TUI Mode Error

TUI mode is NOT supported in OpenClaw. Always use Print mode:

CODEBLOCK24