Code block modifiers

Modifier referenceComma-separated, after fence

```bash,run	Click-to-run in the active terminal. Most common form.
```run	Click-to-run, no syntax highlighting. Language-less runnable block.
```copy	Adds a copy-to-clipboard button. Works without a language tag.
```nocopy	Disables the default copy button. Use on output blocks.
```bash,wrap	Wraps long lines instead of horizontal scroll.
```line-numbers	Shows a line-number gutter. Combinable: `run,line-numbers`, `js,line-numbers,wrap`.
```bash,wrap,copy	Wrap plus copy. Useful for long one-liners learners need to grab.
```bash,nocopy,run	Run-only, no copy button. For commands the learner shouldn’t grab.
```bash	Plain bash. No run button. Use for snippets with placeholders.
```copy	For placeholder-bearing snippets that must be edited before running. Forces paste-edit-execute.

Common combinations

# Click-to-run command ```bash,run aws s3 ls ``` # Copyable long command ```bash,wrap,copy curl -X POST ... ``` # Snippet with placeholder ```copy grant select on <TABLE-NAME> to ana; ``` # Reference output ```nocopy Process completed. ```

Language identifiers

bash · sh · shell · python · javascript · js · typescript · ts · yaml · yml · json · dockerfile · hcl · aql · esql · http · graphql · markdown · md · ruby · go · rust · click · mongodb · logs · plaintext · text

sh and shell are synonyms for bash. click is for terminal-pasted code that isn’t a literal bash invocation (inside a kubectl exec shell, for example).

TrapsDon't do this

Invalid syntax: ```bash {“run”: “execute”} looks like it should work but is not valid Instruqt syntax. The block renders, but no run button appears. Always use comma-separated modifiers: ```bash,run.

Placeholder + run is wrong: code blocks with angle-bracket UPPER-DASH-CASE placeholders (<TABLE-NAME>, <USER-EMAIL>) should never use ,run. Use copy alone — learners are forced to paste, edit, and execute manually.

Wrong language tag breaks execution: ```python,run on a bash command tells the platform to run it as Python. Output looks weird, errors confuse. Match the language tag to what’s actually executing.

Choosing the right modifier

bash,run for commands the learner should execute as-is.
copy for snippets containing placeholders the learner must edit before running. Pair with an opt-in <details> hint when the placeholder is non-obvious.
nocopy for output blocks the learner shouldn’t paste back into the terminal.
Plain bash (no modifier) when even copy is undesirable — for example, code samples in pure-explanation passages.
Modifiers stack freely; order does not matter (bash,wrap,copy equals bash,copy,wrap).