Skip to content

Latest commit

 

History

History
33 lines (23 loc) · 2.18 KB

File metadata and controls

33 lines (23 loc) · 2.18 KB

Messages

Read-only research into supported and private local Messages surfaces on macOS. The current baseline maps the public integration boundary, Messages.app, chat.db structure without row data, IM private frameworks, agents, notifications, hooks, and XPC ownership.

Status

Baseline established on macOS 26.5.2 (25F84) against the macOS 27.0 SDK. Generated interfaces, comparison against another OS build, and controlled event-delivery proof remain open.

Start Here

  1. Read the supported and private boundary before choosing an integration or experiment.
  2. Use the comprehensive baseline for the environment, evidence checklist, initial findings, and open questions.
  3. Follow the topic index below for focused conclusions.
  4. Consult the raw-evidence index only when reproducing or auditing a capture.

No command in this index sends a message or reads message rows. Some documented experiments inspect private frameworks, app metadata, daemon configuration, or database schema and can require Full Disk Access, Automation permission, or OS-specific private-framework availability.

Topic Index

  • Surfaces: supported extension and compose APIs, URL schemes, manifests, and the public/private boundary.
  • Storage: chat.db schema, relationships, lifecycle metadata, and privacy limits.
  • Types: supported and private type families.
  • Symbols: SDK and live symbol evidence.
  • Agents: apps, agents, daemons, plugins, and service ownership.
  • Runtime: Objective-C metadata and dyld-cache observations.
  • Hooks: automation, listener, query, callback, and interception surfaces.
  • Notifications: candidate names, delivery mechanisms, and observer evidence.
  • XPC ownership: launchd services, entitlements, clients, and authority boundaries.
  • Experiments: completed, blocked, and proposed research steps.

Cross-Target Context

Messages and Phone share several communication-service boundaries. Use the combined status map when a finding crosses both targets.