← All guides

Compose safely and share a minimal diagnostic summary

Prepare a prompt before inserting it into a terminal, and share status categories without exporting your host details or terminal output.

Guide 10 · 3 min read · Updated 2026-11-09 · Current release: 1.1.0. Diagrams illustrate the workflow, not app screenshots.

Before you begin

Compose text and safe diagnostic summaries are available in the current App Store release. Plain-text composing and diagnostic summaries do not require Pro. Controls can differ by version.

  1. Write in a local draft

    Open Terminal’s More menu → Compose text…. Type or paste normally, including Chinese IME text. The draft belongs to that tab, and editing it sends nothing to SSH. Finish choosing an IME candidate before selecting Insert.

  2. Return without losing your place

    Back, tab switches and reconnects retain the draft while the app remains open. Closing a drafted tab asks whether to keep the tab or discard it. Drafts are memory-only and are not restored after the app terminates or restarts.

  3. Insert deliberately

    Insert pastes without adding Enter. Control characters are rejected, and multiline insertion requires protected paste support. The remote program still controls how pasted content is interpreted; inspect the terminal before executing.

  4. Review a safe support summary

    Open Help & privacy → Safe diagnostic summary, or Preview actions → Safe diagnostic summary. Review the JSON, then choose Copy summary if you want to share it. It contains platform, build mode and up to 12 recent category/state pairs. Clear removes this in-memory record.

If something gets in the way

My draft vanished after restarting the app

That is the current privacy-oriented design: drafts are deliberately not stored on disk. Save long-lived notes in your own editor before quitting.

The report is empty

Only selected connection, forwarding, web and storage events from this running app session are recorded. An empty report does not prove that no error occurred.

How should I report a problem?

Send the app build, platform, reproduction steps and the reviewed diagnostic summary. Redact screenshots separately; never send passwords, private keys or raw terminal logs.

Next guide →Find your way around the mobile workspace

Still need a hand?

Tell us your platform, app build, and the steps you tried. Never send passwords or private keys.

Contact support