Support
Pick the channel that matches the request:
| Need | Context | Agent Graph |
|---|---|---|
| Usage, integration or design question | Discussions | Discussions |
| Reproducible defect | Bug report | Bug report |
| Suspected vulnerability | Private report | Private report |
Agent Graph Discussions also take ideas that are not yet actionable. Both projects point to this site first, and the answer is often already here: Installation for setup checks, Asking Questions for querying knowledge, and the FAQ.
Check before reporting
- Installation.
context --versionandcontext plugin statusconfirm the CLI and the host plugins. If an entry is present but thecontextexecutable is missing, the entry names the installation step to run. - Workflow state.
context status --format jsonshows the current Route, its reason code and diagnostics. Resume from that Route rather than repeating an earlier command. - Traces.
context debug enablerecords workspace-local traces under.tmp/context-runtime/debug/, andcontext debug exportbuilds a replay you can inspect; see CLI Commands. - Agent Graph.
npx @c4a/agent-graph validate --format jsonloads the whole Provider and returns a structured error without side effects, and the Graph tests replay Routes without a host, which makes a minimal reproduction easy to share; see Testing and Publishing.
What to include in a bug report
| Context | Agent Graph |
|---|---|
Context version (context --version) and installation mode | Agent Graph version |
| Node.js and Bun versions | Node.js and Bun versions |
| The Agent host, such as Claude Code, Codex or Cursor | |
| The command or entry you ran | The command you ran |
| Sanitized diagnostic output | The complete error output, secrets removed |
| A minimal Provider or Graph, when possible |
Keep private material out of public Issues. For Context, do not publish source documents, review payloads, credentials, private paths or knowledge generated from a private workspace; reduce the case to neutral content instead.
Security
Do not open a public Issue for a suspected vulnerability. Both projects use GitHub's private vulnerability reporting (links above). Include:
- the affected version and component;
- reproduction steps or a proof of concept;
- the security impact;
- any suggested mitigation;
- whether the issue has been disclosed elsewhere.
Context applies security fixes to its latest published release; Agent Graph, which is pre-1.0, applies them to its latest published minor line, so upgrade before reporting if you can. Agent Graph maintainers aim to acknowledge a report within five business days and, after validation, coordinate the fix, disclosure timing and credit with the reporter.
In scope are unsafe file access, command execution, path traversal, credential or source disclosure, authority and trust-boundary bypasses, integrity failures of packages and build artifacts, and — for Context — review-gate bypasses. Vulnerabilities can be in any published part: the CLI, SDK, extractors, plugins, schemas or artifacts. General questions and ordinary bugs belong in Discussions or Issues.
支持
按需求选择渠道：
| 需求 | Context | Agent Graph |
|---|---|---|
| 使用、集成或设计问题 | Discussions | Discussions |
| 可复现的缺陷 | 问题报告 | 问题报告 |
| 疑似安全漏洞 | 私下报告 | 私下报告 |
Agent Graph 的 Discussions 也接受尚不能落地的想法。两个项目都优先指向本站，答案往往已经在这里：安装检查见安装，查询知识见提问，另有常见问题。
报告前先检查
- 安装。
context --version和context plugin status用于确认 CLI 和宿主插件。如果入口存在但缺少context可执行文件，入口会指出需要执行的安装步骤。 - 工作流状态。
context status --format json显示当前 Route、它的原因码和诊断信息。请从这个 Route 继续，而不是重复之前的命令。 - 追踪。
context debug enable会在.tmp/context-runtime/debug/下记录知识工作区本地的追踪，context debug export会生成可供查看的回放；参见 CLI 命令。 - Agent Graph。
npx @c4a/agent-graph validate --format json会加载整个 Provider，无副作用地返回结构化错误；Graph 测试无需宿主即可重放 Route，便于分享最小复现；参见测试与发布。
问题报告应包含什么
| Context | Agent Graph |
|---|---|
Context 版本（context --version）和安装方式 | Agent Graph 版本 |
| Node.js 和 Bun 版本 | Node.js 和 Bun 版本 |
| Agent 宿主，例如 Claude Code、Codex 或 Cursor | |
| 你运行的命令或入口 | 你运行的命令 |
| 脱敏后的诊断输出 | 完整的错误输出，去掉密钥 |
| 尽可能附上最小的 Provider 或 Graph |
不要把私有材料放进公开 Issue。对 Context，不要公开来源文档、审核载荷、凭证、私有路径或由私有知识工作区生成的知识；请把问题缩减为中性的内容。
安全
不要为疑似漏洞开公开 Issue。两个项目都使用 GitHub 的私下漏洞报告（链接见上文）。请包含：
- 受影响的版本和组件；
- 复现步骤或概念验证；
- 安全影响；
- 建议的缓解措施（如有）；
- 该问题是否已在其他地方披露。
Context 的安全修复只针对最新发布的版本；Agent Graph 尚处于 1.0 之前，修复只针对最新发布的次版本系列，因此报告前最好先升级。Agent Graph 维护者力争在五个工作日内确认收到报告，验证后与报告者协调修复、披露时间和致谢。
适用范围包括不安全的文件访问、命令执行、路径穿越、凭证或来源泄露、授权与信任边界绕过、知识包和构建产物的完整性问题，以及 Context 的审核 Gate 绕过。漏洞可能存在于任何已发布的部分：CLI、SDK、提取器、插件、schema 或产物。一般问题和普通缺陷请使用 Discussions 或 Issues。