Describe the bug
After installing PowerContext via the README.md / Quick Start path, users face two usability issues:
-
Lack of Skills guidance — users don't know how to use artifact capabilities (Memory, Experience, Skill, Handoff, Profile, Topic Memory, etc.) and need to check multiple times to confirm whether these features are actually enabled.
-
Missing Hook trust prompt — when a user starts a new Codex session for the first time after installation, Codex prompts whether to trust the PowerContext UserPromptSubmit Hook, but the README/Quick Start does not mention this step. Users may be confused by the trust prompt, not know what to do, or accidentally skip it — causing the Hook (auto Source capture + context recall) to be silently disabled without the user realizing it.
Steps to reproduce
- Open Codex (already installed and logged in)
- Tell Codex: Help me install PowerContext: https://github.com/oceanbase/powercontext
Expected behavior
After installation, the user should immediately understand:
- What capabilities exist — a capability matrix listing 7 Artifact families + Source + Tag, each with a description and trigger method
- How to trigger each capability — a Codex conversation example for each (e.g., "remember xxx" triggers Memory, "handoff" triggers Handoff)
- Which require LLM, which do not — clearly label Basic memory mode vs Full memory mode capability differences
- Skill approval ≠ installation — explicitly state that after approval, the Skill still needs to be exported and installed to the Agent's local directory
- What the Hook does automatically — explain that UserPromptSubmit Hook auto-captures Source and recalls context
- Hook trust is required on first session — explicitly state that the first new Codex session requires trusting the PowerContext Hook, and explain what happens if not trusted
Actual behavior
Codex follows the Quick Start / README.md approach and executes the installation commands:
Environment
No response
Are you willing to submit a PR to fix this bug?
Describe the bug
After installing PowerContext via the README.md / Quick Start path, users face two usability issues:
Lack of Skills guidance — users don't know how to use artifact capabilities (Memory, Experience, Skill, Handoff, Profile, Topic Memory, etc.) and need to check multiple times to confirm whether these features are actually enabled.
Missing Hook trust prompt — when a user starts a new Codex session for the first time after installation, Codex prompts whether to trust the PowerContext
UserPromptSubmitHook, but the README/Quick Start does not mention this step. Users may be confused by the trust prompt, not know what to do, or accidentally skip it — causing the Hook (auto Source capture + context recall) to be silently disabled without the user realizing it.Steps to reproduce
Expected behavior
After installation, the user should immediately understand:
Actual behavior
Codex follows the Quick Start / README.md approach and executes the installation commands:
Environment
No response
Are you willing to submit a PR to fix this bug?