Article
Codex IBKR Chart Data Prompt Template (Copy-Paste)
Use a Codex IBKR chart data prompt template that keeps parsers, schemas, tables, documentation, and QA tied to supplied export fields.
A Codex IBKR chart data prompt should be specific enough to prevent drift. This support page focuses on the prompt itself; use Using Codex or Claude Code With IBKR Chart Data as the main page for the broader IBKR Codex and Claude Code workflow.
Prompt Template
Use this structure: Here is a sanitized MyLinedChart export from my IBKR chart workflow. Use only these fields. Explain the data shape, identify missing review fields, and draft one implementation artifact. Do not infer trading advice, do not invent market context, and list every assumption separately.
The important part is not the exact wording. It is the boundary: source, fields, one task, constraints, assumptions, and human review. For the full workflow before and after the prompt, use Using Codex or Claude Code With IBKR Chart Data.
Template Fields
The prompt should identify the source, field meanings, requested output, review constraints, and expected review output. If those parts are missing, Codex is more likely to produce output that looks useful but is hard to verify.
| Prompt Field | What to Include |
|---|---|
| Source | MyLinedChart export from an IBKR chart workflow |
| Fields | Symbol, timeframe, drawings, notes, levels, setup tags, review status |
| Task | Parser, table schema, dashboard draft, documentation, or QA checklist |
| Constraint | No trading advice, no invented fields, no unreviewed risk logic |
| Review | Assumptions, missing data, and tests a human should run |
Good First Tasks
Start with a parser, field map, table schema, or dashboard draft. These tasks are narrow enough to check manually and useful enough to improve the workflow.
Do not start by asking Codex to produce an end-to-end trading system. The prompt should improve the chart-data handoff, not replace trader judgment.
Next Step
After testing the prompt template, use Using Codex or Claude Code With IBKR Chart Data to compare the Codex prompt with the Claude Code prompt and the human review checklist.
Keep the prompt stable while testing so output changes reflect the chart data, not prompt drift.
FAQ
What should a Codex IBKR chart data prompt include?
Include source context, sample data, field definitions, one task, and review rules that block trading advice and unsupported assumptions.
What is a good first Codex task?
Ask for a parser, field map, table schema, dashboard draft, documentation pass, or QA checklist that can be checked manually.
Where should this prompt link back?
Use Using Codex or Claude Code With IBKR Chart Data as the main guide for the broader IBKR Codex and Claude Code workflow.
Sample Structured Chart-Data Exports
Review how chart drawings, annotations, OHLC, volume, and execution context become reusable structured data.