Share feedback

fx is under active development. Report issues and share diagnostic data to help improve fx.

Report a problem

Inside the interactive shell:

/feedback opens fx.sh/feedback, which forwards to the fx bug report form on GitHub. It does not generate diagnostics and does not change the clipboard.

The form asks for the issue, the expected behavior, and steps to reproduce it. It also has an optional Trace field for the output of /trace, and it requires you to confirm that you removed secrets and other sensitive data first.

Create a private diagnostic trace

Inside the interactive shell:

/trace creates a private Markdown file with logs, session context, runtime state, permissions, recent tools, and renderer information. On macOS, fx copies the .md file to the clipboard. On other platforms, it saves the file and prints its path. The command does not open or link to the report form; run /feedback separately when you are ready to attach the reviewed trace.

Review and redact the trace before sharing it. It remains local unless you share it yourself.

Record a terminal issue

Recordings help the fx team reproduce rendering and interaction bugs.

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

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

Replay a recording before sharing it to confirm that it captures the issue:

Check your setup first

fx doctor checks the workspace, configuration, authentication, startup settings, local session state, and Git integrations without starting an agent turn:

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