Get back to your work

Start with the specific notice in Push and the affected work. Keep its reference and explain what you expected before changing accounts, connections or local data.

The agent cannot find the Push skill

Use Settings → Workspace → Push CLI and skill to install or repair it. Invoke /p in agents using slash skills or $p in Codex. A newly installed skill may need a fresh conversation. See the skill walkthrough.

The push command is not found

The same settings panel shows the CLI installation and the exact PATH adjustment for your shell. Apply that instruction in a shell, then try push --help. A shell command pasted into an agent conversation remains a message until the agent runs it.

My agent is not detected or cannot start

Open Settings → Terminal and use Re-probe runtimes after installing a coding CLI. Resolve Sign-in needed, rate limits or usage limits through that runtime's own interface. Read the work's Run explanation for access or capacity requirements.

For a read-only overview in your shell:

push doctor

Follow the diagnostic's named recovery rather than resetting unrelated settings.

A conversation did not return

Check the selected folder, tab filter and work's Open or Reopen control. Use Copy Session Information… from the tab menu for support and preserve the work reference. Avoid unlinking or deleting history to make an error disappear.

Updates

Use Push → Check for Updates… on the Mac. Read any interruption notice before installing or restarting; active work and recordings can be affected. A website message requesting a host update needs an update on that host, not repeated browser sign-ins.

My phone or browser cannot reach the Mac

1. Confirm that the Mac is awake, connected and running Push.
2. Check the workspace/device connection and the exact offline or access message.
3. If it requests an update, update the host. If it says access was removed, ask the owner to review your role.
4. Reconnect through the supported device flow only after checking which connection is affected.

Review Always On for future availability. Before restarting Push, inspect what is running and read its confirmation. Keep unsynced phone captures while fixing connectivity.

Slack cannot act on my message

For “Push can't act on this, because your Slack account isn't connected”, ask the owner to connect or map your identity, then ask again. The earlier message was context and is not automatically executed later.

If the bot is quiet, have the operator check the host, Slack connection and delivery state before repeating a request that might create work. See Slack.

A recording has no transcript

Mac recording transcription requires your OpenRouter key in Settings → Recording → Transcription. Ask the agent to inspect the selected recording and create a missing transcript once the prerequisite is ready. Saved audio and an available transcript are separate results.

For iPhone capture, check its local transcription download or optional provider configuration. See voice capture.

A file or share link is unavailable

Confirm which file or published item you meant. Check file access, workspace access and the publication's expiry or revocation state. A localhost preview needs its Mac-local server running. See results and sharing.

Get help

Use support or the public issue tracker. Include the platform, app version, work reference when appropriate, what you tried and the specific error. Review logs or screenshots for private content before sharing them publicly.

Report security issues through the tracker's private security instructions. Recent changes are in the changelog.