Use the Push skill

The Push skill teaches your coding agent how to use Push for the work you ask it to do. You can stay in the conversation while your agent tracks work, finds results, checks progress, and prepares a handoff.

Before you start

Open a supported coding agent inside a Push terminal. Settings → Workspace → Push CLI and skill provides setup and repair for the bundled CLI and skill. If push is missing from your shell, use the PATH instructions shown there.

Invoke the skill as /p in agents that use slash skills, or $p in Codex. You can also explicitly ask the agent to use the Push skill in ordinary language. Skill invocation belongs in the agent conversation; push commands belong in a shell or are run by the agent.

Ask for an outcome

For a useful read without changing work, ask:

Use the Push skill to tell me what is running, what needs my attention, and where I can open each item.

Be specific about changes you want. For example, in a fresh untracked conversation:

Use the Push skill to track this conversation as "Prepare the launch".

Or, when work produces a file:

Show me the final report in Push and keep it with this work. Prepare it for sharing, but let me review what would become public first.

These are examples for different situations, not a sequence to run on every conversation.

Use the CLI directly

The same status lookup has a shell alternative:

push status

You do not need to interrupt an agent conversation to use this alternative. Ask the agent to run the lookup, or use another Push shell tab. The CLI guide explains direct commands and scripting.

See the result

Ask the agent to name the Push Session, file or UI location it used. Tracking appears on the board; a surfaced file appears with the work's Artifacts; progress and questions appear on the work's thread or terminal.

The skill can explain a missing permission and guide you to the setting. You make OS grants, change Data Access, approve tool prompts, and decide when to take terminal control yourself. A request for permission means that part is still waiting.

If something stops

If the agent does not recognize /p or $p, check the CLI and skill setup panel, then start a fresh agent conversation after installation. Do not paste credentials into the conversation to repair setup. For a refused operation, follow the reason and next step the command reports.

Continue with tracking, checking progress, or your results.