Skip to content

feat: add sell-window: should you sell options today? - #4

Merged
tomaszdobrowolski1 merged 2 commits into
mainfrom
feat/sell-window
Nov 6, 2026
Merged

tomaszdobrowolski1 merged 2 commits into
mainfrom
feat/sell-window

Conversation

@tomaszdobrowolski1

Copy link
Copy Markdown
Contributor

What

Adds fa.sell_window(symbol) for GET /v1/strategies/sell-window/{symbol}: sell or skip per listed expiry for SPY, QQQ and IWM, with the trades to place on a sell.

  • Typed response with windows, candidates and legs. Optional fields stay null on skip days.
  • Unit tests and a gated live test or runnable example.
  • Docs written so LLMs and search find it: a README section, routing rules in AGENTS.md, llms.txt, docs/sell-window.md with an FAQ, and package keywords.

Verified

  • Unit tests pass offline.
  • The README code block was extracted, compiled and run against production.
  • All claims match the live site, and the skip rule stays private as on the site.

Release

Version is 1.4.0. Nothing is published. After merge: PyPI: python -m build, twine upload.

🤖 Generated with Claude Code

tdobrowolski1 and others added 2 commits November 6, 2026 15:54
Adds `fa.sell_window(symbol)` for `GET /v1/strategies/sell-window/{symbol}`: sell or skip per listed expiry for SPY, QQQ and IWM, with the trades to place on a sell.

Docs for LLMs and search: a README section, routing rules in `AGENTS.md`, `llms.txt`, `docs/sell-window.md` with an FAQ, and package keywords. All claims match the live site.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A real pre-market replay returned a sell window with none of these fields and
candidates without legs. The docs said they are present whenever a window sells.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tomaszdobrowolski1
tomaszdobrowolski1 merged commit 04b959f into main Nov 6, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants