If you are already using Codex, Claude Code, or Holon, the recommended onboarding path
is to hand the bundled AgentInbox skill to the agent and let it configure the
local workflow for you.
This is the preferred path for first-run setup. It avoids pushing the user
through raw source add, subscription add, and uxc auth commands before the
agent is ready.
If you use the community skills installer, install the bundled skill with:
npx skills add holon-run/agentinbox --skill agentinbox -a codex -a claude-code -a holonThe bundled skill lives at:
When used for onboarding, the skill should:
- verify
agentinboxis available inPATH - start or verify the local daemon
- verify
uxcis available - verify GitHub auth is usable
- if
ghis already authenticated, import that token intouxc - register the current runtime/session as an agent
- use the docs-site examples to add standing GitHub subscriptions
For Holon, registration should use HOLON_AGENT_ID plus
HOLON_EXTERNAL_TRIGGER_URL, or pass --webhook-url if the trigger URL is not
in the environment.
The agent should verify:
agentinbox --version
agentinbox daemon status
uxc --version
gh auth statusIf the daemon is not running:
agentinbox daemon startIf GitHub auth should be reused from gh:
uxc auth credential import github --from ghThis requires uxc 0.15.3 or newer:
Once uxc can access GitHub and the current runtime/session is registered, the
agent can move directly into real usage:
- add a shared GitHub host plus
repo_eventsorci_runsstreams - add standing subscriptions for review comments or CI failures
- add task-specific subscriptions for a PR or branch
- remove those subscriptions when the task is done
See:
AgentInbox onboarding is still evolving. The skill can absorb environment
checks, uxc auth reuse, and per-agent workflow setup without forcing the user
to manually learn every low-level CLI step first.