Files
feuerwerk/tools/mcp/relay.d.mts
T
adminandClaude Opus 5.5 48ec722660
feuerwerk / gate (push) Successful in 5m41s
feuerwerk / suite (push) Successful in 18m44s
Let an AI agent see the open editor through MCP (#429)
Claude Code should be able to work inside the user's open editor tab.
This first stage connects the two and lets the agent look: what the
user sees and a picture of it. Changing the project comes in stage 2.

- An agent token per account opens only /mcp, no API route. The
  dialog "Agent tokens..." in the account menu creates it once, shows
  the ready "claude mcp add" line and revokes it. The server keeps
  only its sha256 (api/lib/AgentTokens.php).
- Wrong tokens count into the sign-in brake from #427. Changing the
  password, renaming or deleting an account ends its tokens.
- The relay (tools/mcp/) is a small Node service without packages,
  WebSocket server included. It runs in the container feuerwerk-mcp
  because PHP-FPM cannot hold connections. Whether a token or a tab
  ticket is valid is still decided by the PHP API, through two routes
  that answer only with the relay key.
- The tab joins over WebSocket on the same origin with the normal
  session, an Origin check and a one-time ticket. It connects only
  after "Agent" is switched on in the account menu. One tab per
  account is active, a new one takes over. Guests get nothing.
- Tools: get_view (project, tab, document, selection with names,
  camera, play state, open dialog) and screenshot. The resource
  feuerwerk://view can be subscribed. Claude Code does not act on
  that reliably, so a changed view is also noted on the next answer.
- A badge next to the account menu shows the connected agents. It
  counts only agents with an open stream or a request in the last
  two minutes.
- CI starts the relay in front of php -S (tools/ci/serve.sh), and
  e2e 71 runs the whole path in the browser.

Found on the live test: the badge showed four agents because old
sessions of revoked tokens were still counted.

Tests:
- Gate on atx: 316 files, 4888 tests
- relay protocol test with fake API and fake tabs: 23/23
- get_view, tools, socketUrl: 16/16
- PHP agents 29, rights 103 checks
- e2e 71 on atx 10/10, against the live site 10/10, no CSP violation
- real Claude Code against the live site: get_view answered
- ZAP against /mcp: nothing at High or Medium
- every new check fails when the guard it covers is taken out (6)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 10:39:34 +02:00

43 lines
1.0 KiB
TypeScript

export interface ApiAnswer {
status: number;
user?: string;
role?: string;
error?: string;
retryAfter?: string | null;
}
export interface RelayApi {
verifyToken(token: string, address: string): Promise<ApiAnswer>;
redeemTicket(ticket: string): Promise<ApiAnswer>;
}
export interface RelayOptions {
port?: number;
host?: string;
api: RelayApi;
tools: () => Promise<object[]>;
origins: string[];
trustProxy?: boolean;
backend?: string;
log?: (line: string) => void;
callTimeoutMs?: number;
helloTimeoutMs?: number;
pingMs?: number;
maxMessageBytes?: number;
maxBodyBytes?: number;
sessionIdleMs?: number;
agentRecentMs?: number;
maxSessionsPerAccount?: number;
}
export interface Relay {
port: number;
stats(): { tabs: string[]; sessions: string[] };
close(): Promise<void>;
}
export const PROTOCOL_VERSIONS: string[];
export const VIEW_URI: string;
export const CLOSE: { replaced: number; badHello: number; refused: number; helloTimeout: number };
export function startRelay(options: RelayOptions): Promise<Relay>;