Support

Email linyishan@gmail.com or visit the project repository.

Never include API keys, passwords or private post text in a support request.

Labels do not appear

Open Settings from the popup, read the data notice, check the acknowledgement and click Agree and enable. TypeSafe is the default service. For a custom compatible API, save its full HTTPS URL and grant host access first, then consent and enter a key issued for that service. Existing users also need to consent when upgrading to 0.1.3.
Open an X page containing text posts. Refresh existing pages after installing or updating the extension.
Check Skip replies and the status panel. A 401 error usually indicates an invalid key; provider credits or access may also be required.
After fixing credentials or a temporary network error, pause and resume to retry failed posts.

Stop requests or delete local data

Pause or withdraw consent first. Clear cache in Settings removes local judgments, not your API key. Empty the key field and move focus to save the change. Uninstall to remove the extension's local storage. Contact the selected provider for provider-side deletion.

Report an issue

Include the extension and Chrome versions, operating system, selected language, steps to reproduce and a redacted screenshot. Labels are model estimates; a prediction alone does not establish wrongdoing or authorship.

中文帮助

联系 linyishan@gmail.com。请勿发送 API key、密码或私密正文。

没有标签时，先从弹窗打开设置页并阅读说明、勾选同意项并点击“同意并启用”（旧用户升级到 0.1.3 也需要确认），默认使用 TypeSafe；自定义兼容 API 须先保存完整 HTTPS URL 并授权域名，再同意及填写该服务的 key。然后检查 key、启用开关和“跳过回复”及状态面板。安装或升级后刷新 X 页面。修正凭证或网络问题后，可暂停再恢复以重试。删除本地数据时先暂停或撤回同意，再到设置页清缓存；清缓存不会删除 key，需要另行清空输入框并移出焦点保存。

反馈时附上扩展与 Chrome 版本、系统、界面语言、复现步骤及脱敏截图。