FAQ
AXHub FAQ updated against the current CLI/backend/plugin surfaces
Can I keep using apphub.yaml?
During migration, backend and CLI can still read legacy apphub.yaml, but the canonical filename is axhub.yaml. If both exist, axhub.yaml wins. New docs and projects should use axhub.yaml.
Did the CLI install domain change?
Yes. The current public installer domain is https://cli.axhub.ai.
curl -fsSL https://cli.axhub.ai/install.sh | bashWhere are MCP tools?
On the AxHub MCP server (https://mcp.axhub.ai/mcp). Connect an MCP client like Claude Code and you get 5 tools to browse the data catalog and run read-only SQL. See AxHub MCP for details.
Which deploy modes are supported?
The resolver supports axhub.yaml, Dockerfile, Compose files, and Railpack auto-detection. The app DB deploy_method is docker | compose and immutable after creation.
How does a user app read login identity?
Read ingress-propagated X-AxHub-* headers. Email/name are base64-encoded. The old X-AppHub-* names are not current backend behavior.
How do PAT and OAuth differ?
PAT (AXHUB_API_KEY) is for explicitly allowed surfaces such as /data/*, table DDL, and PAT management. App creation, deploys, GitHub connection, and tenant/member/admin work use OAuth device flow.