Canary
Something broke or looks wrong
For problems you can reproduce in the app, remote access, CLI, MCP, install or docs.
Report a bugFeedback
Share feedback or report issues for Canary.
Bugs, feature requests and general workflow feedback go through the public GitHub forms. Email is for private context, broker-sensitive details or anything you would rather not file as a GitHub issue.
Do not post account numbers, order IDs, balances, positions, API tokens, hostnames, gateway details or unredacted broker screenshots in public issues.
Public and trackable.
Each route opens a GitHub issue with enough structure to reproduce a problem and keep requested work in view.
A workflow should exist
For new Canary app views, MCP tool ideas, CLI commands, docs or install improvements.
Request a featureQuestion, confusion or reaction
For anything that is not clearly a bug or a feature request but should still be visible.
Share feedbackPrivate and direct.
Email me when the context that matters belongs outside a public GitHub issue, or when GitHub is too much friction.
Reach Oliver directly
Best for account-specific context, broker-sensitive details, screenshots that need redaction help or remote-access setup.
Email OliverMake diagnostics safe
Redact account IDs, order IDs, position sizes, balances, tokens, hostnames and gateway addresses before you send logs or screenshots.
Report security vulnerabilities privately
Send security reports through the private advisory flow rather than a public issue or ordinary email.
Report a vulnerabilityWhat helps most.
- Tell me which part you used: the Canary app, remote access, CLI, MCP server, install or docs.
- Include the Canary version, your OS, the browser or MCP client and whether the source was TWS or IB Gateway.
- For bugs, include the shortest steps that reproduce it and the redacted output you saw.
- For feature requests, describe the workflow and what a good result would look like.