Codex / ChatGPT Pack

The workflow, boundaries, and safety behavior are identical to the Claude Code pack — only the packaging differs.

Install steps (Codex)

1. Create a Gateway Key (ecosystem: Codex; default scopes gateway:read + gateway:submit_draft) and store it in the KEFUAGENT_GATEWAY_KEY environment variable.
2. Install SKILL.md to ~/.agents/skills/kefuagent-support/SKILL.md (frontmatter fields pending validation against your Codex release).
3. Place openai.example.yaml below as the skill's agents/openai.yaml to declare the MCP dependency for automatic wiring (schema pending validation; see the config.toml fallback below).
4. (Optional) Paste the snippet below into your project's AGENTS.md.
5. Ask Codex: "查一下 KefuAgents 有什么客服卡要处理".

agents/openai.yaml (raw file: /agent-packs/codex/openai.example.yaml)

# agents/openai.yaml — declares the KefuAgents gateway as an MCP dependency so
# the Codex environment wires the connection automatically.
# 待验证 [NEEDS VALIDATION]: exact schema/key names against the verified Codex
# release. Fallback: register the server in ~/.codex/config.toml instead
# ([mcp_servers.kefuagent] — see the docs page).
mcp_servers:
  kefuagent:
    transport: streamable_http
    url: https://kefuagents.com/api/gateway/mcp
    headers:
      Authorization: 'Bearer ${KEFUAGENT_GATEWAY_KEY}'

Fallback: ~/.codex/config.toml

If your Codex release does not support openai.yaml auto-wiring, register the remote MCP server in the user config instead (exact keys pending validation — follow your Codex release docs):

[mcp_servers.kefuagent]
url = "https://kefuagents.com/api/gateway/mcp"
# transport: Streamable HTTP; auth header:
# Authorization = "Bearer ${KEFUAGENT_GATEWAY_KEY}"

Keep the skill installed either way — it carries the workflow and boundaries independently of how the connection is wired.

AGENTS.md snippet (raw file: /agent-packs/codex/agents-md-snippet.md)

The snippet is maintained in Chinese (the merchant supervision language); it describes the five-action supervision model, the tool loop, and the safety boundaries. Copy it from the raw link above or the Chinese page.

ChatGPT connector notes (honesty over promise)

• ChatGPT connectors / Apps-SDK integrations consume the same MCP endpoint (https://kefuagents.com/api/gateway/mcp) — no separate build.
• Pending validation: whether the current ChatGPT connector UI can attach a static Authorization: Bearer header. Historically, hosted connectors offered OAuth or no-auth only. Until validated, treat it as unsupported: ChatGPT connectors do not currently accept a static key — use Codex to connect; an OAuth front-door is on the roadmap. Do not waste hours on an input field that may not exist.
• Either way the platform guarantees hold: the gate re-checks every draft, high-risk stays human, one key = one workspace, every call is audited.