Healthcheck

0) Model self-check (non-blocking)

Before starting, check the current model. If it is below state-of-the-art (e.g., Opus 4.5, GPT 5.2+), recommend switching. Do not block execution.

1) Establish context (read-only)

Try to infer 1–5 from the environment before asking. Prefer simple, non-technical questions if you need confirmation.

Determine (in order):

1. OS and version (Linux/macOS/Windows), container vs host.
2. Privilege level (root/admin vs user).
3. Access path (local console, SSH, RDP, tailnet).
4. Network exposure (public IP, reverse proxy, tunnel).
5. Marti gateway status and bind address.
6. Backup system and status (e.g., Time Machine, system images, snapshots).
7. Deployment context (local mac app, headless gateway host, remote gateway, container/CI).
8. Disk encryption status (FileVault/LUKS/BitLocker).
9. OS automatic security updates status. Note: these are not blocking items, but are highly recommended, especially if Marti can access sensitive data.
10. Usage mode for a personal assistant with full access (local workstation vs headless/remote vs other).

First ask once for permission to run read-only checks. If granted, run them by default and only ask questions for items you cannot infer or verify. Do not ask for information already visible in runtime or command output. Keep the permission ask as a single sentence, and list follow-up info needed as an unordered list (not numbered) unless you are presenting selectable choices.

If you must ask, use non-technical prompts:

• “Are you using a Mac, Windows PC, or Linux?”
• “Are you logged in directly on the machine, or connecting from another computer?”
• “Is this machine reachable from the public internet, or only on your home/network?”
• “Do you have backups enabled (e.g., Time Machine), and are they current?”
• “Is disk encryption turned on (FileVault/BitLocker/LUKS)?”
• “Are automatic security updates enabled?”
• “How do you use this machine?” Examples:
  • Personal machine shared with the assistant
  • Dedicated local machine for the assistant
  • Dedicated remote machine/server accessed remotely (always on)
  • Something else?

Only ask for the risk profile after system context is known.

If the user grants read-only permission, run the OS-appropriate checks by default. If not, offer them (numbered). Examples:

1. OS: uname -a, sw_vers, cat /etc/os-release.
2. Listening ports:
   • Linux: ss -ltnup (or ss -ltnp if -u unsupported).
   • macOS: lsof -nP -iTCP -sTCP:LISTEN.
3. Firewall status:
   • Linux: ufw status, firewall-cmd --state, nft list ruleset (pick what is installed).
   • macOS: /usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate and pfctl -s info.
4. Backups (macOS): tmutil status (if Time Machine is used).

2) Run Marti security audits (read-only)

As part of the default read-only checks, run marti security audit --deep. Only offer alternatives if the user requests them:

1. marti security audit (faster, non-probing)
2. marti security audit --json (structured output)

Offer to apply Marti safe defaults (numbered):

1. marti security audit --fix

Be explicit that --fix only tightens Marti defaults and file permissions. It does not change host firewall, SSH, or OS update policies.

If browser control is enabled, recommend that 2FA be enabled on all important accounts, with hardware keys preferred and SMS not sufficient.

3) Check Marti version/update status (read-only)

As part of the default read-only checks, run marti update status.

Report the current channel and whether an update is available.

4) Determine risk tolerance (after system context)

Ask the user to pick or confirm a risk posture and any required open services/ports (numbered choices below). Do not pigeonhole into fixed profiles; if the user prefers, capture requirements instead of choosing a profile. Offer suggested profiles as optional defaults (numbered). Note that most users pick Home/Workstation Balanced:

1. Home/Workstation Balanced (most common): firewall on with reasonable defaults, remote access restricted to LAN or tailnet.
2. VPS Hardened: deny-by-default inbound firewall, minimal open ports, key-only SSH, no root login, automatic security updates.
3. Developer Convenience: more local services allowed, explicit exposure warnings, still audited.
4. Custom: user-defined constraints (services, exposure, update cadence, access methods).

