Reporting an issue

Questions about Claudette go to dotBunny’s Discord. Problems go to its GitHub issues, where they’re tracked until they’re fixed. The Settings window has what you need for both, with the versions already gathered for a report.

Asking a question

Ask on Discord, under Help (the question mark beside the version at the foot of the Settings sidebar), opens dotBunny’s Discord in your browser. Ask there how to do something, whether something is meant to work the way it does, or anything else about Claudette. The menu at the header’s right, the three lines after your plan, has it too, as do the command palette and, on macOS, the menu bar’s Help menu.

The server’s members see what you post, so leave out anything private. If it turns out to be a bug, report it on GitHub too, as below.

The version

The foot of the Settings sidebar shows which Claudette this is, on every page: Claudette 0.6.0. A copy run from source adds the commit it was built from, such as Claudette 0.6.0 · 842169b. See Running from source.

Click it to copy the versions for a bug report, one per line. It says Copied for two seconds. The lines are:

  • Claudette’s version and how it was installed: an MSIX, the Microsoft Store, a .dmg, or a source build and its commit.
  • Claude Code’s version.
  • The operating system and its identifier.
  • The .NET runtime.

Only versions: never paths, names or account details, because it’s meant to be posted.

Report an issue

Report an issue, under Help at the foot of the Settings sidebar, opens a new issue on Claudette’s GitHub page in your browser. It starts with an outline, what happened, what you expected and steps to reproduce, and the same versions filled in. Nothing is sent until you submit it on GitHub.

  1. Choose Report an issue in the header’s menu, in Settings, or in the command palette.
  2. Fill in the outline. Say what you were doing, what you expected and what happened instead.
  3. Add what helps: the text of an error the tab showed, the tab’s status, and whether it happens every time.
  4. Review everything, then submit.

What helps

  • Which part. The page of this guide that describes it, or the name of the button.
  • Diagnostics. Copy diagnostics in Settings → Advanced adds the login shell line, the Claude app line and counts of messages Claudette didn’t know. Read it first: it includes the path to claude. See Diagnostics and logs.
  • A protocol log when Claude Code’s behavior is the question. It holds prompts and file contents, so cut it down to the lines that matter, or describe them.
  • Whether it happens in a terminal. If plain claude does the same thing, the problem is probably Claude Code’s, not Claudette’s, and belongs with Anthropic.

Leave out anything private: your prompts, project paths and account details.

See also

Back to top

Claudette is made by dotBunny under the MIT license. Privacy policy

Claude and Claude Code are trademarks of Anthropic, PBC. Godot and the Godot logo are trademarks of the Godot Foundation; the logo is by Andrea Calabró, under CC BY 4.0. Unity is a trademark or registered trademark of Unity Technologies or its affiliates in the U.S. and elsewhere. Unreal®, Unreal Engine®, and the Unreal Engine® logo are trademarks or registered trademarks of Epic Games, Inc. in the United States of America and elsewhere. Other brands or product names are the trademarks of their respective owners. The logo is used with Epic's permission. Perforce, P4V and the Perforce logo are trademarks of Perforce Software, Inc. or one of its affiliates; the logo is used with Perforce's permission. Claudette isn't sponsored by, affiliated with or endorsed by any of them. Other names are trademarks of their owners.

Edit this page on GitHub

This site uses Just the Docs, a documentation theme for Jekyll.