The sentry demo makes me wonder if this chat-based, IDE interface would be the preferred go-to for Devs for multi-tool, multi-step workflows? Or would they prefer to automate the flow as a background, asynchronous task?
> Or would they prefer to automate the flow as a background, asynchronous task?
Definitely want to use it for automation. When writing bindings for a large library it's helpful to have a script that picks several files as implementation examples then has Copilot write the rest by i.e. looping over library headers.
Definitely want to use it for automation. When writing bindings for a large library it's helpful to have a script that picks several files as implementation examples then has Copilot write the rest by i.e. looping over library headers.