Skip to content

when reporting for host for flutter_tools, we should report for 'CLI' host #22214

Open

Description

@devoncarew commented on Sep 21, 2018, 3:10 PM UTC:

We report the host for flutter_tools runs - this is used to know which IDE is driving flutter_tools; we key off the value of the FLUTTER_HOST environment variable. It would be nice to also report a 'host' for pure CLI usage. We could infer this by there being no value set for FLUTTER_HOST, and for the entrypoint command into the tool not being the daemon command (or, flutter run --machine).

We should also update the docs for building tools on flutter_tools to specify that IDEs - and people driving flutter_tools - should specify an FLUTTER_HOST env variable.

cc @mit-mit

This issue was moved by devoncarew from dart-lang/sdk#34543.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Sep 24, 2018
  2. added this to the milestone on Feb 14, 2019
  3. added
    P2Important issues not at the top of the work list
    on May 29, 2020
  4. removed this from the milestone on Aug 17, 2020
  5. self-assigned this
    on Jun 27, 2025
  6. added
    tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.
    on Jun 30, 2025
  7. flutter-triage-bot commented on Nov 3, 2025

    @flutter-triage-bot

    This issue is assigned to @bkonyi but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  8. added
    ⏳Bot is counting down the days until it unassigns the issue
    on Nov 3, 2025
  9. flutter-triage-bot commented on Nov 18, 2025

    @flutter-triage-bot

    This issue is assigned to @bkonyi but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  10. flutter-triage-bot commented on Jan 22, 2026

    @flutter-triage-bot

    This issue was assigned to @bkonyi but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.

  11. removed
    ⏳Bot is counting down the days until it unassigns the issue
    on Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: new featureNothing broken; request for a new capabilityteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions