Official launch

Alfred IDEis live.

Name: Alfred IDE
Author: GoSiteMe

Alfred IDE is now the official front door for GoSiteMe development: browser-native workspace access, Alfred built directly into the coding flow, sovereign account control, and a real launch path that fits the rest of the ecosystem.

GoCodeMe remains the legacy product name, but Alfred IDE is the official public launch name moving forward.

What is live today

Launch truth, not vapor.

Browser IDE runtime is online

Alfred IDE is already running on the live stack and protected by the GoSiteMe auth flow.

Sovereign sign-in is already wired

PIN and account verification flow through the Alfred IDE gate instead of a generic third-party login wall.

Customer workspaces stay service-aware

Commander launches the server workspace directly. Customer launches stay tied to their own GoCodeMe service and billing state.

Alfred built in

Chat, coding assistance, and account-aware tooling live inside the workspace instead of being bolted on after the fact.

Terminal and Git ready

The live environment is positioned as a real working IDE, not a toy editor or read-only code viewer.

MCP tool reach

GoSiteMe infrastructure already exposes deep tool access through the surrounding Alfred platform and middleware services.

Sovereign account model

Access stays inside the GoSiteMe identity fabric instead of fragmenting the user into separate disconnected IDE identities.

Platform matrix

Web is official now. Desktop is tiered honestly.

Official now

Web / Cloud

Alfred IDE is fully official in the browser today. This is the flagship path: no install, sovereign sign-in, service-aware workspace routing, and the live Alfred IDE stack.

Best path: open Alfred IDE in the browser

Support level: flagship platform

Open web Alfred IDE

Available now

Windows

A real Alfred IDE Windows build exists today as a portable desktop package. It is the next platform to productize fully after the web flagship is locked.

Package: portable x64 ZIP

Current stance: available, still being hardened

Get Alfred IDE for Windows

Browser-first for now

Ubuntu / Linux

Ubuntu and Linux users should use the browser IDE today. Native Alfred IDE packaging is the next Linux track, but it should not be implied as finished before it is real.

Current best path: launch the web IDE

Next native target: Ubuntu/Debian packaging

Use Alfred IDE in browser

Platform clarity matters more than pretending every build is equally mature. Web is the flagship, Windows is real and available, and Ubuntu/Linux stays browser-first until native Alfred IDE packaging is truly ready.

Operational snapshot

What the live Alfred IDE stack says right now

Live runtime reachable

IDE runtime

The Alfred IDE code-server runtime responded on the live stack in about 0 ms.

Public page, protected app

Access gate

This launch page stays public, while `/alfred-ide/` remains protected by the Alfred IDE auth gate and token flow.

Customer routing resolves after sign-in

Workspace routing

After sign-in, Alfred IDE routes customer accounts according to service entitlement instead of dropping everyone into one shared environment.

Alfred panel ships today

In-IDE command surface

The current IDE layer already includes Alfred chat, voice STT/TTS, attachments, account stats, terminal launch, save actions, split editor, command palette access, and code insertion.

Workspace readiness

Can this account open Alfred IDE right now?

Guest view only

Account state

The launch page stays public, but workspace readiness only becomes real after GoSiteMe sign-in.

Service check starts after sign-in

Service entitlement

Customer workspace access is resolved after account sign-in and an active Alfred IDE service lookup.

IDE session begins after sign-in

IDE session

The Alfred IDE workspace token is only issued after the auth gate runs.

Launch will open the auth gate

Launch handoff

One click first resolves Alfred IDE sign-in, then the workspace path.

Launch control activates after login

Guests can read the product story here, but actual workspace routing starts once the GoSiteMe account session is known.

Next move: enter the Alfred IDE auth flow

Open Alfred IDE sign-in

Open live workspace Manage login access Review workspace service

Launch paths

Three clean ways into Alfred IDE

Commander

Server workspace

The Commander account opens the primary Alfred IDE server workspace at the live IDE route.

Launch commander workspace

Sign-in

Access verification

The public sign-in and PIN flow is already wired for Alfred IDE and redirects correctly into the workspace.

Open Alfred IDE sign-in

Customers

Service-linked workspaces

Customer launches stay tied to active GoCodeMe service access instead of dropping everyone into the Commander environment.

Review plans and service access

First-session flow

How a real Alfred IDE session is supposed to unfold

Authenticate through GoSiteMe

Users do not hit a generic editor login wall. They come through the Alfred IDE auth flow, which already supports GoSiteMe sign-in, PIN verification, and token issuance.

Commander uses the protected server workspace path.
Customers stay tied to their own service entitlement.

Land in the correct workspace

Workspace launch is role-aware. Commander stays on the main environment, while customer launches are meant to resolve into their own service-linked workspace instead of one shared server shell.

No fake “one size fits all” workspace story.
Customer access is governed by active GoCodeMe service status.

Use Alfred inside the IDE

The current Alfred Commander layer already gives the user a meaningful operating surface inside the editor instead of just a renamed stock code-server shell.

Chat, model selection, voice STT/TTS, and hands-free mode.
Attachments for images, PDFs, text, code files, and ZIP bundles.

Build, save, run, and ship

Quick IDE actions already surface terminal, save, save all, command palette, split editor, and new file flows. The next maturity step is making workspace health, preview, and runtime workflows just as visible.

Terminal and code insertion are already wired.
Onboarding and lifecycle visibility are the next product gaps to close.

Why it matters

The official product story is finally coherent

Real browser IDE

Alfred IDE launches as a full browser workspace, not a brochure that hands the user off to a vague developer promise.

Alfred in the workflow

The product name now matches the actual experience: Alfred is not adjacent to the IDE, Alfred is part of it.

Sovereign access

Sessions, account checks, and workspace launches are handled inside GoSiteMe instead of outsourcing trust to unrelated platforms.

Tool gravity

The IDE sits inside the broader Alfred platform, which is where the MCP tools, automation, hosting, and launch leverage already live.

Build and ship

Terminal, Git, browser access, and ecosystem routing make Alfred IDE part of the actual build path, not a detached experiment.

Unified platform surface

Search, browser, hosting, billing, and IDE can now be presented as one ecosystem instead of separate isolated stories.

GoCodeMe becomes Alfred IDE

GoCodeMe still exists as the legacy product label and customer service context, but the public launch name shifts to Alfred IDE so the product aligns with the ecosystem brand and the live runtime.

View legacy GoCodeMe page

Open the IDE that belongs to the platform.

Today's launch does not need fantasy. It needs a public entry point, honest access rules, and one clear message: Alfred IDE is live, it is part of GoSiteMe, and it is ready to open in the browser now.