Move work from your chosen coding tool into a team workspace
Surface connects supported coding-host work to a team workspace for governed usage, review and release. The visual is an illustrative product view, not customer deployment proof.
From a coding task to a controlled team release
Choose the coding tool
Start in a supported host and keep provider access and prerequisites visible.
Work in the team workspace
Bring the app or workflow into a shared place for governed usage and review.
Prepare access and controls
The team owns identity, access and security readiness for its environment.
Release with accountable owners
Make integration, testing and release ownership explicit before the workflow is relied on.
Choose a host with its status visible
Codex — supported
Install Codex desktop or CLI and arrange provider account access. Preview desktop with eai start . --surface codex-desktop --dry-run or terminal with eai start . --surface codex-cli --dry-run. Desktop opens the project when the Codex CLI is available; otherwise choose the project folder in the app. Ask it to use the repository EAI skill. The terminal path supplies the starting prompt. Official start source reviewed 6 September 2026.
Open official Codex guideClaude — supported
Install Claude desktop or Claude Code CLI and arrange provider account access. Preview with eai start . --surface claude-desktop --dry-run or eai start . --surface claude-cli --dry-run. Desktop opens a Code session when supported; otherwise choose the project folder, start a Code session and ask it to use the repository EAI skill. The terminal path supplies the starting prompt. Official start source reviewed 6 September 2026.
Open official Claude guideGitHub Copilot — supported
Install the Copilot app or CLI and sign in with the required Copilot access. Preview with eai start . --surface copilot-desktop --dry-run or eai start . --surface copilot-cli --dry-run. In the desktop app, choose the project folder and ask it to use the repository EAI skill. The terminal path supplies the starting prompt. For the editor route, use the separate VS Code choice. Official start source reviewed 6 September 2026.
Open official GitHub Copilot guideAntigravity — unverified
Provider access may be required. There is no implemented eai start option for Antigravity, and an EnterpriseAI integration has not been verified. Review its provider guide; choose a supported host for the EnterpriseAI exercise. Official start source reviewed 6 September 2026.
Open official Antigravity guideGrok — supported
Install the Grok CLI and arrange provider account access. Preview with eai start . --surface grok-cli --dry-run. The launch opens a terminal session for the project and supplies the starting EAI prompt. Official start source reviewed 6 September 2026.
Open official Grok guideVS Code — supported
Install VS Code with Copilot built in or installed, then sign in with the required Copilot access. Preview with eai start . --surface vscode-copilot --dry-run. The launch opens the project and starts an EAI Copilot chat. VS Code alone does not establish Copilot readiness; other editor AI tools are not covered by this launch option. Official start source reviewed 6 September 2026.
Open official VS Code guidePrepare your first Surface session
Use an existing project with the repository EAI skill and the EnterpriseAI CLI installed. In a terminal at the project folder, run eai start --check to see detected hosts and readiness. This checks local setup; it does not verify provider sign-in, subscription eligibility or an EnterpriseAI connection.
Choose one of the commands on your host card. Keep --dry-run to inspect the launch plan without opening the provider. If the host is missing, follow its official guide, complete provider sign-in and run the check again. When you are ready for that provider to access the sample project using your account, remove --dry-run and run the same command. Follow the desktop handoff on the card if the project or starting prompt is not passed automatically.
Start with fictitious data and ask: Use the repository EAI skill. Help me define one small workflow, its expected result and who approves it. Use the vendor exercise on Get started as the test brief. Check a complete case, a missing input and a failure; record corrections and have the named reviewer approve the result before any team release. Record separate provider charges and the workspace owner before paid use.
What the states mean
Supported means the current EnterpriseAI host inventory includes that option; it does not include the provider account or universal compatibility. Antigravity is unverified and has no implemented CLI launch path. The six host choices include eight implemented desktop, terminal and editor launch options; they are not eight separate products.
Provider guidance proves provider setup only, not EnterpriseAI integration or account eligibility.
A practical first result is a small internal workflow that the team can integrate, test, review and release under named ownership. Optional help can be scoped where the team needs it.