Skip to main content
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 the build-ultracart-storefronts skill 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 environmentWhere it runsinit --targetWhere the skill landsSign-inStatus
Claude CodeDesktop, or a containerclaude<workspace>/.claude/skills/Keychain on a desktop; encrypted file in a containerSupported
CodexDesktop, or a containercodex<workspace>/.agents/skills/Keychain on a desktop; encrypted file in a containerSupported
Google Antigravity (CLI, IDE and app)Desktopgemini (or codex)<workspace>/.agents/skills/KeychainSupported
Hermes AgentDesktop, server or containerhermes<Hermes home>/skills/, shared by every workspace on the machineKeychain on a machine that has one; encrypted file in a container or cloudSupported
OpenClawDesktop, server or containercodex<workspace>/.agents/skills/Keychain on a machine that has one; encrypted file in a container or cloudWorks with caveats
Grok BotHosted cloud computercodex; the Bot reads the skill file when asked/workspace/<workspace>/.agents/skills/; Grok Bot does not load skill folders by itselfEncrypted file, key in the Bot's secretsDocumented
Cursor, GitHub Copilot, OpenCode and other shell agentsDesktopcodex (no dedicated target).agents/skills/; Copilot in VS Code documents only .github/skills/KeychainWorks with caveats
Gemini CLI (Enterprise and API-key accounts only)Desktopgemini<workspace>/.agents/skills/KeychainDocumented
Docker, Fly.io and CI runnersContainer or CI machineThe agent's own targetInside the image or volumeEncrypted file, key from the platform's secretsDocumented
Muse (Meta)HostedNoneNoneNot possible: no way to pass a saved secret to the agent's shell commandsNot supported yet

What the status means​

  • Supported: init installs 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 status reports 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 for build-ultracart-storefronts.
  • Where will the sign-in go? uc-storefront auth status prints a credential store: line and a credential key: line without showing any secret. A keychain store (macos-keychain, windows-credential-manager or linux-secret-service) means the desktop sign-in applies. encrypted-file means you need the credential key first.
  • Is this address approved? If commands stop with location_approval_required, the agent runs uc-storefront auth approve-location and 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 runs auth login --continue --wait until it exits 0. Exit 3 means the sign-in is still waiting for you. Connect your store has the full sign-in steps.

Next steps​

Was this page helpful?