share-server-setup

To share HTML artifacts across multiple coding agents, set up a local share server that publishes and serves static files. It handles installation, configuration, and health checks to keep artifacts accessible across different agents.

Yes, you can optionally expose the share server viewer via Tailscale for private artifact viewing. This creates a secure tunnel so only authorized devices on your Tailscale network can access the published HTML reports.

You need bunx, tailscale, and python3 installed to set up the local share server. These tools provide the runtime environment, optional secure network access, and script execution needed for artifact publishing and management.

You can set up an optional macOS LaunchAgent to keep the local share server running continuously. This ensures the server stays active and accessible locally, allowing coding agents to publish and view HTML artifacts without manual restarts.

Yes, the local share server implements health checks to verify the server is running and accessible. This ensures that artifact publishing and viewing endpoints remain operational and available for connected coding agents.

Use a local share server when multiple coding agents need a centralized endpoint to publish and view HTML reports. It is ideal for cross-agent artifact sharing, especially when optional private viewing via Tailscale is needed.