A SMALL CHECK-IN GOES A LONG WAY

How did Synapse
feel to use?

You do not need to write a full review or create a perfect bug report. Answer whichever questions are easy. One honest sentence is useful.

✓ Optional questions No account needed to prepare a draft Nothing is submitted automatically

WHAT HELPS MOST

Tell us about the real attempt—not what you think we want to hear.

Confusion, missing steps, unexpected behavior, and small wins are all useful. “I got stuck here” is a perfectly good report.

What were you trying to do?Your goal or use case

Where did you get stuck?The step, error, or unclear concept

What would make it better?One change is enough

YOUR CHECK-IN

Share what you noticed

ALL FIELDS OPTIONAL

1. What were you trying to do? 2. How did it go? 3. What felt confusing, slow, broken, or harder than expected? A command, error message, missing explanation, or rough description is enough. Do not include API keys, personal data, prompts, or customer records. 4. What worked well or felt useful? 5. What would you improve or want to see next? 6. Environment (optional)

Your answers stay in this page until you choose to copy them or open a GitHub draft.

⌑

Your feedback is not sent from this form. “Copy my feedback” copies the answers to your clipboard. “Continue to GitHub issue” opens a prefilled draft on GitHub; review it and submit it there if you choose. Do not put secrets, personal data, prompts, raw tool arguments, or customer information in public feedback.

PREFER ANOTHER ROUTE?

Pick the channel that fits.

Browse existing issuesCheck whether someone has already reported it ↗ Report a security vulnerabilityUse the private reporting route—not a public issue ↗ Contribute a fixSee the contribution and sign-off guidance ↗

How did Synapsefeel to use?

Tell us about the real attempt—not what you think we want to hear.

Share what you noticed

Pick the channel that fits.

How did Synapse
feel to use?