使用 Drifting 时遇到问题，可以发邮件给我们，也可以在 GitHub 上提交 Issue。
系统要求
Drifting 目前只支持搭载 Apple 芯片的 Mac，需要 macOS 13 或更新版本。Intel Mac、Windows、Linux 和移动设备暂不支持。官方安装包在 GitHub Releases 发布。
报告问题
请附上：
- Drifting 版本（设定 → 关于 Drifting）；
- macOS 版本和 Mac 型号；
- 复现步骤、你期望的结果和实际发生的情况；
- 相关的错误提示或截图。
也可以附上 设定 → 隐私 → 脱敏诊断摘要 中“复制摘要”的内容。它只包含版本、平台、功能可用性、同步计数与错误类别，不含稿件、凭据、项目标识或绝对路径。
请不要发送私人稿件内容、数据库文件、API Key、登录令牌，或带有这些信息的截图。GitHub Issues 是公开的。发送邮件后，我们会收到你的地址和邮件内容，只用于处理这次请求；详情及删除方式见隐私政策。
已知问题
报告之前可以先看看已知问题。
数据在哪里
资料库、导入的素材、Agent 对话和数据库安全快照都保存在
~/Library/Application Support/cc.drifting.client/（在访达中按 ⇧⌘G
并输入这个路径）。资料库数据库是其中的 databases/drifting-library.db。Drifting
运行时请不要移动或修改这些文件。
每个项目的 Markdown 文件夹默认也在这里，位置可以在 设定 → 同步与数据 → 本地数据 中查看和更改。其中章节和构想文件可以用其他编辑器修改，修改会合并回 Drifting；其余文件只读。
备份与恢复
在 设定 → 同步与数据 → 本地数据 → 资料库备份 中选择“导出备份…”，Drifting
会把所有项目的数据库和图片、PDF 原文件打包成一个 .drifting
文件，可以用来恢复，也可以带到另一台电脑。恢复时选择“选择备份…”，当前资料库会先自动保存一份恢复前副本。
同步开启时暂时无法备份或恢复，需要先在 设定 → 账号 中断开同步。Markdown 导出便于阅读，但不是完整备份；Hosted 同步也不能代替备份。
Hosted 账号与同步
Hosted 是可选的。请在每台 Mac 上登录同一个账号。退出登录或断开同步会保留本机项目和云端副本；从 Hosted 永久删除项目需要联网并登录拥有该项目的账号。要删除账号，请用账号邮箱发邮件到 support@drifting.cc。
安全问题
请通过 GitHub 仓库 Security 标签页的私密漏洞报告提交，不要在公开 Issue 中写漏洞细节、API Key、稿件、数据库或个人信息。请写明受影响的版本、平台、影响和复现步骤，以及概念验证中是否含有敏感数据。我们会尽量在 7 天内确认收到。如果私密报告暂时不可用，请开一个不含漏洞细节的简短 Issue，请维护者开启私密渠道。
GitHub
你可以在 GitHub 查看 Drifting 的源代码（AGPL-3.0-or-later）并提交技术问题。
If you run into a problem with Drifting, email us or open an issue on GitHub.
Requirements
Drifting currently supports Macs with Apple silicon running macOS 13 or later. Intel Macs, Windows, Linux and mobile devices are not supported yet. Official installers are published on GitHub Releases.
Reporting a problem
Please include:
- your Drifting version (Settings → About Drifting);
- your macOS version and Mac model;
- steps to reproduce, what you expected and what happened;
- any relevant error message or screenshot.
You can also paste the output of Settings → Privacy → Sanitized diagnostic summary → Copy summary. It contains only versions, platform, feature availability, sync counts and error categories, with no manuscript, credentials, project identifiers or absolute paths.
Never send private manuscript text, database files, API keys, sign-in tokens, or screenshots showing them. GitHub Issues are public. When you email us, we receive your address and message and use them only to handle your request; see the Privacy Policy for details and deletion options.
Known issues
Before reporting, check the known issues.
Where your data lives
Your library, imported materials, Agent conversations and database safety snapshots are
stored in ~/Library/Application Support/cc.drifting.client/ (press ⇧⌘G in Finder
and enter the path). The library database is
databases/drifting-library.db inside it. Do not move or edit these files while
Drifting is running.
Each project's Markdown folder is also there by default; see or change its location in Settings → Sync & Data → Local data. Chapter and idea files in it can be edited in other editors and merge back into Drifting; the other files are read-only.
Backup and restore
In Settings → Sync & Data → Local data → Library backup, choose Export backup… to package
every project's database with the original images and PDFs into one
.drifting file. Use it to restore or to move to another computer. To restore,
choose Choose backup…; the current library is saved as a pre-restore copy first.
Backup and restore are unavailable while sync is on; disconnect sync in Settings → Account first. Markdown export is readable but is not a complete backup, and Hosted sync does not replace a backup.
Hosted account and sync
Hosted is optional. Sign in to the same account on each Mac. Signing out or disconnecting sync keeps your local projects and the cloud copies; permanently deleting a project from Hosted requires a connection and the account that owns it. To delete your account, email support@drifting.cc from your account address.
Security issues
Use GitHub's private vulnerability reporting under the repository's Security tab. Do not put exploit details, API keys, manuscripts, databases or personal data in a public issue. Include the affected version, platform, impact, reproduction steps, and whether a proof of concept contains sensitive data. We aim to acknowledge reports within seven days. If private reporting is temporarily unavailable, open a minimal issue asking the maintainer to enable a private channel, without vulnerability details.
GitHub
You can view the Drifting source code (AGPL-3.0-or-later) and report technical issues on GitHub.