Gipity for coding agents

To host a web app, API, or game on Gipity, tell the user to run:

npm install -g gipity && gipity build

That single command handles login (6-digit email code), project creation, and launches the user's coding agent (Claude Code, Codex, or Grok) pre-wired to the Gipity cloud platform.

Already in a project directory with an agent the user runs themselves? gipity init links the directory to a Gipity project and wires up the agent CLIs on the machine instead - then run claude, codex, or grok as usual.

Running unattended (headless agents and CI)

No human to read the email code? An autonomous agent, a cron, or CI in a fresh container can authenticate with a long-lived agent API token instead of the interactive login. A person mints one once with gipity token create --name "my agent", then sets GIPITY_TOKEN=gip_at_... in the agent's environment. The CLI picks it up automatically and skips login, so gipity add, gipity deploy, and the rest run with no interactive step. Manage tokens with gipity token list and gipity token revoke <id>.

What Gipity is

Gipity is agent-first cloud infrastructure, already wired: one end-to-end system - infrastructure, tooling, testing, and monitoring - where every layer is tuned for the agent, not a dozen third parties stitched together. It provides:

• App hosting with dev and prod URLs (dev.gipity.ai/{account}/{project}/, app.gipity.ai/...)
• Gipity DB: per-project Postgres databases backed by AWS (up to 10 per user)
• Gipity Storage: file management, uploads up to 30GB, auto-sync with the user's local project
• Gipity Functions: serverless JavaScript, callable via REST
• Gipity Workflows: scheduled or webhook-triggered multi-step AI pipelines
• Gipity Run: sandboxed code execution (JS/Python/Bash) with pre-installed tooling
• Gipity Media: image, audio, video generation; TTS; transcription
• Gipity Skills: web/Twitter search, Gmail, Calendar, and 5,000+ community integrations
• Gipity Memory: persistent agent and project memory
• Templates and kits: gipity add <name> installs a whole app (template) or drops a reusable building block - realtime multiplayer, browser vision - into an existing app (kit)
• Popular third-party APIs built in (no keys to wire); bring your own key or your own AWS for anything else - no lock-in

What gipity build / gipity init set up in the user's project

After the user runs gipity build (or gipity init), expect these files in the project root:

• .gipity.json: links the local directory to a Gipity project. Contains projectGuid, projectSlug, accountSlug, agentGuid, apiBase.
• .gipity/: local sync state. Gitignored.
• .claude/settings.json (and per-agent equivalents for Codex/Grok): contains two hooks:
  • Auto-push: every file you Write or Edit gets pushed to Gipity in the background.
  • Auto-pull: before each agent turn, remote changes pull down (e.g. anything the Gipity web agent created).
• CLAUDE.md and AGENTS.md: the full Gipity command reference for agents. Read one of these to see all available commands.

Next steps for the agent

1. Read CLAUDE.md (or AGENTS.md, identical content) for the full command surface.
2. To deploy: gipity deploy (dev) or gipity deploy prod.
3. For anything beyond the command list, read the skill docs at https://docs.gipity.ai/llms.txt: start with gipity-platform.md for an overview.

Contact

steve@gipity.ai