Docs

Aetower documentation

Rendered from the repository's docs/ directory on every deploy — the repo is the source of truth. Engineering documents may lag the app between releases.

Using Aetower

• Getting Started with Aetower Developer Preview — This guide is for technical users installing a direct-download Developer
• Aetower Product Direction — PRD-style direction, priorities, invariants, and source map for Aetower.
• Aetower Feature List — Current shipped product surfaces, technical capabilities, and maturity notes.
• Aetower Tab-by-Tab Guide — Current app workspaces, nested sections, and when to use each page.
• Download Aetower Developer Preview — Aetower is distributed as a direct-download Developer Preview for macOS.
• Known Limitations — Aetower is currently a Developer Preview for technical users. Share builds

Automation & agents

• Aetower local MCP server — Aetower includes a local MCP server for agents that need direct access to
• MCP tool reference — Aetower's local MCP server exposes 46 tools — 45 read-only tools plus one guarded operator action. Operator actions are visible to trusted local clients…

Distribution & release

• Aetower distribution — scripts/package-macos.sh produces a local app bundle. When
• Direct Download Release — Aetower's current public release channel is Developer Preview. Public
• Homebrew Release — Aetower's Homebrew distribution is a cask that installs the same signed and
• Developer Preview Release Checklist — Use this checklist before sharing a public Developer Preview build.
• Cloudflare Release Hosting — aetower.dev is served by two independent Cloudflare deploy units so a
• Public Preview Validation — Use this runbook before sharing a Developer Preview build outside the

Engineering internals

• Aetower module breakdown — This document defines a concrete initial repository layout and module ownership plan for Aetower.
• Observability — type: reference
• Aetower Diagnostics And Debug Console Spec — Current state: partial diagnostics, no real debug console.
• Aetower runtime profiling — The benchmark harness protects the collection pipeline. This workflow measures the real packaged app while it is running.
• Aetower performance harness — Use the local harness to measure the core sampling pipeline cost on the current machine.
• Local Ci — type: how-to
• Aetower Design System — Status: scaffolded
• Brand Assets — Aetower uses one canonical app-icon source image and derives macOS package
• Bincode v1 → v2 Migration Plan — Open. Tracked via the RUSTSEC-2025-0141 ignore in deny.toml.

Also on this site

• aetower CLI reference — commands, options, install paths, and driving the UI from scripts
• Privacy — what Aetower observes and what stays local
• Security — reporting and hardening posture