@vmayoral thank you so much for sharing your thoughts and ideas.
How about a init subverb which initiates a new conversation and packs the most representative (if not all) ROS graph data and passes it over for digestion, so that future queries take that into account.
yeah, that would be interesting. so that AI can help user more precisely and dedicated to the environment.
btw, i consider some ideas about session with
context-aware mode, i gotta spend some more time to figure that out, instead of playing NintendoSwitch (should be PlayStation ) …
Subverbs update and summarize come to mind as well, which could build upon the init one proposed above (and with a similar mindset).
I see, this would be useful too, good idea.
Actually I am kinda inclined to have much less subcommands in the future but only
ros2 ai, so that user just relies on calling simple commands without being bothered by sub-commands and options…
which is costly AFAIK
true, I personally use my own API key. I need funding
it would be really nice if we could have community support for this, we can get more scaled data for ROS 2 and that could be really useful for ROS 2 community as well.
to be honest, the pain is not the cost right now, but latency. API is kinda lagging… i guess, i need to find some better fine tuning…
all that said, i just have some ideas but concrete, i will post the issues and slide to share more details