Feedback for features

[Graeme22]

I'd like to get an idea of what commands are most desired by the community so I know what to prioritize implementing. Some are really obvious:

• [ ] list watchlists
• [x] list option chain for a symbol at a given date (potentially defaulting to the closest monthly to 45 days)
• [x] place options orders
• [ ] place futures orders
• [ ] place stock orders
• [ ] place crypto orders
• [x] charting a la tastypl
• [ ] list portfolio
• [ ] list order history
• [ ] cancel/replace orders
• [ ] list activity
• [ ] list positions
• [ ] portfolio statistics (net liq, beta-weighted delta, etc.)
• [ ] compile past and present data of portfolio for analysis
• [ ] portfolio risk analysis (correlation, % of capital used relative to VIX, etc.)

I'm sure I'm missing lots of things, so I'd appreciate feedback on what other features people would like.

[def-mycroft]

this one might be a bit harder to implement and we might not be able to do anything on it before the release.

I've written some code that allows me to create custom price alerts. I'm using IB for a minute-by-minute data subscription and Telegram to send out alerts. I have simple code that alerts when prices of an underlying surge and when crossing a rolling window, and these are configurable with a sort of "heat level" setting i.e. 100 normal amount of alerts, 200 is a lot of alerts (for things that I want to watch closely) and 50 would be something that I only want to be alerted if there is a very large move. can also do above/below threshold levels, of course.

I just don't think we know what the functionality of the API will allow at this point in time.

[def-mycroft]

should and/or could the tastypl project be fully integrated here?

would be convenient if you could run commands like

tastyworks-cli tastypl -input yourcsvfile.csv -printpl -positions -chart

...corresponding to go run tastypl.go -input yourcsvfile.csv -printpl -positions -chart, although with the api likely wouldn't have to export the transactions file.

[def-mycroft]

would be nice to be able to archive and resubmit futures orders, for some reason the platform currently doesn't allow gtc futures orders, which means that I have to manually enter orders before the overnight session. they say they're working on a fix but I guess it's complicated.

if have the feature that sends futures orders, then being able to archive orders and resubmit efficiently would be useful.

[def-mycroft]

scanning functionality could be a whole project itself.

one scanning function that comes to mind would be: for a given chain, try all (or a large number of) possible combinations of iron condors and return possible choices ranked by "expected edge", i.e. the difference between pop and breakeven probability given by the width of the strikes and the premium collected.

[Graeme22]

should and/or could the tastypl project be fully integrated here?

would be convenient if you could run commands like

tastyworks-cli tastypl -input yourcsvfile.csv -printpl -positions -chart

...corresponding to go run tastypl.go -input yourcsvfile.csv -printpl -positions -chart, although with the api likely wouldn't have to export the transactions file.

That's a good idea. Definitely a useful feature as long as TW doesn't provide portfolio charts itself.

[Graeme22]

scanning functionality could be a whole project itself.

one scanning function that comes to mind would be: for a given chain, try all (or a large number of) possible combinations of iron condors and return possible choices ranked by "expected edge", i.e. the difference between pop and breakeven probability given by the width of the strikes and the premium collected.

this one might be a bit harder to implement and we might not be able to do anything on it before the release.

I've written some code that allows me to create custom price alerts. I'm using IB for a minute-by-minute data subscription and Telegram to send out alerts. I have simple code that alerts when prices of an underlying surge and when crossing a rolling window, and these are configurable with a sort of "heat level" setting i.e. 100 normal amount of alerts, 200 is a lot of alerts (for things that I want to watch closely) and 50 would be something that I only want to be alerted if there is a very large move. can also do above/below threshold levels, of course.

I just don't think we know what the functionality of the API will allow at this point in time.

I think these ideas could be done. However it might be better to have them as plugins or something, and keep the "core" functionality here.