# AGENTS.md — working with ohmyho.st

ohmyho.st hosts Astro, Next.js, Vite/React and TanStack apps, keeps their versions with ohmyho.st or connects a GitHub repository the customer authorizes. Postgres, domains, transactional mail and credits use one organization balance. Operate through authenticated remote MCP, the ohmyhost CLI, local stdio MCP or the REST /v1 API, using the capabilities available in this client.

1. Read https://ohmyho.st/llms.txt, the get-started Skill at https://ohmyho.st/skills/ohmyhost-get-started/SKILL.md and the source-routing Skill at https://ohmyho.st/skills/ohmyhost-deploy/SKILL.md.
2. Inspect the execution environment, reachable checkout and saved project binding; reuse a matching local CLI/MCP profile or private token source unless the user explicitly chooses remote access. The availability of remote tools alone does not choose a route; verify the chosen identity and workspace with identity_get before continuing, and stop on a mismatch. A supported remote chat connects https://app.ohmyho.st/mcp through OAuth. A local agent installs current clients when needed and keeps the sign-in link/code flow from `ohmyhost login --json`. Never paste credentials into chat.
3. Reuse the existing project; read project_context_get and source_get before acting. The server's current source binding comes first. Choose a new source from the actual checkout and the customer's preference: a new app developed entirely in chat keeps versions with ohmyho.st; an explicitly selected GitHub repository uses GitHub. For an unbound local checkout without GitHub, ask once whether to keep versions with ohmyho.st or set up GitHub. An explicit choice skips that question. Source choice follows the app across local and cloud agents.
4. Keep the customer's authentication provider, region, data and existing project URLs. Deliver remote-chat secrets through secret_input_request and its private portal link; local agents use the stdin command from secret_set_command. Plan the exact saved commit with deployment_plan, run deployment_create, observe its accepted operation and verify Dev. Publish only when requested and authorized, using the deployment Skill's guarded promotion flow.
5. Discover remote tools from the connected server; read the local catalog at https://ohmyho.st/mcp-tools.json and API errors at https://docs.ohmyho.st/limits.md. Reuse the original operation and idempotency key after uncertainty. Connection, source saving and a successful build each need their own returned proof; report a working address only after app verification.

Pricing and limits: https://ohmyho.st/pricing.md · https://docs.ohmyho.st/limits.md · Report a defect: the feedback_submit tool.