# 19 — Nested commands in interactive mode trigger prompt2

**Status:** done

Running nested commands in an interactive command drops into prompt2 when it shouldn't:

```
~/Code/20251000_lush> !echo ${`ls`.stdout}
>>
```

The parser sees the opening `{` and thinks the expression is incomplete, waiting for more input. The nested backtick command should be parsed and evaluated inline.