Your files and connected services

Implementation overview · 6 September 2026

Local project and app data

Astrology reads and writes the project folder you select. It stores the project list, settings and licence state in its local application-data directory. The licence state includes a device identifier, activation data and the last successful validation time.

Claude Code and Codex

When you send a prompt, Astrology passes it to the selected agent CLI in your project folder. The agent can read project context and contact its provider according to its configuration and permissions. Data retention and training policies depend on the service and account you use; Astrology does not override those policies.

Git, packages and deployments

Git pushes and GitHub actions can upload repository content. Deployments can send source files or build output to your chosen host. Package installs, dependency checks and tool updates contact package registries or other services used by the CLI. A page shown in preview can also load external resources configured by that project.

Licence activation and app updates

Release builds include licence activation and validation. Activation sends the licence key, device identifier, app version and platform to the configured licence service. Validation and deactivation use the activation token and device identifier. When an update channel is configured, the app contacts it to check for available versions and downloads an update when requested.

Diagnostics and logs

The app's diagnostics inspect your project and can run build or dependency checks. Command output is shown in the interface and can include paths, errors and other information printed by the tools.

Scope of this page

This page describes the current app implementation. Service-specific retention details and purchase-related data handling will be provided with the public release. It does not promise that all operations remain offline.