← All use cases

Add Mac telemetry

Use ZeroTwo to add Logger instrumentation to one Mac feature, run the app, and confirm the action in unified logs.

The Build macOS Apps plugin lets ZeroTwo add a few meaningful `Logger` events near windows, sidebars, commands, or sync flows, and then launch the app and confirm in Console, or with `log stream`, that the expected actions ran.

Advanced
30m

Related links

Skills & Plugins

  • Build macOS Apps
    Adds Logger instrumentation, launches the app, and confirms the events in Console or log stream (desktop app; needs a Mac with Xcode).

Add one Logger where debugging gets vague

When a Mac behavior is too fuzzy to diagnose from code, have ZeroTwo add a few unified log events around it, run the app, trigger the flow, and confirm the events in Console or log stream. The Build macOS Apps plugin (desktop app, Mac with Xcode) keeps this light through its telemetry skill: Apple's Logger, a clear subsystem and category, logging at action boundaries, no sensitive payloads, and verification after a real run.

Why telemetry is useful for agentic engineering

Logs provide ZeroTwo with a repeatable feedback loop, so it can exercise a flow and read evidence rather than asking you to click through everything. Three loops benefit:

  • Hands-free debug: instrument, launch, trigger, read the sequence, patch, repeat.
  • Session collection: log launch, window, selection, and import events, then summarize the timeline.
  • Human-driven capture: keep a filtered stream running while you reproduce a bug, then analyze it.

Keep the instrumentation small and filterable

Use one logger per feature area with categories like Sidebar or Sync.

private let logger = Logger(subsystem: Bundle.main.bundleIdentifier ?? "App", category: "Sidebar")
logger.info("Selected sidebar item: \(item.id, privacy: .public)")

Prefer info for lasting lifecycle events and debug for noisy local detail; add signposts only to time a span.

Ask ZeroTwo to prove the event from logs

ZeroTwo should run the flow and report the exact filter plus a representative line.

log stream --style compact --predicate 'subsystem == "com.example.app" && category == "Sidebar"'

If an event is missing, move the log closer to the suspect path and retry. For crashes, switch to the plugin's build-run-debug workflow.

Save a session trace for a later pass

For intermittent bugs, save a focused stream to a small trace file in the workspace and summarize it, so a later run can compare the behavior before and after a patch. The same approach works when you drive the app by hand while ZeroTwo captures.

Practical tips

Instrument one feature at a time

Start with one sidebar, window, or sync path, then widen once it is reliable.

Make privacy part of the prompt

Have each logged identifier explained, and keep secrets and personal data out.

Keep sample output in the final summary

Include the filter and a short timeline so the next run can reuse the check.

Related use cases