The future of software development is Bots.
The Grok Bot interface has started the path down this road.
Why is Cursor not focusing on this direction more?
What I want to see:
- Accept Grok Bot as the interface for next level development.
- Split coding and Grok Bot token usage - as currently under one usage - I cant use Cursor coding as I need all allocation for Grok Bot
- Decrease Grok Bot token usage! It is only the Orchestrater - it should not need to handle it all.
- Allow users bringing their other Provider subscriptions to be used through Grok Bot - This then gives Grok Bot its identity as a the neutral orchestrator interface - gaining acceptance on a large scale.
- Improve grok bot UI and features in its role as the Orchestrator and Job / Board manager.