Skip to content

docs(LLM provider): Add usage tracking Note to OpenHands provider page - #92

Merged
mamoodi merged 5 commits into
mainfrom
docs/add-usage-tracking-note-openhands-provider
Nov 25, 2025
Merged

mamoodi merged 5 commits into
mainfrom
docs/add-usage-tracking-note-openhands-provider

Conversation

@enyst

@enyst enyst commented Nov 7, 2025

Copy link
Copy Markdown
Member

This PR adds a Note to the OpenHands LLM provider documentation clarifying minimal usage tracking:

  • Inserted immediately after the API key instructions image and before the models table, as requested
  • Explains that when using OpenHands as a provider, minimal usage tracking is performed to understand whether models are used for the agent, condenser, or other uses
  • States that this data is sent to All Hands AI to improve the OpenHands experience and that we never sell this data

File changed:

  • openhands/usage/llms/openhands-llms.mdx

Let me know if you'd like the Note positioned elsewhere or reworded.

@enyst can click here to continue refining the PR

Add a Note after the API key instructions and before the models table to clarify minimal usage tracking sent to All Hands AI and that we never sell data.

Co-authored-by: openhands <openhands@all-hands.dev>
Comment thread openhands/usage/llms/openhands-llms.mdx Outdated
…ion; clarify metadata is sent to All Hands AI\n\nPer reviewer feedback, relocate the Note from after API key to the CLI section and simplify wording while retaining that minimal metadata is sent to All Hands AI to improve the experience.\n\nCo-authored-by: openhands <openhands@all-hands.dev>
…; explicitly mention metadata is sent to All Hands AI\n\nCo-authored-by: openhands <openhands@all-hands.dev>

@neubig neubig left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In a previous comment I requested that this include a link to our privacy policy, instead of posting specifically about what it is or is not used for, since that may get out of sync. I think we should do that before changing the wording here: https://openhands.dev/privacy

Comment thread openhands/usage/llms/openhands-llms.mdx Outdated
…eedback\n\nReplace explicit data-use statement with a link to https://openhands.dev/privacy to avoid drift.\n\nCo-authored-by: openhands <openhands@all-hands.dev>
@enyst

enyst commented Nov 7, 2025

Copy link
Copy Markdown
Member Author

In a previous comment I requested that this include a link to our privacy policy, instead of posting specifically about what it is or is not used for, since that may get out of sync. I think we should do that before changing the wording here: https://openhands.dev/privacy

Done! WDYT, does this work?

@enyst
enyst requested a review from neubig November 7, 2025 16:54
@enyst

enyst commented Nov 7, 2025 •

Copy link
Copy Markdown
Member Author

In a previous comment I requested that this include a link to our privacy policy, instead of posting specifically about what it is or is not used for, since that may get out of sync. I think we should do that before changing the wording here: https://openhands.dev/privacy

FWIW I do see the concern that it’d get out of sync. But I’m not sure it’s the best way to express it to people.

The attempt in this PR is to say in plain English what happens, so that people know and it doesn’t come as a surprise. Maybe we should add what data is collected here, because if people don’t know it’s just ‘agent’ or ‘condenser’, and they find out later that OpenHands tracks their usage, they may fear the worst.

FWIW, I’ve seen at times something like, on some company site: “Tos in English” << with a plain English short explanation of what’s up, and then a link to the full legalese. I’m not good with words, to convey it, if you could imagine the Tos in English, it was fun, it had a lightweight tone and told people what’s happening and why. Maybe it’s worth thinking of this PR as the small version of that?

(It’s not like AH is going to sell this kind of data, right? So couldn’t we just say it doesn’t?)

@neubig neubig left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM now! And yes, I think it makes a lot of sense for us to try to create a simpler version of the privacy policy as well.

@mamoodi
mamoodi merged commit a08d7f0 into main Nov 25, 2025
3 checks passed
@mamoodi
mamoodi deleted the docs/add-usage-tracking-note-openhands-provider branch November 25, 2025 14:37

This branch was successfully deployed

1 active deployment
staging — df944d40 Deployed Nov 7, 2025 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants