auspex: IT Admin User Guide for Jamf Pro (macOS)

Last updated: November 16, 2026

This guide is for IT administrators deploying the Span agent (auspex) to macOS devices via Jamf Pro.


What This Package Does

auspex captures AI coding activity (prompts, file edits, tool use) from supported IDEs (Cursor, Claude Code, Codex, and more) and sends telemetry to Span's analytics backend. This data appears in your Span dashboard under AI Effectiveness.

The macOS installer is a single universal .pkg. When it installs elevated (as Jamf does), it places the auspex binary at /usr/local/bin/auspex and, from v0.13.0, /usr/local/bin/auspex-capture, the small program every coding-tool hook runs, drops a root-owned managed configuration at /Library/Application Support/auspex/ (the managed.yaml marker = managed mode), and converges automatically (its postinstall runs auspex install --system, wiring machine-wide hooks and provisioning each engineer's identity, then starts the per-user agent at login).

You don't need a separate "install hooks" policy — the package converges itself. Your job is to (a) pre-authorize file access so users are never prompted, and (b) deliver each device's identity (token + work email) before the package installs.


Prerequisites

  1. A Span account with access to the integrations settings page.

  2. A Jamf Pro tenant managing the target macOS devices (macOS 13+, supervised), with each device's Email Address populated under User and Location in its inventory record (typically synced from your directory provider — LDAP, Cloud IdP, Jamf Connect, or SSO). Without it, the config script cannot determine the per-device work email.

  3. The macOS package URL, reachable by Jamf (or upload it as a package): https://auspex.span.app/releases/latest/darwin/auspex_darwin_universal.pkg — click here to download


Deployment order (important)

  1. Configuration profiles (file access + background items) — first.

  2. Email variable profile + identity script + package, bundled in one policy (script priority Before), so identity lands before the package converges.


Step 1: Enable the Integration and Get Your Token (one-time)

This step is the same regardless of your MDM.

Head to the AI tool settings dashboard (https://span.app/_/settings/integrations) and under IDE & CLI AI Tool Integrations, enable the tools your engineers use. Here is what each tool supports:

Tool

What's captured

Claude Code

OTEL metrics + hooks

Cursor

Hooks

Codex CLI

OTEL metrics + hooks

Copilot CLI

Hooks

VSCode chat

Hooks

Note: Some integrations don't yet have a dashboard toggle. If your engineers use one, enable Claude Code or Codex CLI to generate the token — it's shared across all tools. The token is org-wide.

The token itself is on the Traces settings page: open the Trace collection card and click View token. It's shown there regardless of which tools are toggled on above, and it's the same span_… org-wide value every device uses. That page is limited to Span admins and users whose permission group can manage integrations — if it doesn't load for you, ask one of them to fetch the token.


Step 2: Deploy the File-Access + Background-Items Profile (before the package)

auspex reads the edited file from the project's git working tree the moment an AI edit fires. If a user keeps repos under a TCC-protected folder (Documents, Desktop, Downloads), that read would prompt:

"auspex" would like to access files in your Documents folder.

Deploy the combined profile below before the package so no one is prompted. It grants Full Disk Access (PPPC), pre-approves auspex's background items, and silences the background-activity notification.

Upload route (any Jamf version):

  1. Computers → Configuration Profiles → Upload.

  2. Select auspex-background-items.mobileconfig.

  3. Set Scope to the target group → Save.

The profile ships with Span's Developer ID team (KNH44SBYN4) and the binary paths (/usr/local/bin/auspex and /usr/local/bin/auspex-capture) already filled in. To confirm the code requirement against a deployed Mac:

codesign -dr - /usr/local/bin/auspex
codesign -dr - /usr/local/bin/auspex-capture

Upgrading to v0.13.0 or later? Since v0.13.0, auspex ships a second, capture-only program called auspex-capture, installed at /usr/local/bin/auspex-capture. It's a leaner copy of the main auspex program that your coding tools' hooks run to capture events. It reads the edited files, so it needs the same file access as auspex.

The auspex-background-items.mobileconfig profile now has entries for both programs. If you deployed an earlier copy, update it once when you upgrade to v0.13.0. It's a one-time update: download the profile again from that link, replace the old one, and deploy it before the new package.

If you use your own profile instead, add an auspex-capture entry next to each auspex entry. Upgrading auspex shows the entry to add; Full Disk Access isn't required. Until a device has the updated profile, macOS may prompt for or block reads of edited files under Documents, Desktop or Downloads.

Tamper-proofing (recommended): deliver PayloadRemovalDisallowed on the managed profile so an enrolled user can't remove it. The package already ACL-protects /Library/Application Support/auspex on disk.

Requires a supervised device from a trusted MDM (macOS 13+).


Step 3: Deploy the Email Variable Profile (one-time)

Jamf policy scripts run locally on the device (as root) and can't read the server-side User and Location inventory directly. Deploy a Configuration Profile that uses Jamf's $EMAIL payload variable — Jamf substitutes the assigned user's email server-side and writes it to a managed plist on disk.

Save the following as span-email.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>EMAIL</key>
    <string>$EMAIL</string>
</dict>
</plist>
  1. In Jamf Pro: Computers → Configuration Profiles → New.

  2. General payload → Name: auspex Email Variable.

  3. Application & Custom Settings → Configure → External Applications → Add:

    • Source: Upload File

    • Preference Domain: app.span.auspex

    • Upload PLIST File: span-email.plist.

  4. Scope → the same group used in Step 2 → Save.

Jamf writes the resulting plist to /Library/Managed Preferences/app.span.auspex.plist. Verify on a test device:

/usr/libexec/PlistBuddy -c 'print :EMAIL' '/Library/Managed Preferences/app.span.auspex.plist'

If empty, populate the Email Address under Computers → select device → Inventory → User and Location.


Step 4: Add the Identity Script

In Jamf Pro: Settings → Computer Management → Scripts → New.

  1. General tab → Display Name: auspex Identity.

  2. Script tab → paste below, replacing <YOUR_TOKEN> with the token from Step 1.

  3. Save.

#!/bin/bash
set -e

# REPLACE with your org token from Step 1
SPAN_AUTH_TOKEN="<YOUR_TOKEN>"

if [ "$SPAN_AUTH_TOKEN" = "<YOUR_TOKEN>" ] || [ -z "$SPAN_AUTH_TOKEN" ]; then
  echo "ERROR: SPAN_AUTH_TOKEN placeholder was not replaced in the script body."
  exit 1
fi

PLIST="/Library/Managed Preferences/app.span.auspex.plist"
if [ ! -f "$PLIST" ]; then
  echo "ERROR: Email variable profile not found at $PLIST. Complete Step 3 and let it install, then re-run."
  exit 1
fi

WORK_EMAIL=$(/usr/libexec/PlistBuddy -c 'print :EMAIL' "$PLIST" 2>/dev/null || true)
if [ -z "$WORK_EMAIL" ] || [[ "$WORK_EMAIL" != *"@"* ]]; then
  echo "ERROR: EMAIL in $PLIST is empty or invalid (got: '$WORK_EMAIL'). Populate User and Location > Email Address."
  exit 1
fi

json_escape() { printf '%s' "$1" | sed 's/\\/\\\\/g; s/"/\\"/g'; }
TOKEN_JSON=$(json_escape "$SPAN_AUTH_TOKEN")
EMAIL_JSON=$(json_escape "$WORK_EMAIL")

mkdir -p '/Library/Application Support/auspex'
printf '{\n  "token": "%s",\n  "work_email": "%s"\n}\n' "$TOKEN_JSON" "$EMAIL_JSON" \
  > '/Library/Application Support/auspex/identity.json'
chown root:wheel '/Library/Application Support/auspex/identity.json'
chmod 644 '/Library/Application Support/auspex/identity.json'

echo "Success: identity.json written for $WORK_EMAIL"

The identity.json (token + work_email, root:wheel, 0644) is a delivery file the package's converge reads at install time, migrating it into each user's own private (0600) identity and then removing it.


Step 5: Upload the Package

In Jamf Pro: Settings → Computer Management → Packages → New → Display Name auspex → upload the universal .pkg (or configure your distribution point to fetch the URL above). Save.


Step 6: Create the Deployment Policy

This policy runs the identity script before the package, so identity.json exists when the package converges.

In Jamf Pro: Computers → Policies → New.

  1. General → Display Name auspex Install; Trigger Recurring Check-in; Execution Frequency Once per computer.

  2. Scripts → Configure → add auspex Identity with Priority = Before.

  3. Packages → Configure → add auspex (action Install).

  4. Scope → the same group as Steps 2–3.

  5. Save.

The package's postinstall converges the device to managed mode and starts the daemon.


Step 7: Smoke Test (before fleet rollout)

Validate on 1–2 pilot devices first.

  1. Create a auspex Pilot Smart/Static group with your device and a teammate's.

  2. Temporarily scope the Step 2/3 profiles and the Step 6 policy to auspex Pilot.

  3. On each pilot device: sudo jamf policy.

  4. Confirm the email variable and identity delivery:

    /usr/libexec/PlistBuddy -c 'print :EMAIL' '/Library/Managed Preferences/app.span.auspex.plist'
    
  5. Confirm the package installed and the device is managed:

    pkgutil --pkg-info app.span.auspex
    auspex status        # stderr: install mode: managed
    auspex auth show     # work email + MASKED token
    
  6. In System Settings → Privacy & Security → Full Disk Access, auspex and auspex-capture should show enabled and "managed by your organization."

  7. Have the pilot user run Claude Code / Cursor and confirm traces in the dashboard.

  8. Re-scope everything to production.


Verifying the Deployment

Computers → device → History → Policy Logs — the auspex Install policy should show Completed, with the identity script ending Success: identity.json written for <email>. On the device:

auspex status
auspex auth show

Optional: Replace legacy Span coding-hooks in the same rollout

If you're migrating from the older coding-hooks agent, you can retire it on each device as part of this rollout. This step is optional and best-effort: it removes coding-hooks only after auspex is confirmed installed and converged — the per-user agent is running and an identity (work email + org token) is provisioned for every engineer on the device — and only if the coding-hooks uninstaller is present. It's safe to assign fleet-wide, including to devices that never had coding-hooks (there it simply no-ops).

Why bundle it: until coding-hooks is removed, a device running both agents will capture and send each event twice (duplicate traces). Gating removal on a confirmed and converged auspex install lets you cut over cleanly, one device at a time — with no window where both agents are running, and none where coding-hooks is gone but auspex hasn't finished provisioning (an unprovisioned device would otherwise lose coverage silently).

In Jamf Pro: create it under Settings → Computer Management → Scripts (Display Name auspex Migrate coding-hooks), then put it in a separate policy from the package — triggered on Recurring Check-in with Execution Frequency Ongoing. Don't attach it to the package policy with Priority = After — it would no-op on every device.

Run it on a repeating cadence, not once immediately after the package. Gate 3 reads per-user state — it needs the engineer to have logged in at least once and their agent running, with an identity provisioned either device-wide (the managed identity.json) or per-user by the converge. Seconds after the package lands that is usually not yet true, so an install-time run will no-op and print what it's waiting for. Let it repeat and it removes coding-hooks on the first run after the device has converged.

#!/bin/bash
# OPTIONAL post-install: retire legacy Span coding-hooks AFTER a confirmed, running, provisioned auspex install.
# Runs entirely as root: no login session, no launchctl, no per-user daemon. Always exits 0.
set -uo pipefail

CH_UNINSTALL="/Library/Application Support/app.span.coding-hooks/uninstall.sh"
MANAGED_ID="/Library/Application Support/auspex/identity.json"
HEARTBEAT_MAX_AGE=300   # seconds; a healthy agent beats every 15s

# Gate 1 — auspex package receipt present (install confirmed by macOS).
if ! /usr/sbin/pkgutil --pkg-info app.span.auspex >/dev/null 2>&1; then
  echo "auspex receipt not found — install not confirmed; leaving coding-hooks in place."
  exit 0
fi

# Gate 2 — auspex binary AND managed marker both in place.
if [ ! -x "/usr/local/bin/auspex" ] || [ ! -f "/Library/Application Support/auspex/managed.yaml" ]; then
  echo "auspex not fully in place (binary or managed marker missing) — leaving coding-hooks in place."
  exit 0
fi

# Gate 3 — EVERY user with an auspex runspace must have a live agent and a provisioned identity.
# A runspace is counted by its heartbeat (the daemon writes it whether or not the per-user converge
# provisioned an identity). Identity follows the daemon's own resolution order (managed > user): the
# root-owned managed identity, when present, serves every user on the device; otherwise the user's
# 0600 runspace identity (root reads it directly). A shared Mac must not lose coding-hooks while any
# engineer on it is still unprovisioned.
found=0
for hb in /Users/*/.auspex/run/heartbeat; do
  [ -f "$hb" ] || continue
  found=$((found + 1))
  user=$(echo "$hb" | cut -d/ -f3)

  # 3a — the per-user agent is alive.
  age=$(( $(date +%s) - $(/usr/bin/stat -f%m "$hb") ))
  if [ "$age" -gt "$HEARTBEAT_MAX_AGE" ]; then
    echo "$user: heartbeat stale (${age}s) — agent not running; leaving coding-hooks in place."
    exit 0
  fi

  # 3b — resolve the identity the daemon actually uses.
  if [ -f "$MANAGED_ID" ]; then
    idf="$MANAGED_ID"
  else
    idf="/Users/$user/.auspex/run/identity.json"
  fi
  if [ ! -f "$idf" ]; then
    echo "$user: no identity (managed or user tier) — not provisioned; leaving coding-hooks in place."
    exit 0
  fi

  # 3c — a work email is provisioned.
  if ! grep -q '"work_email"[[:space:]]*:[[:space:]]*"[^"]*@[^"]*"' "$idf"; then
    echo "$user: no work email in $idf — not provisioned; leaving coding-hooks in place."
    exit 0
  fi

  # 3d — an org token is provisioned. Presence only: this script makes NO network call, so it
  # cannot tell you the control plane ACCEPTS the token.
  if ! grep -q '"token"[[:space:]]*:[[:space:]]*"[^"]\{8,\}"' "$idf"; then
    echo "$user: no org token in $idf — not provisioned; leaving coding-hooks in place."
    exit 0
  fi

  echo "$user: agent live, identity provisioned ($idf)."
done

if [ "$found" -eq 0 ]; then
  echo "no running auspex user runspace found — agent has not started for any user; leaving coding-hooks in place."
  exit 0
fi

# All gates passed — best-effort remove coding-hooks.
if [ -f "$CH_UNINSTALL" ]; then
  echo "auspex confirmed for all $found user(s) — removing legacy coding-hooks…"
  bash "$CH_UNINSTALL" || echo "coding-hooks uninstall returned non-zero (best-effort) — continuing."
  echo "Done: coding-hooks removal attempted."
else
  echo "No coding-hooks uninstaller found — nothing to remove."
fi
exit 0

Notes:

  • The script exits 0 on every path, so a coding-hooks removal failure never fails the policy or disturbs auspex.

  • It removes coding-hooks only when every gate passes and the uninstaller exists at /Library/Application Support/app.span.coding-hooks/uninstall.sh. On any other device it reports which gate it stopped at and exits cleanly.

  • It runs entirely as root and makes no network call. Root reads each 0600 per-user identity directly, so there is no launchctl asuser hop, no sudo -u, and no dependency on an active login session or a reachable control socket — the parts that behave differently from one MDM to the next.

  • What it does not prove: that the control plane accepts the token. The gates confirm auspex converged, is running, and has an identity — not that its traces are being accepted. A device whose org token is rejected keeps beating: the agent's liveness heartbeat is deliberately refreshed throughout a route-terminal auth hold, so an auth failure still looks alive locally. Confirm the pilot devices are actually landing traces in the dashboard before you assign this fleet-wide.

  • On a shared Mac every user with an auspex runspace must pass; the script leaves coding-hooks in place if any engineer on the device is still unprovisioned.

  • User-defined hooks in Cursor and Claude Code are preserved by the coding-hooks uninstaller.


Troubleshooting

Policy log shows ERROR: SPAN_AUTH_TOKEN placeholder was not replaced

Open Scripts → auspex Identity, replace <YOUR_TOKEN> with the real token, Save. Then Computers → device → History → Policy Logs, Flush auspex Install, and run sudo jamf policy.

EMAIL is empty or invalid

Populate User and Location → Email Address, Update Inventory, then Flush the policy and re-run sudo jamf policy.

Device is managed but capture isn't authenticated

The package converged before identity.json existed. Confirm the identity script ran (auspex auth show), then re-run sudo auspex install --system (the daemon hot-reloads identity). Ensure the script's Priority is Before in the policy.

User was prompted for Documents access

The file-access profile (Step 2) wasn't in place before the package. Deploy it, then on the device: sudo tccutil reset SystemPolicyAllFiles and re-check.


Upgrading

Upload the new package to the existing auspex package item, then Flush All on the auspex Install policy so Jamf re-delivers at next check-in. managed.yaml and edited fleet policy are preserved; the identity script only needs redeploying if the token changes.

Upgrading to v0.13.0 or later? As a one-time update, deploy the updated auspex-background-items.mobileconfig profile (or your own profile with an auspex-capture entry) first. The note in Step 2 explains why. Going back to a release before v0.13.0? First run sudo /usr/local/bin/auspex hooks uninstall --system on v0.13.0 or later, then deploy the older package. Releases before v0.13.0 don't recognize the newer hook entries, so without this step every event is captured twice.


Uninstalling

A macOS .pkg has no built-in uninstaller, so removal is a script. auspex hooks uninstall --system un-wires the managed (machine-wide) capture hooks, but it doesn't remove the binary, launchd units, or root-owned managed config the package placed. So a clean managed removal runs that command, removes those machine-wide files and each user's auspex data, then removes the MDM-delivered profiles.

Step 1 — Uninstall auspex

Run it elevated on the device, or deliver it through Jamf Pro (as a one-off policy, Scripts payload). It un-wires the hooks first (while the binary still exists), then removes the daemon units, the managed config, the binaries, the package receipt, and each user's auspex data. It exits non-zero and names anything it couldn't remove:

#!/bin/bash
# Removes a managed (.pkg) auspex install and every user's auspex data. Run as root, from an MDM script or
# `sudo`. The MDM guides on help.span.app copy this file verbatim, and the Release E2E workflow runs it.
set -uo pipefail
BIN="/usr/local/bin/auspex"   # full path: root/MDM shells often omit /usr/local/bin from PATH
CAPTURE="/usr/local/bin/auspex-capture" # the capture binary every hook runs, or its placeholder link

[ "$(id -u)" -eq 0 ] || { echo "uninstall-managed.sh: run as root (sudo)" >&2; exit 1; }

# 1. Un-wire the MANAGED (machine-wide) capture hooks — the tier the MDM package wired.
"$BIN" hooks uninstall --system || true

# 2. Stop and remove the launchd units. Boot out the converge LaunchDaemon (system domain) AND
#    each user's daemon agent by label, which also stops a leftover self-install agent of the same label.
launchctl bootout system "/Library/LaunchDaemons/app.span.auspex.converge.plist" 2>/dev/null || true
for u in /Users/*; do uid=$(id -u "$(basename "$u")" 2>/dev/null) || continue
  launchctl bootout "gui/$uid/app.span.auspex" 2>/dev/null || true
done
rm -f "/Library/LaunchDaemons/app.span.auspex.converge.plist" "/Library/LaunchAgents/app.span.auspex.plist"

# 3. Remove the root-owned managed config tree. Its tamper-proof ACL denies deletion even to root, so
#    clear it first.
chmod -R -N "/Library/Application Support/auspex" 2>/dev/null || true
rm -rf "/Library/Application Support/auspex"

# 4. Remove the binaries and forget the package receipt.
rm -f "$BIN" "$CAPTURE"
pkgutil --forget app.span.auspex 2>/dev/null || true

# 5. Delete each user's auspex data: undelivered events, the local copy, logs and device id. A linked
#    .auspex is unlinked, not followed. Also remove what a self-install from before enrollment left.
for u in /Users/*; do
  rm -rf "$u/.auspex"
  rm -f "$u/Library/LaunchAgents/app.span.auspex.plist"
  if [ -L "$u/.local/bin/auspex" ]; then rm -f "$u/.local/bin/auspex"; fi
done

# Report failure, so an MDM shows it, if anything survived (for example an ACL that blocked a delete).
left=()
for path in "$BIN" "$CAPTURE" "/Library/Application Support/auspex" "/Library/LaunchAgents/app.span.auspex.plist" \
  "/Library/LaunchDaemons/app.span.auspex.converge.plist" /Users/*/.auspex; do
  if [ -e "$path" ] || [ -L "$path" ]; then left+=("$path"); fi
done
if [ "${#left[@]}" -gt 0 ]; then
  echo "uninstall-managed.sh: could not remove: ${left[*]}" >&2
  exit 1
fi
echo "auspex uninstalled"

On a self-installed (non-managed) Mac, use auspex uninstall instead — see the self-install guide.

Step 2 — Remove the MDM-delivered profiles and assignment

In Jamf, unscope the auspex package/policy (Steps 5–6) and the configuration profiles (Step 2), and remove any PayloadRemovalDisallowed lock first. Do this so the MDM does not re-deliver auspex on the next check-in.

Verify the removal is complete

Run on the device — every line should print ok: (no receipt, binary, config, daemon, or per-user data left):

pkgutil --pkg-info app.span.auspex >/dev/null 2>&1 && echo "STILL PRESENT: package receipt" || echo "ok: no package receipt"
command -v auspex >/dev/null 2>&1 && echo "STILL PRESENT: auspex on PATH ($(command -v auspex))" || echo "ok: auspex not on PATH"
[ -e /usr/local/bin/auspex ] && echo "STILL PRESENT: /usr/local/bin/auspex" || echo "ok: binary gone"
{ [ -e /usr/local/bin/auspex-capture ] || [ -L /usr/local/bin/auspex-capture ]; } && echo "STILL PRESENT: /usr/local/bin/auspex-capture" || echo "ok: capture binary gone"
[ -e "/Library/Application Support/auspex" ] && echo "STILL PRESENT: managed config tree" || echo "ok: managed config gone"
launchctl print system/app.span.auspex.converge >/dev/null 2>&1 && echo "STILL LOADED: converge daemon" || echo "ok: converge daemon not loaded"
CU=$(stat -f%u /dev/console 2>/dev/null || echo 0); launchctl print "gui/$CU/app.span.auspex" >/dev/null 2>&1 && echo "STILL LOADED: per-user daemon (gui/$CU)" || echo "ok: per-user daemon not loaded"
ls /Library/LaunchDaemons/app.span.auspex.converge.plist /Library/LaunchAgents/app.span.auspex.plist >/dev/null 2>&1 && echo "STILL PRESENT: launchd units" || echo "ok: launchd units gone"
ls -d /Users/*/.auspex >/dev/null 2>&1 && echo "STILL PRESENT: per-user auspex data ($(ls -d /Users/*/.auspex | tr '\n' ' '))" || echo "ok: no per-user auspex data"

Fallback — only if the checks above still show remnants

A leftover usually means an MDM profile re-pushed the managed config before Step 2 completed, or a delete was blocked. Confirm Step 2 removed the MDM assignment, so nothing re-delivers, then run the Step 1 script again. It clears the managed config's tamper-proof ACL itself, and names anything it still can't remove.

User-defined hooks in Cursor and Claude Code are preserved throughout.


Support

For issues not covered here, contact the Span team with:

auspex status
auspex support        # redacted support bundle