Hey @gilly3 - Sounds like this is a semantics issue. This sentence is pointing out that a new tab can't be opened in an existing instance of an already open Terminal. As you point out, wt nt will open a new instance with a new Terminal tab.

You know, I'm gonna reactivate this. We should just remove

Windows Terminal is not yet capable of opening new tabs or panes in an existing instance.

because it totally is possible to open new tabs in existing windows (via wt -w ...)

Thanks @zadjii-msft. Wasn't aware of this change - I'll get this update in the doc.

@zadjii-msft When I try wt -w 0 "Command Prompt (or any number), I get a new tab opened in the existing terminal window, but with error 2147942402 (0x80070002)... am I doing something wrong? I'm running version 1.21.2911.0

Ah, that's an intricacy of Terminal's interaction model.

If you are launching a profile (combined color scheme, title, command, other settings pertaining to how it interacts with the console session, etc.), you use wt [other args] -p "Profile Name".

If you're launching an executable (cmd.exe, powershell.exe), you use wt [other args] executable.

In your case, you'll want either wt -w 0 -p "Command Prompt" or wt -w 0 cmd.

Ahhhh! Thanks @DHowett! I'll get this in the doc.