Support

Something wrong with the tool? Open an issue on GitHub. It is open source, the discussion is useful to the next person who hits it, and the fix arrives in a release everyone gets.

Something wrong with your account, billing, or a team? Email support@flanner.io from the address on the account. That is faster than a public issue and does not put your team's details in a search engine.

A security problem? security@flanner.io, and please read the reporting section of the Acceptable Use Policy first.

Email is answered within two working days, usually sooner. Security reports are acknowledged within three working days.

There is no paid support tier and no SLA. This is a small operation, and saying so is more useful than promising an hour and missing it.

Three things turn most reports into a fix on the first reply:

• What you ran, and what happened instead of what you expected.
• Your version. flanner --version, plus your operating system.
• The error, in full. The last few lines are rarely the useful part.

Please do not paste plan content. It is almost never needed, and we would rather not receive it. If a specific file matters, describe its shape.

• Sync is slow. Run flanner peer status. If it says a connection is relayed rather than direct, a firewall is refusing to be punched through. It still works, just slower.
• A peer cannot be reached. Check both machines are signed in and that the device appears under Devices on your team page. A revoked device cannot be dialled at all.
• The agent is not saving plans through flanner. Run flanner claude-info to see whether registration actually took.

The docs cover installation and daily use, and the FAQ answers what people ask most. Both are quicker than waiting for us.