Visible control surface
Agent channels, device state, waitlist flow, pricing surface, and onboarding commands are present today.
MUSU early access๋ โAI๊ฐ ๋๋ํ๋คโ๋ ์๊ธฐ๊ฐ ์๋๋ผ, ์ด๋ฏธ ๊ฐ์ง ๊ธฐ๊ธฐ์ AI ์์ ์ ํ ํ๋ฉด์์ ์ด์ํ๊ฒ ํด์ฃผ๋ ์ ํ์ ๋จผ์ ๋ค์ด์ค๋ ๊ฒ์ด๋ค.
์ง๊ธ ๋จ๊ณ์ ์ฌ๋ฐ๋ฅธ CTA๋ broad checkout์ด ์๋๋ผ proof-backed early access๋ค.
MUSU์ ํ์ฌ ๊ฐ์ ์ โ๋ฌด์์ด ์ค์๊ฐ์ผ๋ก ์ด์๋๊ณ ์๋์งโ์ ๊ฐ๊น๋ค. ๊ทธ๋์ early access ํ์ด์ง๋ ์ถ์์ ์นดํผ๋ณด๋ค ๊ธฐ๊ธฐ, ์ํ, ์ค์น, ์ ๊ทผ ํ๋ฆ์ ๋จผ์ ์ค๋ช ํด์ผ ํ๋ค.
Agent channels, device state, waitlist flow, pricing surface, and onboarding commands are present today.
A browser terminal backed by remote PTY is a strong future wedge, but it should stay roadmap-framed until implementation and security policy exist.
Early access is the right path for users who want to shape how MUSU handles machine coordination, control surfaces, and future remote access.
Current install framing should stay simple: install the port, connect the machine, and surface it inside MUSU.
Installer delivery is handled during onboarding while the public bootstrap endpoint is still being hardened.
Linux install instructions are issued after access approval so the public site does not point to a bootstrap URL that is not live yet.
macOS follows the same beta flow: confirm access, receive the install package, then connect the machine.