Overview
Surface Editor is a Code-OSS based Grid-native IDE. The extension SDK lets you build VS Code-compatible extensions that run in Surface Editor. Extensions are distributed via the self-hosted Open VSX registry — no Microsoft Marketplace dependency.
EDITOR.P0 (Grid Editor Profile: theme, key bindings, ArcRouter model endpoint) can start immediately. See the Surface Editor Matrix.
Extension API
The Surface Editor extension API is the VS Code Extension API. Existing VS Code extensions are compatible. Grid-specific additions layer on top.
// package.json
{
"name": "arcgrid-surface-extension",
"engines": { "vscode": "^1.85.0" },
"contributes": {
"commands": [{
"command": "arcgrid.openSurface",
"title": "Open in Surface"
}]
}
}
// extension.ts
import * as vscode from 'vscode'
export function activate(ctx: vscode.ExtensionContext) {
ctx.subscriptions.push(
vscode.commands.registerCommand('arcgrid.openSurface', () => {
// extension logic
})
)
}Model API (ArcRouter)
Surface Editor exposes an ArcRouter-backed model endpoint. Extensions call it for inline completions, chat, and analysis — no Copilot, no OpenAI, no Anthropic direct calls.
// Use the Grid model endpoint from an extension
const response = await fetch('http://archelm:8080/v1/chat/completions', {
method: 'POST',
headers: { 'Authorization': `Bearer ${gridApiKey}` },
body: JSON.stringify({
model: 'AR-D1', // Noema base
messages: [{ role: 'user', content: prompt }]
})
})Publish to Open VSX
Extensions are published to the self-hosted Open VSX registry on ArcHelm. The registry requires ARCHUB.2 before extensions can be namespaced and versioned properly.
# Set the registry endpoint
export OVSX_REGISTRY_URL=http://archelm:8080/ovsx
# Publish an extension
npx ovsx publish --pat $OVSX_PATBuild status
EDITOR.P0 (Grid Editor Profile) is ready to start. EDITOR.P1+ depends on ArcAware M3. EDITOR.P3 (Open VSX registry) depends on ARCHUB.2.