Skip to main content
Not yet released. This guide describes implemented changes awaiting rollout. Availability requires the corresponding backend and dashboard release.

​
Goal

Understand what is happening, who requested it and where to inspect its outcome.

​
Prerequisites

  • Access to the project, Application or database.
  • An environment with the shared activity backend and dashboard release enabled.

​
Workflow

1
Open the resource overview or Application Releases and find its activity section.
2
Review Current operations separately from Earlier history. Load older activity when needed.
3
Select an activity row’s inspect control or a release’s Details action to see attribution, related operations and available destination links.
4
Open the existing build, deployment, release or database reader for detailed progress and logs.

​
Where activity appears

  • Project Overview: Recent Activity includes current work and history alongside existing domain activity. This includes standalone, WordPress and Ghost projects.
  • Build and deployment details: origin and related-operation references sit beside existing progress and log readers.
  • Application Releases: each release keeps its service results and controls together. Service and database activity includes only resources you can access.
  • Standalone and project-linked database overview: Recent activity appears below the existing overview content.
  • Agent objective details: Resources and operations resolves references to the same underlying records. Task links require separate access.

​
Manual and agent work share the same history

Activity covers recorded work started in the dashboard, by Git, through CLI/API requests, or through an agent. You do not have to use an agent to read activity or logs. Authorized reads do not consume AI credits and do not require an AI subscription, even when agent execution is disabled or your balance is exhausted. Deployment and other mutation controls retain their existing permissions and entitlements. Activity access does not grant permission to deploy, cancel, retry or roll back.

​
Read origin and status separately

  • Requester identifies who requested the work; channel identifies how it arrived; executor identifies the recorded controller or agent. Missing historical evidence stays unknown or not recorded.
  • MCP work is identified as an external agent. A client-supplied name does not establish that Codex, Cursor or another named client performed it.
  • A completed build means the build finished. Its deployment can still fail independently.
  • An agent waiting for approval or credits does not change the status of an already-running controller operation.
  • Unknown source states remain unknown. Inspect details to see the recorded source state; do not treat unknown as completed.

​
Refresh, filters and unavailable data

Visible activity summaries refresh every five seconds and when the browser regains focus. Detailed deployment progress continues to use the existing event stream. Filters and sorting apply to loaded activity; use Load older activity to extend the history being inspected. During a temporary connection or source failure, the last successful rows stay visible with stale or unavailable feedback. That is different from an empty history. Retry when offered. Incomplete history does not advance to another page until its source recovers. Access denial removes the inaccessible records.

​
Coverage and rollout limits

History comes from retained build, deployment, release, resource, provisioning, backup/restore/validation, transfer, retirement and pooler records. Older actions without durable records cannot be reconstructed, including historical database start/stop actions where no operation was recorded. The shared activity foundation adds durable history to existing screens. The live workload workspace builds on those same records with a contextual Activity panel and approvals. Neither release adds MCP connection setup, OAuth onboarding or a new CLI release. This documentation update does not itself deploy either feature.

​
Expected result

The same recorded operation has the same identity in resource activity and authorized agent task activity.

Live workload workspace

Follow a deployment, release or database operation alongside its activity and approval decisions.

Builds, deployments, and logs

Understand the project execution lifecycle: build output, deploy state, rollback behavior, and where to inspect logs.

Build a multi-service application

Create an application, add public and private services from one repo or many, and let each service deploy independently while sharing one private network.

Managed database overview

Understand project and standalone databases, stable endpoint identity, supported engines, recovery, and transfer eligibility.

Operation activity API

Read canonical current operations and paginated history without invoking an agent.