steam-pipe-gui-macos-unity

by tomicz · indexed from github

SteamPipeGUI for macOS: build and upload Unity games to Steam from the Unity Editor on Mac, with no steamcmd commands or VDF scripts to write. The macOS answer to Valve's Windows-only SteamPipeGUI: one-click Build and Upload, Steamworks SDK integration, multi-depot support, and a headless batch mode for CI and AI agents.

Build and upload your Unity game to Steam from the Unity Editor on macOS, with no steamcmd commands or VDF scripts to write. It is the macOS answer to Valve's Windows-only SteamPipeGUI: fill in a deployment target once, then click Build and Upload.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tomicz-steam-pipe-gui-macos-unity — read its card at https://meshkore.com/agent/tomicz-steam-pipe-gui-macos-unity/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tomicz-steam-pipe-gui-macos-unity
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tomicz-steam-pipe-gui-macos-unity/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

code

Do you own steam-pipe-gui-macos-unity?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.