I have had the IBKR integration working nicely. It has stopped since this morning. In a current chat it could not make any new api calls.
In a new chat it could still connect but not use all the function.
Here is the bug report:
Hier is een technisch bugreport dat je direct kunt plaatsen op het OpenAI Developer Forum of de Community. Ik heb alle persoonlijke informatie weggelaten.
Bug: IBKR connector becomes partially unavailable in long conversations and option tools fail independently
Summary
I found what appears to be two separate issues with the Interactive Brokers connector.
Issue 1
In long-running conversations the connector sometimes stops executing tool calls.
Instead of executing the requested function, ChatGPT only exposes the tool definitions/schema.
The exact same IBKR account works correctly in a newly created conversation.
Issue 2
Even when account access works (positions/orders/balances), option-related functionality appears not to execute.
The following functionality cannot be used reliably:
- search_contracts (for option workflow)
- get_option_parameters
- get_option_data
- option quote retrieval
- option chain retrieval
Environment
- ChatGPT iOS
- Interactive Brokers connector
- Latest ChatGPT app
- Same account
- Same authorization
- Same permissions
Issue 1: Conversation-specific connector failure
Expected
Calling
get_account_positions()
returns live portfolio data.
Likewise
get_account_orders()
get_account_balances()
get_account_summary()
should execute normally.
Actual
Instead of executing the connector call, ChatGPT only returns the connector schema.
Example behaviour:
api_tool.list_resources(…)
↓
Found XX tools matching the query
↓
entire tool definition
↓
no connector execution
No API request appears to reach IBKR.
Reproduction
- Create a conversation.
- Use the IBKR connector extensively.
- Continue the conversation for many days.
- Ask
Read my positions.
Result:
Only tool definitions are returned.
No execution.
Create a new conversation.
Ask exactly the same question.
Result:
Live positions are returned correctly.
Expected behaviour
Conversation history should not affect connector execution.
Issue 2: Option chain functionality
Even in conversations where account access works:
These appear not to execute correctly:
search_contracts
↓
get_option_parameters
↓
get_option_data
↓
get_price_snapshot
for option contracts.
This prevents:
- covered call analysis
- option chain retrieval
- delta calculation
- implied volatility retrieval
- open interest retrieval
- option volume retrieval
Expected
Typical workflow:
search_contracts()
↓
get_option_parameters()
↓
get_option_data()
↓
get_price_snapshot()
returns
- strikes
- expirations
- bid
- ask
- IV
- delta (or sufficient data)
- volume
- open interest
Actual
The workflow never completes.
Sometimes only tool definitions are shown.
Sometimes option-related tools appear unavailable while portfolio tools still work.
Additional observation
The feedback tool itself also became unavailable after working previously.
Example error:
Resource not found:
Interactive_Brokers_(IBKR).provide_customer_feedback
Call api_tool.list_resources again to rediscover the currently available tools.
This suggests connector/tool registration may become inconsistent during a conversation.
Suggested improvements
1. Connector reset
Provide a way to reset connector state without creating a new conversation.
Example:
Reconnect connector
or
Refresh connector context
2. Better error reporting
Instead of silently exposing tool schemas, return explicit errors such as:
Connector unavailable
Connector authorization expired
Tool registration failed
Option endpoint unavailable
3. Option support diagnostics
If option endpoints are unavailable, indicate which step failed:
- contract lookup
- option parameters
- option chain
- market data
- pricing
instead of failing silently.
Impact
This prevents automated workflows such as:
- portfolio monitoring
- covered call strategies
- option screening
- weekly option analysis
- rolling recommendations
The connector works well when available, but intermittent tool availability makes it difficult to build reliable long-running portfolio workflows.