Share feedback

Report a problem with /feedback. For rendering or interaction bugs, you can attach a trace or terminal recording to help reproduce it.

Report a problem

Inside the interactive shell:

$/feedback

The command opens the GitHub issue form. Include what happened, what you expected, and the steps to reproduce the problem.

Create a private diagnostic trace

Inside the interactive shell:

$/trace

/trace collects logs, session context, and runtime diagnostics into a Markdown file. On macOS, it copies the file to the clipboard; on other platforms, it prints the saved path. Attach it through /feedback.

Traces and recordings stay local until you share them. They can contain prompts, code, paths, and secrets, so remove anything private before attaching them.

Record a terminal issue

Start fx with recording enabled, then reproduce the problem:

$FX_DEBUG_RECORD=1 fx

fx prints the recording path and writes a private .fxtape file under ~/.fx/recordings/. Choose an explicit path with FX_RECORD:

$FX_RECORD=./repro.fxtape fx

Add FX_DEBUG_RECORD_SILENT_BANNER=1 when the recording notice should stay out of the inline transcript during a screen share. Ctrl-O still shows the notice, and recording remains active.

Recordings capture visible terminal output, resizes, interrupts, and markers. Set FX_RECORD_INPUT=1 only when the fx team needs raw terminal input to reproduce the issue.

Replay a recording

Exit fx, then replay the recording to confirm that it captures the issue:

$fx replay ./repro.fxtape

Check your setup first

For startup or session problems, run:

$fx doctor

When fx can recover a session problem, the output includes the command to run. Troubleshooting covers the problems it reports most often.