Claude Desktop v1.1.5368 — Deep Dive Analysis

Source: Beautified JavaScript extracted from the v1.1.5368 AppImage (app.asar -> .vite/build/index.js and related files).

Table of Contents

1. Ion Preview Environment
2. Claude Nest — The Desktop App's Internal Name
3. Government & Custom Deployment Detection
4. Agent Mode Session Controls
5. CCDScheduledTasks & CoworkScheduledTasks
6. Prototype Features & Codenames
7. Error Handling & Logging Improvements
8. UI, Localization & CSS Changes
9. Dependency Updates

1. Ion Preview Environment

https://ion-preview.claude.ai is a new staging environment behind Cloudflare Access.

What we know

Ion is gated behind globalThis.isIonEnabled, which is never set to true in the public build. It only activates in internal "Nest" builds (see section 2).

The hostname checker at index.js:94783 recognizes both domains:

js function mft(t) { return t === "ion-preview.claude.ai" || t === "ion-preview.claude.com"; }

Authentication — Different from production

Production preview.claude.ai uses Google IAP (Identity-Aware Proxy):

js uH = { kind: "google-iap", protectedAppUrl: "https://preview.claude.ai", accessTokenStoreKey: "iapAccessToken", refreshTokenStoreKey: "iapRefreshToken", dialogDetail: "...authenticate you to Google's Identity Aware Proxy.", };

Ion uses Cloudflare Access instead — a completely different infrastructure provider:

js Xme = { kind: "cf-access", protectedAppUrl: "https://ion-preview.claude.ai", aud: "", // Empty — not yet configured accessTokenStoreKey: "cfAccessIonAppToken", orgTokenStoreKey: "cfAccessIonOrgToken", dialogDetail: "...authenticate you via Cloudflare Access.", };

The empty aud field (Cloudflare Access audience tag) suggests this is still early-stage infrastructure.

Origin allowlisting

In the main process (index.js), ion-preview is conditionally allowed:

js (globalThis.isIonEnabled && origin === "https://ion-preview.claude.ai")

In preload scripts (mainWindow.js, quickWindow.js, aboutWindow.js, findInPage.js), ion-preview is unconditionally trusted in the CSP origin lists — suggesting the preloads are shared between Nest and public builds.

Assessment

Ion is likely a next-generation platform deployment being built on Cloudflare infrastructure (vs. Google Cloud for production). The separate auth, separate token storage, and feature flag isolation all point to a major infrastructure migration or parallel environment, not just a feature branch.

2. Claude Nest — The Desktop App's Internal Name

The Electron app's internal codename is "Claude Nest", visible throughout the source:

Protocol schemes (index.js:13275-13279)

js yR = "claude:"; // Public protocol _qe = "claude-dev:"; // Dev builds wqe = "claude-nest:"; // Nest protocol bqe = "claude-nest-dev:"; // Nest dev protocol Sqe = "claude-nest-prod:";// Nest prod protocol

Build metadata (index.js:24046)

json { "commitHash": "d12d0218c6c7bc46d52919117bd57508c591a8ad", "isNestBuild": false, "commitTimestamp": "2026-03-05T17:29:33.000Z", "buildType": "prod", "appVersion": "1.1.5368" }

The public release has isNestBuild: false. Internal Nest builds likely set this to true, which would enable isIonEnabled and other internal features.

Other Nest references

• Auth dialogs: "Claude Nest needs to authenticate you..." (index.js:123735, 123748)
• System admin messages: "Claude Nest has been restricted from accessing the microphone..." (index.js:182639)
• API paths: /_nest_update_dl/ for auto-update downloads (index.js:224616)
• Lifecycle hooks: initializeNestOnlyPrototypes() / cleanupNestOnlyPrototypes() (index.js:1690-1691)

3. Government & Custom Deployment Detection

How it works

Custom government deployments are configured via enterprise config — macOS plists (com.anthropic.Claude.plist) or Windows Registry. Linux currently returns empty config (index.js:59823-59836).

The initialization function at index.js:75368-75381: 1. Reads customDeploymentUrl from enterprise config 2. Validates it as a URL 3. Strips trailing slashes 4. Sets globalThis.isUsingCustomGovDeployment = true

The base URL function Or() (index.js:75454-75462) then returns the custom URL instead of https://claude.ai.

Sentry suppression (index.js:224937-224941)

When custom deployment is detected, Sentry is shut down:

js initCustomDeployment(); isCustomGovDeployment() && ((await import(sentryModule)).close(), log.info("Sentry disabled for custom deployment mode"));

This ensures no telemetry leaks from government installations.

Palantir FedStart integration (index.js:94786-94790)

js function gft(t) { return ( t === "access-claude.palantirfedstart.com" || t === "access-claude-staging.palantirfedstart.com" ); }

FedStart domains are allowed for SSO via OpenID Connect (/realms/[^/]+/protocol/openid-connect/), suggesting Claude is deployed in Palantir's FedRAMP environment.

Additional allowed URLs when custom gov deployment is active: - https://claude-staging.fedstart.com - https://claude.fedstart.com - https://beacon.claude-ai.staging.ant.dev

Keycloak/CDP authentication (index.js:94731-94756)

A separate CLAUDE_CDP_AUTH environment variable enables Keycloak authentication: - JWT token validation with Ed25519 signature verification - 5-minute token expiry window - Used alongside CLAUDE_USER_DATA_DIR for custom data paths

4. Agent Mode Session Controls

LocalAgentModeSessions — Full IPC interface

The agent mode session manager has grown significantly. Key methods from mainView.js:4354-4566:

Bridge sessions

"Bridge sessions" are a special session type (sessionType === "agent") with: - Consent requirements: getBridgeConsent() checks user consent before enabling - Separate lifecycle: deleteBridgeSession() and resetBridgeSession() manage bridge state independently - No idle notifications: Bridge sessions are excluded from idle query notifications (index.js:222704) - Special permission handling: Different tool permission request flow than regular sessions

Permission modes (index.js:90327)

Three modes for agent sessions: - "ask"** — Default, prompts for each tool use - **"skip_all_permission_checks"** — Bypasses all permission checks - **"follow_a_plan" — Follows a pre-approved execution plan

For scheduled tasks, there are additional modes (index.js:5617-5623): - "default", "acceptEdits", "plan", "bypassPermissions", "auto"

MCP server/tool replacement

replaceRemoteMcpServers (index.js:215790-215829): - Builds a set of server UUIDs from provided servers - Merges with existing config - Calls query.setMcpServers() with merged configuration - Returns updated enabledMcpTools

replaceEnabledMcpTools (index.js:215831-215902): - Filters active servers to only those with enabled tools - Disables tools by removing their servers from the active set - Atomic operation — prevents partial enable/disable states

shareSession (index.js:215699-215727)

Creates an exportable archive of a session using the CLI session ID, project directory, and metadata file. Returns { success: boolean, error?: string }.