Skip to content

docs: promote HRouter and add the consultation email - #22

Merged
honestTai merged 1 commit into
mainfrom
cursor/promote-hrouter-docs-19df
Oct 25, 2026
Merged

honestTai merged 1 commit into
mainfrom
cursor/promote-hrouter-docs-19df

Conversation

@honestTai

Copy link
Copy Markdown
Owner

Summary / 概述

Adds a short, bilingual pointer to HRouter in the Desktop READMEs, and sends HRouter account, billing, and consultation mail to honesttibo@mail.grokbot.com.

  • README.md and README_ZH.md keep the provider-neutral quick start. A new Need model API access? / 需要模型 API 接入? section sits right after it, with the same note repeated under Get started. It links to https://hrouter.net and https://hrouter.net/home, states the one-key value prop (Claude, GPT, Gemini, and Grok for coding agents), and says Desktop configures that gateway like any other provider.
  • SUPPORT.md adds honesttibo@mail.grokbot.com next to the existing hrouter.net link for account, plan, billing, and consultation.
  • Security reporting is unchanged: SECURITY.md and the support page still direct vulnerability reports to GitHub Security Advisories.
  • MIT / CC Switch attribution, app code, package versions, and release assets are untouched.

Related Issue / 关联 Issue

No linked issue.

Screenshots / 截图

Docs-only change. No UI screenshots.

Checklist / 检查清单

  • Docs-only. No TypeScript, Rust, i18n, or release assets changed, so typecheck, format, and Clippy were not run.
  • English and Chinese READMEs both promote hrouter.net.
  • Consultation email is honesttibo@mail.grokbot.com on the support page and in the new README sections.
  • Security reports stay on GitHub Security Advisories.
Open in Web Open in Cursor 

Point readers at hrouter.net as the prepaid relay for coding agents, and send HRouter account, billing, and consultation mail to honesttibo@mail.grokbot.com. Security reports stay on GitHub Security Advisories.

Co-authored-by: HRouter <honestTai@users.noreply.github.com>
@honestTai
honestTai merged commit ade36f3 into main Oct 25, 2026
4 checks passed
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.

2 participants