5) Produce a remediation plan

Provide a plan that includes:

• Target profile
• Current posture summary
• Gaps vs target
• Step-by-step remediation with exact commands
• Access-preservation strategy and rollback
• Risks and potential lockout scenarios
• Least-privilege notes (e.g., avoid admin usage, tighten ownership/permissions where safe)
• Credential hygiene notes (location of Marti creds, prefer disk encryption)

Always show the plan before any changes.

6) Offer execution options

Offer one of these choices (numbered so users can reply with a single digit):

1. Do it for me (guided, step-by-step approvals)
2. Show plan only
3. Fix only critical issues
4. Export commands for later

7) Execute with confirmations

For each step:

• Show the exact command
• Explain impact and rollback
• Confirm access will remain available
• Stop on unexpected output and ask for guidance

8) Verify and report

Re-check:

• Firewall status
• Listening ports
• Remote access still works
• Marti security audit (re-run)

Deliver a final posture report and note any deferred items.

Required confirmations (always)

Require explicit approval for:

• Firewall rule changes
• Opening/closing ports
• SSH/RDP configuration changes
• Installing/removing packages
• Enabling/disabling services
• User/group modifications
• Scheduling tasks or startup persistence
• Update policy changes
• Access to sensitive files or credentials

If unsure, ask.

Periodic checks

After Marti install or first hardening pass, run at least one baseline audit and version check:

• marti security audit
• marti security audit --deep
• marti update status

Ongoing monitoring is recommended. Use the Marti cron tool/CLI to schedule periodic audits (Gateway scheduler). Do not create scheduled tasks without explicit approval. Store outputs in a user-approved location and avoid secrets in logs. When scheduling headless cron runs, include a note in the output that instructs the user to call healthcheck so issues can be fixed.

Required prompt to schedule (always)

After any audit or hardening pass, explicitly offer scheduling and require a direct response. Use a short prompt like (numbered):

1. “Do you want me to schedule periodic audits (e.g., daily/weekly) via marti cron add?”

If the user says yes, ask for:

• cadence (daily/weekly), preferred time window, and output location
• whether to also schedule marti update status

Use a stable cron job name so updates are deterministic. Prefer exact names:

• healthcheck:security-audit
• healthcheck:update-status

Before creating, marti cron list and match on exact name. If found, marti cron edit <id> .... If not found, marti cron add --name <name> ....

Also offer a periodic version check so the user can decide when to update (numbered):

1. marti update status (preferred for source checkouts and channels)
2. npm view marti version (published npm version)

Marti command accuracy

Use only supported commands and flags:

• marti security audit [--deep] [--fix] [--json]
• marti status / marti status --deep
• marti health --json
• marti update status
• marti cron add|list|runs|run

Do not invent CLI flags or imply Marti enforces host firewall/SSH policies.

Logging and audit trail

Record:

• Gateway identity and role
• Plan ID and timestamp
• Approved steps and exact commands
• Exit codes and files modified (best effort)

Redact secrets. Never log tokens or full credential contents.

Memory writes (conditional)

Only write to memory files when the user explicitly opts in and the session is a private/local workspace (per docs/reference/templates/AGENTS.md). Otherwise provide a redacted, paste-ready summary the user can decide to save elsewhere.

Follow the durable-memory prompt format used by Marti compaction:

• Write lasting notes to memory/YYYY-MM-DD.md.

After each audit/hardening run, if opted-in, append a short, dated summary to memory/YYYY-MM-DD.md (what was checked, key findings, actions taken, any scheduled cron jobs, key decisions, and all commands executed). Append-only: never overwrite existing entries. Redact sensitive host details (usernames, hostnames, IPs, serials, service names, tokens). If there are durable preferences or decisions (risk posture, allowed ports, update policy), also update MEMORY.md (long-term memory is optional and only used in private sessions).

If the session cannot write to the workspace, ask for permission or provide exact entries the user can paste into the memory files.