Gagarin Cloud changelog

https://gagarin.cloud/llms.txt

−    `npx skills add gagarin-cloud/claude-plugin -g`, or in Claude Code−    `/plugin marketplace add gagarin-cloud/claude-plugin`. The skill is a− /plugin marketplace add gagarin-cloud/claude-plugin− That installs the skill, the MCP server, `/gagarin:setup`, `/gagarin:status`,− `/gagarin:ship`, and two subagents — one that takes a repository to a working− HTTPS URL, one that wires CI to deploy on push.− For any other harness, `npx skills add gagarin-cloud/claude-plugin -g` writes the− commands in order, and runs locally with `docker compose up --build`. The links− below are plain markdown.− - [The Claude Code plugin](https://github.com/gagarin-cloud/claude-plugin): the−   skill, the MCP server, commands and deploy agents as one install.+    `npx skills add gagarin-cloud/plugin -g`, or in Claude Code+    `/plugin marketplace add gagarin-cloud/plugin`. The skill is a+ /plugin marketplace add gagarin-cloud/plugin+ That installs the skill, the MCP server, and four more skills: `/gagarin:setup`,+ `/gagarin:status`, `/gagarin:ship` — which takes a repository to a working HTTPS+ URL — and `/gagarin:ci`, which wires CI to deploy on push. The same plugin is in+ ChatGPT's and Codex's shared Plugins Directory (search for Gagarin Cloud), or+ `codex plugin marketplace add gagarin-cloud/plugin` from the Codex CLI.+ For any other harness, `npx skills add gagarin-cloud/plugin -g` writes the+ commands in order, and runs locally with `docker compose up --build`. A page+ whose markdown has a `Deploy:` line also deploys in one click into a project of+ your own. Axon's code is a repository of its own, which its page links. The+ links below are plain markdown.+ - [Axon](https://gagarin.cloud/recipes/axon/index.md): per-project memory for+   agents, from its own repository; a size-m service, a postgres with pgvector and+   an external, private to the project.+ - [The plugin](https://github.com/gagarin-cloud/plugin): the skills and the MCP+   server as one install, for Claude Code, Codex and ChatGPT.+ - [Recipes](https://gagarin.cloud/docs/recipes): publish a project with+   `gg recipe snap`, and anyone deploys it into a project of their own from one+   link. What a snapshot carries, why env never holds secrets, inputs, versions.

version

0.5.0 → 0.6.0

version

0.4.0 → 0.5.0

version

0.3.0 → 0.4.0

https://gagarin.cloud/llms.txt

− 1. Install `gg`: `brew install --cask gagarin-cloud/tap/gg` on macOS, or−    `go install github.com/gagarin-cloud/gg@latest`, or take a binary−    from https://github.com/gagarin-cloud/gg/releases and verify its checksum.−    Without `--cask`, Homebrew installs an old formula that no longer updates.−    separate thing from the binary and may be newer than it; if a command in it−    is refused as unknown, check `gg version` before concluding it does not−    exist.−   qdrant, valkey, iggy, s3 or external (credentials a user supplies).−   `gg resource restore` brings one back.−   rest as one-line index entries. This is cheaper than reading the repository and−   it tells you things the repository does not say.− tags, file paths and kinds are not, and Gagarin holds the key. Reading needs+ 1. Install `gg`. On macOS or Linux:+    `curl -fsSL https://gagarin.cloud/install.sh | sh`. On Windows, in PowerShell:+    `irm https://gagarin.cloud/install.ps1 | iex`. The script checks the download+    against the release's checksums.txt, installs to `~/.local/bin` without sudo,+    and never edits shell profiles: if that directory is not on PATH it prints+    the line to add. If your harness refuses to pipe into `sh`, run+    `curl -fsSLo install.sh https://gagarin.cloud/install.sh && sh install.sh`.+    Alternatives: `brew install --cask gagarin-cloud/tap/gg` (macOS; keep+    `--cask`, without it Homebrew installs an old formula that no longer updates),+    `scoop bucket add gagarin https://github.com/gagarin-cloud/scoop-bucket && scoop install gagarin/gg`+    or `winget install Gagarin.gg` (Windows), `go install github.com/gagarin-cloud/gg@latest`+    (anywhere with Go), or a .deb, .rpm or .apk package from+    https://github.com/gagarin-cloud/gg/releases.+    If `gg` is already installed but a command is refused as unknown, it is+    probably old: run `gg upgrade`, which upgrades it the way it was installed.+    A gg older than v0.54.0 has no `gg upgrade`; run the install line again.+    separate thing from the binary and may be newer than it.+   qdrant, valkey, iggy, rabbitmq, s3 or external (credentials a user supplies).+   A postgres takes `extensions` — the whole set, named as `CREATE EXTENSION`+   names them (`vector` for pgvector, `postgis`, `pg_cron`, `pg_trgm` and more):+   adding one is immediate with no restart, leaving the field out keeps them as+   they are, and dropping one asks no one, because it refuses rather than loses+   anything: it never cascades, and it is refused (`extensions_failed`) while a+   column uses the extension or its own tables hold your data, such as+   pg_cron's jobs. `gg resource add shop/db postgres --ext vector --ext postgis`.+   `gg resource restore` brings one back. A rabbitmq is not backed up.+   rest as one-line index entries, and what changed in the last 7 days at the end.+   Pass `focus` (what you are about to work on) and `paths` (the files you expect+   to touch) and the memories that concern them come first. This is cheaper than+   reading the repository and it tells you things the repository does not say.+   When the fact is one that changes, give it a `key`, a short stable name such as+   `deploy/current`: the next `remember` with the same key replaces the memory+   that holds it, so there is one current answer instead of a pile of old ones.+   `remember` also warns when the project is within 10% of its cap.+ - `memory_update` with `confirm` when you have checked a memory and it is still+   true; with `dispute` when it is probably wrong. A disputed memory is shown with+   a warning sign and ranked lower until it is confirmed, edited or archived.+   `memory_review` is the housekeeping report: likely duplicates, orphans,+   oversized, stale, unread and disputed memories, and how close the project is+   to its cap. Run it now and then, not every session.

https://gagarin.cloud/llms.txt

− # gagarin− > A cloud your coding agent can operate and you can read. gagarin runs your− > containers on managed infrastructure. There are no manifest files and no config− > files: the API is the only way state changes, which is why neither you nor your− > agent can ever be out of sync with what is actually running.− learn, and no endpoint to call by hand:−    the application first; the port is the one it listens on. It builds with−    the local `docker`, so Docker (Docker Desktop, OrbStack, colima) must be−    running. `gg deploy` is the last step on its own, for an image already in−    the registry.− holds values a user typed in rather than ones gagarin minted, so rotating one− steps, of which only the first is gagarin's: the DNS record is theirs to create,− tags, file paths and kinds are not, and gagarin holds the key. Reading needs− - [What gagarin will never build](https://gagarin.cloud/docs/never): the refusal+ # Gagarin+ > Deploy with ease. Maintain without fear. Your agent ships your project in one+ > sentence. Alerts tell you when it breaks, logs say why, project memory keeps+ > the context, and nothing gets deleted without your approval.+ Gagarin runs your containers on managed infrastructure. There are no manifest+ files and no config files: the API is the only way state changes, which is why+ neither you nor your agent can ever be out of sync with what is actually running.+ It is for people building AI agents, bots and MCP servers, and for small teams+ with no platform team of their own.+ learn, and no endpoint to call by hand.+ Check Docker first. `gg ship` builds with the local `docker`, so run+ `docker info` before anything else. If it fails, Docker is not running: ask your+ human to start Docker Desktop, OrbStack or colima, whichever they have, and run+ `docker info` again. Finding this out after login and init costs them a round+ trip.+    the application first; the port is the one it listens on. This is the step+    that needs Docker running. `gg deploy` is the last step on its own, for an+    image already in the registry.+ holds values a user typed in rather than ones Gagarin minted, so rotating one+ steps, of which only the first is Gagarin's: the DNS record is theirs to create,+ ## What comes with it+ Every project gets these without anything to install or configure:+ - **Resources:** `gg resource add <project>/<name> <type>` provisions postgres,+   qdrant, valkey, iggy, s3 or external (credentials a user supplies).+ - **Jobs and schedules:** `gg run` runs an image to completion; with+   `--schedule "0 3 * * *"` it runs on five-field cron instead.+ - **Alerts:** your human turns them on with one switch in the console: the+   project's Alerts tab at `https://my.gagarin.cloud/projects/<id>/alerts`,+   opened on the phone that should buzz (on an iPhone, added to the Home Screen+   first). That allows notifications on the device and opts them in; a terminal+   cannot do the first half; the same page sends a test. There is no gg+   command for alerts. They hear+   when a service goes down, a deploy will not start, or a container keeps+   crashing. No alert rules.+ - **Logs:** `gg logs <project>/<service>`, a week kept, crashed and replaced+   containers included.+ - **Backups:** postgres, qdrant and iggy are backed up nightly and kept 14 days;+   `gg resource restore` brings one back.+ - **Rollback:** `gg history` and `gg rollback` put a previous image and+   environment back.

Showing the first 40 of each.

description

Deploy and operate containers on Gagarin Cloud: services, databases, domains, logs, rollbacks. → Your agent ships the app. Alerts, logs, project memory and approval-gated deletes come with it.

version

0.2.0 → 0.3.0