ibkr canary
Something broke or looks wrong
Use this for reproducible app, remote beta, CLI, MCP, install, or docs problems.
Report a bugFeedback
Share feedback or report issues for ibkr canary.
Use the public GitHub forms for bugs, feature requests, and general workflow feedback. Use email for private context, broker-sensitive details, or when you do not want to create 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.
These routes create GitHub issues with enough structure to reproduce problems and keep requested work visible.
A workflow should exist
Use this for new Canary app views, MCP tool ideas, CLI commands, docs, or install improvements.
Request a featureQuestion, confusion, or reaction
Use this when it is not clearly a bug or feature request, but it should still be visible.
Share feedbackPrivate and direct.
Email me when the useful context 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 early remote app beta coordination.
Email OliverMake diagnostics safe
Redact account ids, order ids, position sizes, balances, tokens, hostnames, and gateway addresses before sending logs or screenshots.
Use the security path for vulnerabilities
Security reports should go through the private advisory flow instead of a public issue or ordinary email.
Report a vulnerabilityWhat helps most.
- Tell me which surface you used: Canary app, remote app beta, CLI, MCP server, install, or docs.
- Include the ibkr version, OS, 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 good would look like.