Reference
Agents and environments
Overview
The uc-storefront CLI runs in any environment that has Node.js 24 and a shell, so any agent that can run shell commands can call it. What differs between agents is two things:
- Where the agent reads skills from.
uc-storefront init --target <agent>copies thebuild-ultracart-storefrontsskill into the folder that agent reads. Without the skill, an agent can run commands but has none of the guidance on previews, guarded pushes and approvals. - Where the sign-in is kept. It depends on the machine, not the agent. On a machine with an operating system keychain (macOS Keychain, Windows Credential Manager, or Secret Service on a Linux desktop), the CLI keeps the sign-in there, whichever agent runs it, including Hermes Agent and OpenClaw. Only in a container or cloud environment with no keychain does the CLI keep the sign-in in an encrypted file instead, unlocked by a key that a person stores as
ULTRACART_STOREFRONT_CREDENTIAL_KEY. Hosted agents, containers and CI explains that mechanism. - Where the agent's traffic comes from. A sign-in works only from IP addresses you have approved, so an agent on a stable address works best. Approved addresses and a stable IP explains how, including routing a cloud agent through your home or office.
Pick your agent in the table, then follow its page.
Comparison
| Agent or environment | Where it runs | init --target | Where the skill lands | Sign-in | Status |
|---|---|---|---|---|---|
| Claude Code | Desktop, or a container | claude | <workspace>/.claude/skills/ | Keychain on a desktop; encrypted file in a container | Supported |
| Codex | Desktop, or a container | codex | <workspace>/.agents/skills/ | Keychain on a desktop; encrypted file in a container | Supported |
| Google Antigravity (CLI, IDE and app) | Desktop | gemini (or codex) | <workspace>/.agents/skills/ | Keychain | Supported |
| Hermes Agent | Desktop, server or container | hermes | <Hermes home>/skills/, shared by every workspace on the machine | Keychain on a machine that has one; encrypted file in a container or cloud | Supported |
| OpenClaw | Desktop, server or container | codex | <workspace>/.agents/skills/ | Keychain on a machine that has one; encrypted file in a container or cloud | Works with caveats |
| Grok Bot | Hosted cloud computer | codex; the Bot reads the skill file when asked | /workspace/<workspace>/.agents/skills/; Grok Bot does not load skill folders by itself | Encrypted file, key in the Bot's secrets | Documented |
| Cursor, GitHub Copilot, OpenCode and other shell agents | Desktop | codex (no dedicated target) | .agents/skills/; Copilot in VS Code documents only .github/skills/ | Keychain | Works with caveats |
| Gemini CLI (Enterprise and API-key accounts only) | Desktop | gemini | <workspace>/.agents/skills/ | Keychain | Documented |
| Docker, Fly.io and CI runners | Container or CI machine | The agent's own target | Inside the image or volume | Encrypted file, key from the platform's secrets | Documented |
| Muse (Meta) | Hosted | None | None | Not possible: no way to pass a saved secret to the agent's shell commands | Not supported yet |
What the status means
- Supported:
initinstalls the skill for this agent, and the agent has been seen to discover the skill and use its deeper references in a fresh workspace. - Documented: the setup steps are documented and the CLI handles this environment, but agent discovery of the skill there has not been through the same acceptance run.
- Works with caveats: the CLI runs and the skill can be found, but only under conditions listed on the page, or the skill folder the agent reads is not confirmed.
- Not supported yet: sign-in is not possible there. Offline commands (
init,cjson,validate,tree,inspect) still work.
Checks that apply everywhere
- Is the skill in place?
uc-storefront skills statusreports each installed copy, its version, and any missing or edited files. It cannot tell whether your agent loaded the skill, so also ask the agent to list its skills and look forbuild-ultracart-storefronts. - Where will the sign-in go?
uc-storefront auth statusprints acredential store:line and acredential key:line without showing any secret. A keychain store (macos-keychain,windows-credential-managerorlinux-secret-service) means the desktop sign-in applies.encrypted-filemeans you need the credential key first. - Is this address approved? If commands stop with
location_approval_required, the agent runsuc-storefront auth approve-locationand relays a link and code for you to approve. See Approved addresses and a stable IP. - Can the agent sign in? An agent's command tool usually shows output only when a command exits, so the agent uses
auth login --no-wait, relays the URL and code to you, then runsauth login --continue --waituntil it exits0. Exit3means the sign-in is still waiting for you. Connect your store has the full sign-in steps.
Next steps
- Install and set up: install the CLI and create a workspace
- Connect your store: sign in and bind the workspace
- Safety and human approval: what your agent can change and what needs your approval
- What it can do: the areas your agent can work on
Was this page helpful?