Skip to main content

Client release 0.1.59 (November 16, 2026)

Install the matching CLI and MCP. No command, tool or API changed.
  • Realtime voice accepted. A hosted application opened a session through /realtime, received the model’s audio and transcript events and closed cleanly on Development and Production. The recorded cost was charged at the AI rate. A session ends after five minutes at most; the provider’s keepalive events keep an idle session open until then, so close it from your server. The Skills for building a portable app say so. Realtime voice.

Client release 0.1.48 (November 3, 2026)

  • LLM cost fallback. Chat and Responses use a USD 0.01 cost only when the answered call has no usable recorded trace cost after bounded lookup, or no usable trace id. Actual cost always takes priority, including zero and amounts below USD 0.01. The unchanged rate-card factor applies to the selected cost; operator records mark fallback use, and there is no automatic later correction. Other unmeasured AI routes still settle at zero. AI billing rules.

Client release 0.1.47 (November 3, 2026)

Install the matching CLI and MCP. The ai configuration block requires 0.1.47 or newer:
  • AI gateway. Paid workspaces can use orq models for chat, Responses, image generation and editing, speech-to-text, text-to-speech, classifiers and OCR through injected server credentials. Declare ai.enabled and choose ai.jurisdiction explicitly. The active revision controls the capability and jurisdiction after promotion or rollback. Calls consume prepaid credit under the active ai.cost rate card and contribute to project Stop budgets; without an active card they answer ai_unavailable. Build AI features.
  • Realtime voice. The server-side WebSocket route is available; release 0.1.59 records its hosted acceptance. Realtime voice.

Client release 0.1.46 (November 1, 2026)

Install the matching CLI and MCP. Clients older than 0.1.46 do not have the database table create command or the database_table_create tool:
  • Create a table. ohmyhost database table create, MCP database_table_create (local server only) and POST /v1/projects/{project_id}/database/tables create a table in the public schema of a Dev or Prod database without a source migration. Create a table.

Client release 0.1.45 (November 1, 2026)

Install the matching CLI and MCP. Clients older than 0.1.45 do not have the database watch commands and tools:
  • Table watches. A watch publishes the insert, update and delete changes of one table’s listed columns as signed data.<topic> webhook events. ohmyhost database watch create|list|delete, MCP database_watch_create|list|delete and the REST watch routes manage them. Table watches.
  • Operation lookup. ohmyhost operation get and every CLI --wait, and MCP operation_get, find existing deployment, source and project operations again. Read deployment status.
  • Project renames. A project handle change ends as a succeeded operation. Connect a domain.
  • Deployment faults. A fault that stopped deployments before the build started is fixed. Diagnose a deployment.
  • Database dumps. Customer database dumps leave out the platform event schema. Export your database.
  • Token retries. After a rejection, ohmyhost token create can be run again under the same idempotency key; the stale rejection is replaced. Login and API tokens.

Client release 0.1.44 (October 31, 2026)

  • Executions are counters. Database executions have no separate price; the cost of a run is the time its database is awake. Webhooks, schedules and executions.
  • Schedules stop at the Stop budget. A project that reaches its Stop budget has its schedules turned off. Schedules.
  • Compute lookup. ohmyhost database compute get answers resource_not_found for an environment without a database. Postgres queries, writes and compute.

Client release 0.1.43 (October 31, 2026)

Breaking for clients older than 0.1.43 that read the credit balance. Update CLI and MCP together:
  • Credit balance only. GET /v1/organizations/{organization_id}/credits and ohmyhost credits balance return available_micros, reserved_micros, grace_started_at and grace_expires_at. active_meters and rate_cards are removed; an older CLI rejects the answer with response_contract_invalid. Understand usage.

Client release 0.1.42 (October 31, 2026)

  • Database webhooks, schedules and executions. ohmyhost database webhook, database schedule and database executions (and the matching MCP tools and REST routes) manage signed HTTPS webhooks for database state changes, scheduled SQL and execution counters of a Dev or Prod database. Webhooks, schedules and executions.

Client release 0.1.41 (October 30, 2026)

Breaking for clients older than 0.1.41 that read credits or usage. Update CLI and MCP together before you read either:
  • Usage report. GET /v1/organizations/{organization_id}/credit-usage, ohmyhost credits usage and MCP organization_usage_get return the billed charges of the last up to 14 UTC days grouped by day, project and meter, plus what each project has used so far this UTC month. The month and cursor inputs are removed (CLI --month and --cursor, MCP month and cursor); older days are not kept. Understand usage.
  • Credit account. GET /v1/organizations/{organization_id}/credits and ohmyhost credits balance no longer return spent_micros, expired_micros or platform_overrun_micros. available_micros is the monthly credit plus the one-time credit minus reservations, next to reserved_micros, grace_started_at, grace_expires_at, active_meters and rate_cards. In ohmyhost credits account, paid_until is the end of the paid coverage and includes the fourteen-day renewal grace of a Stripe subscription.
  • Credits do not expire. Top-up, auto-recharge, bonus and referral credits never expire, also after a downgrade to Free; before, top-ups ended with the Paid coverage. Monthly credits (200 on Free, 1,000 on Paid) still end with their period and are spent first. Only effective Paid workspaces can buy top-ups or enable auto-recharge. Credit prices · Billing.
  • Databases run on PGCF. Customer PostgreSQL databases run on PGCF, the open-source PostgreSQL platform behind ohmyho.st; the previous database provider is retired. Every new access credential is a PGCF credential over WSS, and older entries in database access list stay expired or revoked. Postgres queries, writes and compute.

Current clients

Current release identifies the active version and immutable manifest. The manifest lists CLI, MCP, SDK and runtime archives with SHA-256 hashes. Only the current release is served; older release URLs return 404.

Account workflows

Client release 0.1.34 adds the current account email and workspace names beside their IDs to GET /v1/me, CLI whoami and local/remote MCP identity_get. User API tokens report their owner’s email; machine-to-machine credentials report null. Upgrade CLI and MCP together with the current release when checking the signed-in account. Current account details. One computer can keep several saved logins, each bound to one user/organization. Select —profile-name, MCP profile_name or OHMYHOST_PROFILE; the first legacy-profile upgrade needs network access. After another login is saved, ambiguity needs an explicit choice. organization use binds only an unbound login; use login —organization ID for another workspace. Several accounts. The portal provides projects, profile, Billing, Usage and user API Tokens. New keys remain valid until revoked; existing keys keep their recorded expiry. Granted Paid features are separate from Stripe subscriptions and monthly credit grants. Task guides cover GitHub deployments into Dev or direct Prod, promotion/rollback, protected/public Dev links, immutable US/EU region, chosen project addresses, PostgreSQL and time-bound SQL access, private files, schedules, domains/mail, usage/budgets, project context, feedback and encrypted SQL exports. Read each task guide for its current limits and permissions.

Interface changes

The accompanying release adds guarded Dev/Prod data assignment changes without copying records, a fresh file namespace after Dev reset, bulk readMany/deleteMany and explicit browser-origin declarations. Keep CLI/MCP/runtime together and read the linked current-release manifest; older clients can reject changed response shapes. These documentation changes do not establish a live application’s behavior: verify its required flows after deploying. Website changelog · API reference · Report an issue.