Tutorial

Use Stream Mode only for the right commands.

Stream Mode is for long-running output. It is not better for everything. This guide makes the distinction clear so your chat stays useful instead of noisy.

Step 1 of 4Waiting for confirmation

Step 1: Stream commands that keep talking

sshChat AppRemote Server
Good Stream Mode examples
docker compose build
npm install
pytest
docker compose pull
Why

These commands can run for a while and keep producing new lines. Streaming is useful because you want to see progress as it happens.

How it feels

You send once and then watch output arrive live instead of waiting for one final block at the end.

Step 2: Keep quick snapshots in normal mode

sshChat AppRemote Server
Better in normal mode
pwd
ls -lah
docker compose ps
docker compose logs --tail 100
Why

These commands finish quickly. The result is easier to scan later if it stays as one normal chat result.

Rule of thumb

If the command should end in a few seconds, default to normal mode.

Step 3: Decide from the composer or from the catalog

sshChat App
Two ways to use it

Turn Stream Mode on at send time, or save it directly on a command in the catalog so that command always opens in stream mode by default.

Best use

Put it on the repeat commands you already know are long-running, like Compose Build or Compose Pull.

Premium note

Stream Mode is part of Premium. Free users can still run the command, but enabling Stream Mode should trigger the paywall.

Step 4: Stop when you learned enough

sshChat AppRemote Server
What to do

If the stream is no longer useful, use the stop control in sshChat rather than waiting forever.

Mental model

Stream Mode is for watching progress and deciding fast, not for turning the app into a permanent tail window.

Next step

If you want to organize which commands stream by default, continue to the command catalog guide.