Common OpenCode TUI Command-Line Options and Slash Commands — Master System Commands at Once 【OpenCode 002】

This introduction covers OpenCode’s CLI (command-line interface) options and the slash commands in its TUI (text user interface). Both provide access to many of OpenCode’s system functions.

1 Command-line options

When you start the OpenCode command line without any arguments, it launches TUI mode. If you provide command-line options, however, it performs different functions. The following are commonly used command options:

2 Slash commands

2.1 What are slash commands?

In the OpenCode input box, typing / opens the command panel. These slash-prefixed commands let you quickly perform various actions without memorizing complicated keyboard shortcuts. They are the “gateway” to invoking AI agents and automation features.

Think of slash commands as a “quick menu” — just as typing / in Discord or Notion brings up a function menu, OpenCode also provides a complete command system.

2.2 Basic commands: essentials

These are the commands you’ll use every day when you open OpenCode. Memorize these first.

2.2.1 Session management

2.2.2 Model switching

2.2.3 Editing and undo

2.3 Advanced commands: double your efficiency

Once you’ve mastered the basics, these commands can make your workflow smoother.

2.3.1 Interface control

2.3.2 Skills

Skills are OpenCode’s “plugin scripts” that give the AI capabilities in specific domains.

Recommended common skills:

2.4 Practical tips: making slash commands easier to use

2.4.1 File mentions with @

Typing @ in the input box opens a list of files in the working directory, and entering part of a filename lets you filter quickly.

Please help me check @index.jsp for SQL injection vulnerabilities.

2.4.2 Multiline input without accidental sending

• New line: Shift + Enter or Ctrl + J (most reliable)
• Send: Enter
• Clear: Ctrl + C

2.4.3 Command panel

Press Ctrl + P to open the command panel, where you can use the arrow keys to select commands instead of memorizing their names.

2.4.4 Custom commands

You can create your own slash commands and wrap commonly used prompts into one-click calls. There are two ways to define them:

2.4.4.1 Markdown files (recommended)

Create a .md file in the following directory; the filename becomes the command name:

---
description: Code review
agent: plan
model: anthropic/claude-sonnet-4-20250514
---

Please review the current file, focusing on the following:
1. Potential performance issues
2. Security vulnerabilities
3. Code readability
4. Adherence to best practices

2.4.4.2 JSON configuration

You can also define commands in opencode.json using JSON:

{
  "command": {
    "review": {
      "template": "Please review the current file, focusing on the following:\n1. Potential performance issues\n2. Security vulnerabilities\n3. Code readability\n4. Adherence to best practices",
      "description": "Code review",
      "agent": "plan",
      "model": "anthropic/claude-sonnet-4-20250514"
    }
  }
}

2.4.5 Passing arguments

Use $ARGUMENTS to pass text after the command into the prompt:

---
description: Create a new component
---

Use TypeScript to create a React component named $ARGUMENTS, including appropriate type definitions and a basic structure.

When you run /component Button, $ARGUMENTS is replaced with Button.

You can also use positional parameters to access individual arguments ($1, $2, $3, …):

---
description: Create a file
---

Create a file named $1 in the $2 directory with the following content: $3
```

```bash
/create-file config.json src "{ \"key\": \"value\" }"
```

• $1 → config.json
• $2 → src
• $3 → { "key": "value" }

2.4.6 Shell command injection

Use the !\command`` syntax to embed Bash command output into the prompt:

---
description: Analyze test coverage
---

Here are the current test results:
!\`npm test\`

Based on the results above, suggest how to improve test coverage.

---
description: Review recent changes
---

Recent Git commit history:
!\`git log --oneline -10\`

Review these changes and suggest improvements.

The command runs in the project root, and its output becomes part of the prompt directly.

2.4.7 File references

Use @ to reference files in a command:

---
description: Review component
---

Review the @src/components/Button.tsx component.
Check for performance issues and suggest improvements.

The file contents will be automatically included in the prompt.

2.5 Quick reference: common slash commands

3 Related links

• OpenCode Official Documentation (Traditional Chinese)
• OpenCode Official Keyboard Shortcuts Documentation
• Obsidian + OpenCode knowledge management combination

✅ Explanatory article (Traditional Chinese)
✅ Explanation article (English)
✅ Explanatory article (Japanese)

4 Tutorial video

https://youtu.be/fkLr0diCMrk

＃＃