Skip to content
Discussion options

You must be logged in to vote

Not directly — but flutter-skill talks to your app via the Dart VM Service Protocol, which is the same underlying data source that DevTools uses. So there is significant overlap:

What flutter-skill CAN access (same data source as DevTools):

  • Widget tree / inspector (inspect, inspect_interactive)
  • Performance metrics (get_memory_stats)
  • App logs (get_logs)
  • Hot reload / hot restart
  • All registered VM Service extensions

What flutter-skill cannot currently access:

  • The DevTools UI itself (the browser dashboard)
  • CPU profiler / timeline recordings
  • The Network tab (unless your app registers dart:io HTTP overrides)

Workaround for the DevTools UI: If you open Flutter DevTools in Chrome, connect_cdp

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by finnvyrn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants