Activity | Ghostable Desktop | Ghostable                              Menu

 Activity

   Signed project history
----------------------

 Activity displays repository-backed events recorded by the Ghostable engine. Each row can identify the action, environment or key context, actor device, time, and signature result without showing secret plaintext.

 Because the log travels through Git, pull the latest branch before investigating an event. A local checkout only contains history present in its current repository state.

![Ghostable Desktop signed project activity history](https://ghostable.dev/images/generated/screenshots/ghostable-desktop-v3/project-activity-light.png)![Ghostable Desktop signed project activity history](https://ghostable.dev/images/generated/screenshots/ghostable-desktop-v3/project-activity-dark.png)Activity records repository-backed actions with actor, signature, and time context.

 Activity modes
--------------

   `off`  Do not record normal project activity events.

  `minimal`  Record a reduced set of important operations.

  `full`  Record the broadest supported activity detail for review and audit workflows.

 Configure the mode and audited environments in Project Settings. Production and staging commonly deserve fuller coverage than disposable local environments, but the correct policy depends on repository size, review needs, and retention requirements.

 Search and filters
------------------

 Search narrows events by displayed action and context. Filters can isolate action families or signature status, while pagination loads older repository events. Closing a filter does not clear or modify history.

 Use a specific key, environment, device name, or action when reconstructing a change. Pair the result with the Git commit that introduced the corresponding `.ghostable/` update.

 Signature status
----------------

 A valid signature shows that the event matches a trusted project device record and was not altered after signing. An invalid or unknown signature deserves investigation before relying on the event.

  Signatures are not user surveillance

 Device signatures establish repository-level authenticity. They do not prove who was physically using a machine, that the machine was uncompromised, or that an external provider applied a requested change.

 Purge activity
--------------

 The Activity toolbar can purge recorded events according to the current project controls. Purging changes repository state and reduces future visibility, so use it only under an explicit retention policy and review the resulting Git diff.

 Git history may still contain earlier activity files. Purge is project-state maintenance, not retroactive erasure from every clone or commit.

    On this page

    [ ![Ghostable](https://ghostable.dev/images/logo-dark.svg) ![Ghostable](https://ghostable.dev/images/logo-light.svg) ](https://ghostable.dev)

   Desktop     [   CLI 3.x ](https://ghostable.dev/docs/3.x) [   Desktop ](https://ghostable.dev/docs/desktop)

  CLI 3.x introduction Documentation local first no login encrypted repository plaintext hosted service

  Installation Documentation brew homebrew npm npx linux windows PATH version update

  Start a new project Getting Started setup seed dotenv owner initialize

  Adopt an existing project Getting Started existing env import authoritative source adopt

  Onboard a team member Getting Started join request approve roles offboarding pull request

  Repository and storage Core Concepts .ghostable git conflict merge worktree private identity metadata

  Environments Core Concepts protected production preview staging push sync pull replace run mask-output

  Variables and promotions Core Concepts var promote copy context annotation key

  Access and devices Core Concepts identity reader writer grantor owner revoke rotate leave delete

  Daily development workflow Workflows pull diff validate review clean daily

  Review and secret scanning Workflows scan sarif github suppress secrets drift

  Hygiene and rotation Workflows rotation stale unused suppression environment key

  Automation credentials Automation & CI GHOSTABLE\_CI\_TOKEN ci deploy credential powershell revoke replace

  Continuous integration Automation & CI GitHub Actions fork pull request JSON stdout stderr exit codes mask-output

  Deployments Automation & CI Forge Vapor Cloud provider CLI dry-run preserve remote keys temporary files

  Validation Reference schema required nullable regex min max different\_from

  Command reference Reference --help --json NO\_COLOR flags aliases exit code automation

  Configuration Reference ghostable.yaml activity mode auditEnvironments scan ignores deployTarget dotenv syntax

  Security Reference cryptography XChaCha20 Poly1305 HKDF user presence threat model

  Backups & Offline Reference recovery offline restore clone key identity

  Agent integration Reference AGENTS.md capabilities allowlist coding agent

  Troubleshooting Reference no project found revoked identity stale policy user presence invalid CI token provider CLI git conflict diagnostics

  Ghostable Desktop overview Desktop

  Installation Desktop

  Projects and setup Desktop

  Interface tour Desktop

  Environments and variables Desktop

  Local environment files Desktop

  Validation and review Desktop

  Activity Desktop

  Access and automation Desktop

  Project settings Desktop

  Application settings Desktop

  Licensing and updates Desktop

  Security and storage Desktop

  Troubleshooting Desktop    No results found