582 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
chioarubandGitHub	677d29ffd4	feat(lsp): add first-class code intelligence setup (#950) ... * feat(lsp): add plugin candidate discovery * feat(lsp): add first-class setup command * fix(lsp): add bounded filesystem extension fallback * fix(lsp): repair official marketplace recommendations	2026-05-02 08:35:38 +08:00
KRATOSandGitHub	4fab8b913f	fix(errors): show actual host in 404 message instead of Ollama hint (#926) (#931) ... When an OpenAI-compatible provider returns a 404, the user-facing error message hardcoded "for Ollama: http://127.0.0.1:11434/v1" as a hint regardless of the configured base URL. Users on remote providers (NVIDIA NIM, OpenRouter, etc.) read this as the app ignoring their custom OPENAI_BASE_URL and routing to localhost. Plumb the request URL through the classifier and marker so the user-facing message can name the actual host. Localhost endpoints keep the existing Ollama-flavored guidance for backward compatibility. - classifyOpenAIHttpFailure now accepts an optional url and produces a host-aware hint for non-localhost 404s - the [openai_category=...] marker carries an optional host segment - mapOpenAICompatibilityFailureToAssistantMessage branches on host to show "Endpoint at <host> returned 404. Verify OPENAI_BASE_URL is correct and the selected model (<model>) is supported by this provider." for remote URLs - backward compatibility preserved when no URL is available	2026-05-02 08:34:32 +08:00
3 people	a46b31c3ec	feat: SDK Core — Permission System, Async Context, and Engine Extensions (#951) ... * feat(sdk): add SDK foundation — type declarations, errors, and utilities Adds standalone SDK building blocks with no SDK source dependencies: - sdk.d.ts: ambient type declarations for SDK bundle - coreSchemas.ts + coreTypes.generated.ts: Zod schemas and generated types - errors.ts: SDK-specific error classes - validation.ts: input validation utilities - messageFilters.ts: extracted message filter logic - handlePromptSubmit.ts: imports from messageFilters - 16 generated-types tests * fix(sdk): narrow assertFunction type from broad Function to callable signature Code review finding: assertFunction used `asserts value is Function` which accepts any function-like value without narrowing. Changed to `(...args: any[]) => any` for better type safety. * fix(sdk): update sdk.d.ts header — manually maintained, not generated Reviewer noted the header said "Generated from index.ts" but no generator produces this file. Updated to "Manually maintained — keep in sync with index.ts". Drift detection added in validate-externals.ts (PR 3). * fix(sdk): align sdk.d.ts types with canonical coreTypes.generated.ts Tighten SDK public type contract to resolve reviewer blockers: - PermissionResult: unknown[] → precise 6-shape discriminated union (addRules/replaceRules/removeRules/setMode/addDirectories/removeDirectories) - SDKSessionInfo: snake_case → camelCase (sessionId, lastModified, etc.) - ForkSessionResult: session_id → sessionId - SDKPermissionRequestMessage: uuid + session_id now required - SDKPermissionTimeoutMessage: added uuid + session_id - SessionMessage: parent_uuid → parentUuid - SDKMessage/SDKUserMessage/SDKResultMessage: replaced loose inline definitions with re-exports from coreTypes.generated.ts * feat(sdk): wire existing code modules + SDK shared utilities Modifies core modules for SDK integration: - QueryEngine, tools, state, commands: SDK type hooks - SDK shared utilities (shared.ts, permissions.ts) - 21 SDK tests (shared-utils, permissions) Stack: main ← pr1-foundation ← pr2-sdk-core * feat(sdk): add snake_case ↔ camelCase key mapping utilities casing.ts provides recursive key transformation for the SDK boundary layer. Internal runtime uses snake_case; public API exposes camelCase. Will be used by shared.ts, sessions.ts, query.ts at export boundaries. * test(sdk): add tests for snake_case ↔ camelCase mapping utilities Covers snakeToCamel, camelToSnake, mapKeysToCamel, mapKeysToSnake including nested objects, arrays, null/undefined, and round-trips. * fix(sdk): prevent permission timeout race condition with once-only resolve wrapper Add createOnceOnlyResolve utility to prevent double-resolution of promises when timeout and host response happen simultaneously. This ensures deterministic behavior in the permission handling flow. * fix(sdk): improve race condition test robustness * fix(sdk): handle consecutive underscores in snakeToCamel conversion Changes: - Use _+([a-z]) regex to match multiple consecutive underscores before letters - Add lookahead (?=. ) to preserve underscore-letter pairs at string end - Handle dunder names (__proto__, __typename) by stripping wrapper and capitalizing - Add tests for consecutive underscores and trailing underscore preservation * fix(sdk): include original error message in permission callback denial When a canUseTool callback throws an error, the catch block now includes the original error message in the denial message, making debugging easier for SDK consumers. * feat(sdk): add optional timeout to env mutex for deadlock prevention Add timeout parameter to acquireEnvMutex() to prevent infinite waits in deadlock scenarios. The timeout is optional and defaults to no timeout (wait forever) for backward compatibility. Returns a MutexAcquireResult object with acquired status and optional timeout reason for failed acquisitions. * fix(sdk): remove timed-out callback from mutex queue to prevent deadlock * test(sdk): add missing error path and timeout scenario tests Add tests for timeout scenarios when host doesn't respond to permission requests, fallback behavior when no onPermissionRequest callback, and MCP connection edge cases for undefined/empty config. * fix(sdk): address code review issues - race conditions, validation, error handling - Add createPermissionTarget() factory that applies onceOnlyResolve at registration time, fixing race condition where timeout and host response could both try to resolve the same promise - Add try-catch to releaseEnvMutex() to prevent permanent lock if callback throws - Extract DEFAULT_PERMISSION_TIMEOUT_MS constant (30 seconds) - Add MCP config validation rejecting null, non-objects, and arrays - Preserve error stack traces in MCP connection failures - Add runtime validation to mapMessageToSDK for null/non-object/invalid type - Update tests to use createPermissionTarget and add validation tests * test(sdk): add sequential timeout-then-host-response race condition tests Adds two tests addressing reviewer request for proof that host response after SDK timeout is safely handled with no double-resolve or leaked listener: 1. Integration test: stale host resolve called after timeout deny — verifies no error, no mutation, map cleanup 2. Unit test: raw resolve called exactly once when timeout wins — directly proves createOnceOnlyResolve prevents second execution * fix: restore openclaude.json comment in REPL.tsx Reviewer caught that the comment was incorrectly changed to ~/.claude.json during merge — project has already migrated to ~/.openclaude.json. * fix(sdk): register pending permission before emitting onPermissionRequest The previous code emitted onPermissionRequest before calling registerPendingPermission, so a host responding synchronously from the callback would find an empty map and its response was lost. Swap the order so registration happens first. Adds a regression test for the synchronous host response path. * fix(sdk): make state setters context-aware for SDK isolation When running inside runWithSdkContext(), setter functions (regenerateSessionId, switchSession, setCwdState, setOriginalCwd) now write to the AsyncLocalStorage context instead of global STATE. This prevents cross-session state leakage in multi-session SDK scenarios. Reads were already context-aware; this completes the isolation by making writes consistent. Outside of SDK context, behavior is unchanged — all writes go to global STATE as before. * test(sdk): add context-aware state isolation tests Tests verify that setters within runWithSdkContext() write to the SDK context (not global STATE) and that parallel async contexts do not leak state between sessions. Covers setCwdState, setOriginalCwd, regenerateSessionId, switchSession, and an end-to-end parallel session scenario. * fix(sdk): selective tool schema cache invalidation for multi-engine isolation Replace global clearToolSchemaCache() in QueryEngine.updateTools() with selective invalidation that only removes cache entries for tools no longer in the tool set. This preserves cached schemas for tools that remain, avoiding unnecessary recomputation for concurrent QueryEngine instances in multi-session SDK scenarios. New function invalidateRemovedToolSchemas() handles both simple tool name keys and schema-variant keys (format: "toolName:{...schemaJSON...}"). * docs(sdk): address PR2 non-blocking documentation and logging issues - Document request_id vs tool_use_id relationship in shared.ts (request_id for response correlation, tool_use_id for tracking) - Add injectable SDKLogger interface to permissions.ts, replacing direct console.warn calls with logger.warn (hosts can control noise) - Document Node.js-only AsyncLocalStorage requirement in state.ts (requires Node.js 12.17.0+ or 14.0.0+) - Clarify env-mutex is host utility (SDK doesn't mutate process.env) * fix(sdk): handle throwing onPermissionRequest and fix permission request shape - Wrap onPermissionRequest in try-catch to clean up pending resolver on throw - Add uuid and session_id to permission_request message to match SDK schema - Add regression tests for throwing callback and message shape validation * fix(sdk): use explicit no-session placeholder for standalone permission prompts - Add NO_SESSION_PLACEHOLDER constant ('no-session') for permission requests - Update SDKPermissionRequestMessage doc to explain session_id semantics - Replace empty string fallback with explicit placeholder - Add test verifying placeholder behavior when sessionId omitted * docs(sdk): add example code to permission denial warning Include canUseTool example in warning message to improve developer experience and make SDK usage more discoverable for new users. * fix(sdk): scope parentSessionId to SDK context for parallel isolation regenerateSessionId({ setCurrentAsParent: true }) was writing to the process-global STATE.parentSessionId even inside runWithSdkContext(), allowing one SDK context to overwrite another's parent-session metadata. Add parentSessionId to the SdkContext type and update both regenerateSessionId and getParentSessionId to read/write from the active context when one exists, using an explicit if-else pattern rather than ?? to avoid undefined fallback leaking across contexts. The non-SDK CLI path (no active context) continues to use STATE directly, preserving existing behavior. --------- Co-authored-by: Ali Alakbarli <ali.alakbarli@users.noreply.github.com>	2026-05-02 08:32:50 +08:00
3 people	b471745fb1	Registry-Based Integration Architecture for Providers, Gateways, and Models (#910) ... * setting up * updated plan with missing notes for discovery cache * build out inital checklist and planning adjustments * Phase 1A-1D * Fix descriptor-backed provider profile routing - preserve GitHub, Bedrock, and Vertex runtime flags during profile activation\n- serialize descriptor-backed startup profiles into legacy-compatible persisted kinds\n- add regression coverage for activation, restart round-trip, and saved-profile switching\n- guard integration registration so repeated imports stay idempotent in tests * feat: finish phase 1 provider descriptor routing Complete the Phase 1E CLI/usage migration work and the Phase 1F verification pass for descriptor-backed providers. Details: - derive valid --provider values from descriptor registry and compatibility mappings instead of a fixed list - preserve special CLI semantics for ollama and minimax while allowing descriptor-backed OpenAI-compatible routes such as deepseek and openrouter to pick up descriptor base URLs - add getUsageDescriptor() so /usage resolves vendor/gateway metadata and follows usage delegation - switch Settings Usage rendering to descriptor-backed usage resolution for Anthropic, MiniMax, and neutral unsupported fallbacks - make integration loading idempotent via ensureIntegrationsLoaded() so registry-backed helpers survive tests that clear the registry - fix compatibility mapping for mistral so the preset routes through vendorId=openai with gatewayId=mistral rather than a nonexistent direct vendor route - harden provider profile and startup tests so descriptor-backed providers, legacy OpenAI startup files, and unknown stored providers round-trip correctly - remove a stale ollama model mock that was leaking across the full model test suite - update plan/progress.md with the current 1E complete / 1F in-progress verification state and the note that repo-wide typecheck failures are pre-existing outside this migration slice Verification: - bun test src/commands/usage/index.test.ts src/integrations/compatibility.test.ts src/utils/providerFlag.test.ts src/utils/providerProfiles.test.ts src/utils/providerProfile.test.ts src/utils/model/modelCache.test.ts src/integrations/index.test.ts src/integrations/registry.test.ts - filtered bun run typecheck output for the files changed in this branch is clean * Phase 2 planning * feat: complete phase 2A validation and discovery cache * fix: address review findings for phase 2 cache and validation Fixes the follow-up review issues from the Phase 2A / 2A.5 work. Completed work: - made discovery cache stale entries reachable through getCachedModels(..., { includeStale: true }) while keeping fresh-by-default behavior unchanged - kept recordDiscoveryError stale-data preservation useful to later /model consumers by exposing stale and error-only entries through the public helper API - extended descriptor-backed validation routing metadata with host alias matching support - updated MiniMax validation routing to recognize both api.minimax.io and api.minimax.chat endpoints - added regression coverage for stale cache reads, error-only cache entries, and MiniMax chat-host validation - updated progress.md notes so the recorded 2A.5 helper behavior matches the implementation * feat: complete phase 2B discovery and readiness migration Implement descriptor-backed discovery and readiness routing for Phase 2B. Highlights: - add src/integrations/discoveryService.ts to execute declarative catalog.discovery configs with shared discovery-cache integration - add hybrid merge behavior so curated descriptor catalog entries stay ahead of discovered duplicates - add typed startup readiness metadata via ReadinessProbeKind and wire gateway descriptors for ollama, atomic-chat, lmstudio, and openrouter - export probeOllamaModelCatalog() so discovery can distinguish unreachable Ollama from reachable-but-empty catalogs - migrate ProviderManager and /provider flows to probeRouteReadiness() while preserving existing Ollama messaging - route bootstrap local model discovery through descriptor-backed discovery for recognized local routes, while keeping legacy fallback for generic custom endpoints - add resolveDiscoveryRouteIdFromBaseUrl() so bootstrap can share descriptor-backed discovery and local provider labels - preserve explicit provider env precedence during applySavedProfileToCurrentSession() after focused verification exposed the regression - update plan/progress.md to mark Phase 2B complete and record the verification notes Verification: - bun test src/integrations/discoveryService.test.ts - bun test src/components/ProviderManager.test.tsx - bun test src/commands/provider/provider.test.tsx - bun test src/utils/providerDiscovery.test.ts src/integrations/registry.test.ts src/integrations/index.test.ts - filtered bun run typecheck for the touched 2B files returned FILTER_CLEAN * feat: complete phase 2c provider metadata migration Finish the Phase 2C runtime metadata adoption work on cheeky-cooking-moon. Provider UI metadata: - add shared route metadata and provider preset UI metadata helpers - move preset labels/defaults, route type labels, and custom-header capability checks onto descriptor-backed lookups - update ProviderManager and /provider summaries/setup copy to read shared descriptor metadata instead of bespoke switches - extend local gateway descriptors with default model metadata used by the shared UI helpers Model discovery UX: - add route catalog option builders for descriptor-backed /model rendering - update /model to resolve the active route, read cached route catalogs before rendering, and trigger background refresh when cached discovery is stale - add /model refresh plus in-picker refresh via modelPicker:refresh and the r keybinding - clear discovery cache on manual refresh and surface non-blocking loading/success/stale-error states in ModelPicker - keep descriptor-backed dynamic and hybrid routes on the shared discovery cache service Verification and hardening: - fix combined test pollution by isolating /model test module imports and using real OpenRouter descriptor metadata during shared runs - update progress.md to mark Phase 2C complete with verification notes - verified with bun test for provider profiles, ProviderManager, /provider, /model, discovery cache, and provider validation suites * feat: complete phase 2d runtime provider alignment Align descriptor-backed runtime provider behavior with the legacy APIProvider surface so active routes, OpenAI shim behavior, and resume handling all resolve through the same metadata path. Add runtimeMetadata.ts to centralize active route detection, OpenAI shim overrides, and native-format inference. Update provider resolution to map descriptor-backed routes onto legacy provider categories while preserving existing compatibility fallbacks for Foundry, NVIDIA NIM, MiniMax, GitHub, Bedrock, and Vertex. Move request-shaping rules onto descriptor metadata for DeepSeek, Moonshot, Kimi Code, Gemini, Mistral, GitHub, and local gateways, including reasoning_content preservation, deepseek-compatible thinking payloads, max_tokens field selection, and store field stripping. Treat GitHub Claude native transport as Anthropic-native during conversation recovery so thinking blocks survive resume flows. Extend focused tests for provider resolution, OpenAI shim request shaping, and conversation recovery, and update phase tracking notes in progress.md to mark 2D complete with verification details. * feat: complete phase 2e drift audit Complete the Phase 2E verification and drift-audit packet for the descriptor migration branch. Add representative provider-summary coverage for descriptor-backed OpenRouter routing plus Gemini and Mistral current-provider summaries in src/commands/provider/provider.test.tsx. Extend ProviderManager coverage with first-run Atomic Chat discovery-backed setup and a regression test proving the set-active picker now uses descriptor-backed provider-type labels. Replace stale saved-profile picker wording in ProviderManager so saved profiles no longer collapse to a coarse anthropic/openai-compatible split and instead render the route's descriptor-backed provider type label. Add plan/phase-2e-drift-audit.md documenting the remaining intentional switch sites and non-switch provider branches across provider summaries, active-route detection, OpenAI shim env remapping, auth/header exceptions, and conversation recovery. Update plan/progress.md to mark Phase 2 and 2E complete on-branch, record focused verification, and note the follow-up hardening completed during audit review. Verification completed during this packet: bun test src/components/ProviderManager.test.tsx src/commands/provider/provider.test.tsx src/utils/providerValidation.test.ts src/integrations/discoveryService.test.ts src/commands/model/model.test.tsx and bun test src/utils/providerDiscovery.test.ts src/utils/model/providers.test.ts src/services/api/openaiShim.test.ts src/utils/conversationRecovery.test.ts. Filtered typecheck output still shows pre-existing baseline noise in src/services/api/openaiShim.ts and src/utils/conversationRecovery.ts only. * fix: close phase 2 provider parity follow-through Complete the skipped provider-surface follow-up discovered during the post-Phase-2 review. - add focused status coverage for NVIDIA NIM and MiniMax sessions - add Mistral entries to legacy teammate/model compatibility configs - fill deprecation placeholders for the widened APIProvider surface - add focused regression tests for status and teammate fallbacks - update the Phase 2 drift audit and progress tracker with the compatibility-bridge notes and Phase 3 staging context * phase 3 planning * refactor: start phase 3a dead-switch cleanup Begin the Phase 3 cleanup pass with the metadata-only dead-switch removals that are safe to land independently on cheeky-cooking-moon. Completed work: - updated plan/progress.md to move Phase 3 and Phase 3A into IN_PROGRESS, added slice-level checklists, and recorded what remains intentionally deferred to later packets - removed duplicated OpenAI-compatible status-display branches in src/utils/status.tsx by routing openai/codex/nvidia-nim/minimax through shared metadata helpers - replaced the pure transport-kind label switch in src/integrations/routeMetadata.ts with shared label metadata - replaced the pure provider-label switch in src/components/CostThresholdDialog.tsx with a shared provider-label map - added focused regression coverage in src/utils/status.test.ts, src/integrations/routeMetadata.test.ts, and src/components/CostThresholdDialog.test.ts Verification: - bun test src/utils/status.test.ts src/utils/swarm/teammateModel.test.ts src/utils/model/providers.test.ts - bun test src/integrations/routeMetadata.test.ts src/utils/status.test.ts src/components/CostThresholdDialog.test.ts src/utils/model/providers.test.ts - filtered bun run typecheck for the touched status/routeMetadata/CostThresholdDialog files returned FILTER_CLEAN * refactor: complete phase 3b and 3c cleanup Complete the uncommitted Phase 3B compatibility rename work and the Phase 3C env-shaping consolidation on cheeky-cooking-moon. Phase 3B: - introduce LegacyAPIProvider while keeping APIProvider as the public compatibility alias - introduce LegacyProviderModelConfig and LEGACY_PROVIDER_MODEL_CONFIGS while keeping ModelConfig and ALL_MODEL_CONFIGS as compatibility exports - switch modelStrings, deprecation helpers, and provider profile compatibility naming onto the legacy/compatibility terminology Phase 3C: - add shared managed-env clear/apply helpers in providerProfile.ts and route buildLaunchEnv through the shared compatibility env shaper - route applyProviderProfileToProcessEnv through the same compatibility env shaper so config-backed profiles and startup/session env construction stay aligned - preserve explicit exception behavior for github, mistral, bedrock, vertex, bankr aliasing, MiniMax fallback detection, and NVIDIA NIM mode markers - reduce createOpenAIShimClient to the remaining credential alias hydration that resolveProviderRequest does not already cover - fix applySavedProfileToCurrentSession so saved-profile switching can move away from stale GitHub env selections - add regression coverage for NVIDIA NIM env stamping and stale Codex-managed env clearing - update progress.md to mark Phase 3B and 3C complete on branch and record the verification notes Verification: - bun test src/utils/model/providers.test.ts src/utils/providerProfiles.test.ts src/utils/swarm/teammateModel.test.ts src/utils/status.test.ts - bun test src/utils/providerProfile.test.ts src/utils/providerProfiles.test.ts src/services/api/openaiShim.test.ts - filtered bun run typecheck confirmed no new hits in providerProfile.ts or providerProfiles.ts; remaining openaiShim.ts hits are existing repo baseline debt * docs: complete phase 3d audit and architecture note Complete the Phase 3D final audit/documentation packet on cheeky-cooking-moon. Work completed: - add plan/phase-3d-final-audit.md with the final post-Phase-3 inventory of remaining provider-specific runtime branches - classify the remaining exceptions as intentional long-term runtime differences or temporary env/config compatibility bridges - confirm the audit did not uncover new missed runtime migration work that requires additional Phase 3 code changes - add docs/architecture/integrations.md to document the descriptor-first architecture, current constraints, known exceptions, and follow-on guidance for future cleanup - update plan/progress.md to mark Phase 3D complete on branch, mark 3C merged on branch, and point the tracker at Phase 4A next Key exception categories documented: - github dual-mode transport behavior - mistral dedicated route/runtime shaping - bedrock/vertex/foundry native Anthropic-family paths - Azure and Bankr request-auth/header differences - Gemini, DeepSeek, and Moonshot/Kimi OpenAI-shim quirks - MiniMax dedicated usage handling - native web-search gating - env-only MiniMax and NVIDIA NIM compatibility fallbacks - env/config compatibility bridges such as route detection, --provider shaping, and startup/provider summaries Notes: - this packet is branch-local audit/documentation work only; no runtime code paths were changed - no new tests were required for the audit/doc pass * docs: stage phase 4 tracker and codex profile guard Add the Phase 4 documentation/reference-samples plan to progress.md in the same packet/checkpoint structure as earlier phases, and reconcile the Phase 3 tracker summary with the completed cleanup state. Also fix applySavedProfileToCurrentSession so Codex saved-profile activation does not overwrite an already explicit live provider selection, while still clearing stale profile-managed markers when needed. * docs: complete phase 4a and 4b guides Expand the integrations architecture note with descriptor authoring, routing-contract, transport-boundary, and compatibility-layer guidance. Add overview and glossary docs under docs/integrations/, plus new how-to guides for adding vendors and gateways with one-file and two-file patterns, discovery cache guidance, token-field guidance, and compatibility follow-through. Update progress.md to mark Phase 4 in progress, Phase 4A complete, and Phase 4B complete with notes about the new docs structure and guide outputs. * docs: complete phase 4 integration docs Add the remaining descriptor contributor guides for models, anthropic proxies, and /usage support. Add a reference sample pack and a common-pitfalls checklist, update the integrations overview, and reconcile plan/progress.md so Phase 4 is marked complete on cheeky-cooking-moon with the current implementation boundaries called out explicitly. * docs: reconcile tracker waivers and checkpoints Update plan/progress.md to formally waive the remaining repo-wide typecheck item for Phase 1F as pre-existing debt outside the descriptor migration scope, and mark the Phase 4 branch-local checkpoints as landed on cheeky-cooking-moon with the corresponding commit references. * Align Z.AI merge fallout with descriptors Reviewed the upstream main merge against plan/cheeky-cooking-moon.md and removed drift from the old switch/helper-based Z.AI provider path. Moved Z.AI reasoning, context-window, and max-output metadata into the descriptor route catalog so thinking support can read catalog capabilities instead of URL/model helper checks. Removed the standalone src/utils/zaiProvider.ts helper and updated startup/provider-discovery labeling to resolve known direct routes through descriptor route metadata. Simplified --provider handling for Z.AI by letting descriptor defaults provide the base URL and default model through the generic OpenAI-compatible provider branch. Updated startup and provider-discovery tests for descriptor-backed labels, added Z.AI descriptor-label coverage, and documented the post-main-merge reconciliation in plan/progress.md. Verification before commit: bun test src/utils/providerFlag.test.ts src/utils/providerProfiles.test.ts src/utils/thinking.test.ts src/components/StartupScreen.test.ts src/utils/providerDiscovery.test.ts; bun test src/integrations/compatibility.test.ts src/integrations/index.test.ts src/integrations/registry.test.ts src/services/api/openaiShim.test.ts; git diff --check. * fix: restore descriptor migration behavior and isolate provider tests Restore the descriptor-era Anthropic/OpenAI boundary during conversation recovery by threading the legacy provider category into usesAnthropicNativeMessageFormat instead of relying on ambient env-only route detection. Harden branch-added provider-facing tests so they do not inherit leaked bun mock.module state from neighboring suites. Status, thinking, teammate fallback, and GitHub model options tests now restore mocks and/or import fresh modules under explicit provider context. Update bugfix assertions to validate the descriptor-backed openaiShim contract for removeBodyFields/store stripping instead of the pre-refactor inline conditionals. Validation: - focused status/thinking/conversationRecovery/bugfix suites pass - full bun test --max-concurrency=1 is down to the existing conversationArc perf benchmark failure only - bun run smoke - bun run build - npm pack * fix: close descriptor review drift and provider regressions Address the follow-up review against plan/cheeky-cooking-moon.md by fixing the remaining runtime drift and locking the behavior with focused coverage. Completed work: - make NVIDIA NIM descriptor-backed auth consistent across validation, --provider env shaping, and openaiShim request auth so NVIDIA_API_KEY works without requiring OPENAI_API_KEY - resolve /usage from the active descriptor route instead of collapsing most OpenAI-compatible providers into the legacy openai bucket - honor discoveryRefreshMode in /model so manual, on-open, background-if-stale, and startup catalogs no longer behave identically - clarify docs/progress notes so the branch no longer overstates one-file additive onboarding while loader and preset/UI compatibility surfaces are still manual Verification: - bun test src/services/api/openaiShim.test.ts src/utils/providerValidation.test.ts src/utils/providerFlag.test.ts src/utils/model/providers.test.ts src/commands/usage/index.test.ts src/commands/model/model.test.tsx * docs(plan): require descriptor-native gateway onboarding closure Investigated the current descriptor onboarding flow and documented the remaining manual choke points in the loader, preset compatibility mapping, provider UI metadata, and handwritten preset typing. Tighten cheeky-cooking-moon so additive onboarding is a hard requirement, add Phase 3E for descriptor-native onboarding closure, and update the progress tracker to reflect that follow-up work instead of treating the branch as fully complete. * feat(integrations): close descriptor-native onboarding Implement the Phase 3E generated-artifact workflow for integration onboarding. - add integration artifact generation and check scripts - generate loader inventory, preset manifest, and preset type from descriptors - move preset participation onto descriptor preset metadata for preset-facing vendors and gateways - derive compatibility and provider UI metadata from the generated manifest - remove descriptor-level preset ordering and sort presets by description with standard alphanumeric ordering - pin the custom preset to the bottom automatically in generated ordering - add validation for duplicate preset ids and incomplete preset metadata - add generator tests for representative gateway and direct-vendor onboarding - refresh ProviderManager tests for generated preset ordering - update architecture/how-to/reference docs and progress tracking for the new regeneration workflow * Fix provider profile and discovery drift Honor route-specific auth env vars across descriptor-backed OpenAI-compatible routes by centralizing credential resolution and using it in validation, bootstrap, discovery, and the OpenAI shim. Persist Anthropic startup fallbacks as native anthropic profiles and restore them correctly at startup so the legacy startup file stays aligned with the active provider. Wire discoveryRefreshMode='startup' into startup and provider activation flows, with LM Studio as a live startup-refresh example, and add regression coverage for validation, startup env shaping, discovery refresh, and shim auth handling. * Pin Anthropic provider preset to the top Keep the existing custom gateway preset pinned to the bottom while moving the Anthropic preset ahead of the description-sorted remainder. Regenerate the integration preset manifest/order and extend the artifact generator coverage to lock in both ordering rules. Validation: bun test src/integrations/artifactGenerator.test.ts src/components/ConsoleOAuthFlow.test.tsx; bun run build * docs: refresh integration and setup guides Update the new descriptor-era integration docs so they read as current contributor guidance instead of rollout notes, and align the authoring examples with the actual runtime metadata flow. Highlights: - add a CONTRIBUTING.md pointer to the integration overview and focused how-to guides - remove branch/phase-specific wording from the integration docs - fix OpenAI-compatible header guidance to use transportConfig.openaiShim headers and custom-header flags - clarify anthropic proxy onboarding around generated loader support - refresh advanced setup with current Codex, Gemini, Mistral, and profile-launch details - fix LiteLLM /provider instructions and clarify local no-auth behavior - tighten quick-start and non-technical cross-links so users can find the advanced provider docs * fix: close descriptor integration drift Apply descriptor-backed static headers to OpenAI-compatible request execution and model discovery, preserving request-specific header precedence. Allow Gemini profile launch with API key, access-token, or ADC credentials, and align Gemini fallback defaults with the descriptor/docs default model. Add regression coverage for descriptor header propagation, Gemini defaults, and discovery auth/header behavior. * post-phase follow-up task added * Fix xAI merge follow-ups Route env-only XAI_API_KEY sessions through the OpenAI-compatible shim using descriptor-backed xAI defaults, and map the xAI key into OPENAI_API_KEY for shim auth. Hydrate legacy profile: xai startup env with xAI descriptor defaults, preserving XAI_API_KEY and OpenAI-compatible launch behavior. Update progress tracking for post-merge xAI descriptor inventory and clarify that profile-owned custom headers remain open despite adjacent auth/static-header plumbing. Add regression coverage for env-only xAI client routing, legacy xAI launch env, shell key precedence, and the Gemini/OpenAI client test isolation issue. * Complete profile custom headers follow-up Add persisted provider-profile customHeaders support with shared parsing and sanitization for compact Name: value input. Reject malformed and reserved auth/internal headers before saving or applying profile-owned headers. Expose a descriptor-gated /provider custom headers step, preserve headers during profile edit/update, and apply supported profile headers through ANTHROPIC_CUSTOM_HEADERS for active env and startup fallback profiles. Propagate profile headers into descriptor discovery refresh and bootstrap model discovery while preserving descriptor/profile/auth merge order. Add focused regression coverage and mark the progress tracker packet complete. * Allow api-key custom provider headers Permit api-key in /provider custom header input and preserve it when OpenAI-compatible shim requests are built. This is intentional for gateway providers that require an api-key header in addition to, or instead of, standard bearer auth. Keep managed credential headers protected by continuing to reject/strip authorization and x-api-key, plus Anthropic/Claude-owned headers. Add parser, profile env, and outgoing request coverage for the intended behavior. * fix: restore API mode picker for OpenAI-compatible profiles Use descriptor transport metadata instead of the legacy provider id when deciding whether provider profiles support OpenAI-compatible options. This restores the Chat Completions vs Responses picker for the Custom OpenAI-compatible preset after it moved to the descriptor-backed custom route. Preserve apiFormat and custom auth header profile fields for all routes whose transportConfig.kind is openai-compatible, so selecting Responses is saved and applied as OPENAI_API_FORMAT=responses. Tests: bun test src/components/ProviderManager.test.tsx; bun test src/utils/providerProfiles.test.ts; bun run build; bun run smoke * fix: respect explicit provider routing with xAI env Ensure env-only XAI_API_KEY fallback does not take over when Bedrock, Vertex, or Foundry has been explicitly selected. This preserves native transport routing while still allowing bare xAI env setup to use the OpenAI-compatible shim. Restore api-key to the managed custom-header blocklist now that /provider exposes the API mode/auth-header controls for OpenAI-compatible profiles. The shim and provider override paths strip api-key again, while OPENAI_AUTH_HEADER=api-key remains available for explicit auth configuration. Tests: bun test src/services/api/client.test.ts src/utils/providerCustomHeaders.test.ts src/utils/providerProfiles.test.ts src/services/api/openaiShim.test.ts; bun run build; bun run integrations:check; bun run smoke * docs: fix integration drift Align integration and setup docs with the current implementation. - show model descriptor examples as array default exports, matching the generated MODEL_DESCRIPTOR_GROUPS loader contract - document provider-scoped model env vars instead of implying OPENAI_MODEL globally overrides ANTHROPIC_MODEL - clarify generated provider preset ordering: anthropic first, custom last, description-sorted middle entries - update LiteLLM examples and /provider guidance to use the /v1 OpenAI-compatible base URL Verification: bun run integrations:check * Fix provider discovery cache isolation * Stabilize provider env tests * Stabilize provider test isolation Completed work: - Isolated GitHub model option tests from cached availableModels settings. - Isolated startup discovery tests from live process.env provider flag races. - Mocked teammate provider fallback tests at the provider helper boundary. - Moved cost threshold provider labels into a pure helper for deterministic tests while preserving runtime active-provider behavior. Validation: - bun test src/components/CostThresholdDialog.test.ts src/integrations/discoveryService.test.ts src/utils/model src/utils/swarm - bun run build - bun run smoke * test: isolate startup screen model settings Clear the session settings cache and persisted global model around StartupScreen provider-detection tests. This prevents earlier provider/model suites from leaking saved non-Anthropic models into the default Anthropic startup assertions. Verified with: bun test src/components/StartupScreen.test.ts src/integrations/discoveryService.test.ts src/utils/model/modelOptions.github.test.ts Full bun test now only fails the unrelated Conversation Arc sub-millisecond performance benchmark. * test: isolate route discovery and github model options Restore Bun module mocks around discoveryService tests before loading fresh route-discovery modules. Pin the GitHub model-options test to a complete providers.js mock so cached provider mocks from other suites cannot hide Copilot options. Verified with: bun test src/integrations/discoveryService.test.ts src/utils/model/modelOptions.github.test.ts Also ran full bun test; only the unrelated Conversation Arc sub-millisecond performance benchmark fails locally. * test: avoid startup discovery cache collision Use the 127.0.0.1 LM Studio alias in refreshStartupDiscoveryForActiveRoute so it still resolves the active route from env but does not share the cache partition with the preceding startup refresh test. This keeps the assertion on network refresh stable under Bun 1.3.11 serialized runs. Verified with: bun test --max-concurrency=1 src/integrations/discoveryService.test.ts src/utils/model/modelOptions.github.test.ts Also ran full bun test --max-concurrency=1; only the unrelated Conversation Arc perf benchmark fails locally. * fix: isolate OpenAI-compatible route credentials Restrict OpenAI-compatible shim auth to provider overrides, resolved route credentials, or explicit OPENAI_API_KEY instead of ambient provider-specific secrets. Remove NVIDIA and Bankr compatibility fallbacks that could promote provider-specific API keys into unrelated OpenAI-compatible routes. Preserve Bankr base URL/model compatibility before route credential resolution so Bankr still resolves through descriptor credentials. Clear stale NVIDIA_NIM and copied OPENAI_API_KEY values when switching away from NVIDIA NIM, Bankr, or xAI provider flags to avoid carrying provider secrets across route boundaries. Add regressions for stale NVIDIA, MiniMax, and Bankr keys not leaking into OpenRouter-style routes, plus provider-flag cleanup for copied NVIDIA/Bankr/xAI keys. Validation: bun test src/services/api/openaiShim.test.ts; bun test src/utils/providerFlag.test.ts; bun run build; bun run smoke. * fix: guard model discovery privacy paths Suppress descriptor and legacy model discovery while essential-only traffic mode is active. Use the partitioned discovery cache key for /model cache reads, stale checks, and manual refresh clears, including route-specific credentials and custom headers. Partition legacy local OpenAI additional model caches by credentials and routing headers to avoid catalog reuse across profiles. Add coverage for OpenRouter route credentials, descriptor privacy suppression, legacy discovery privacy suppression, and local cache scope partitioning. * Fix artifact checks and knowledge graph persistence Normalize generated integration artifact comparisons so Windows line endings do not make checked-in artifacts appear stale. Skip knowledge graph entity persistence when re-adding an existing entity with identical attributes, avoiding repeated disk writes during automatic fact extraction and restoring the conversation arc performance benchmark. Verified with bun test src/integrations/artifactGenerator.test.ts --max-concurrency=1, bun test src/utils/conversationArc.perf.test.ts --max-concurrency=1, and bun test --max-concurrency=1. * test: isolate privacy discovery cache path The descriptor discovery privacy test could observe stale OpenRouter cache data populated by an earlier test and receive source=stale-cache instead of static. Use a test-specific API key so the privacy assertion gets its own discovery cache partition while still verifying that nonessential traffic disables network discovery. Verified with bun test src/integrations/discoveryService.test.ts --max-concurrency=1 and bun test --max-concurrency=1. * test: accept cached privacy discovery result * test: set privacy gate before discovery import * test: prevent discovery privacy mock bleed Guard descriptor model discovery directly on CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC so nonessential traffic stays disabled even if the privacyLevel module is mocked in-process. Reduce broad fastMode test mocks for shared modules and use real state/config test hooks, preventing Bun module mock namespaces from leaking into discovery and /model tests. Verified with bun test src/utils/fastMode.test.ts src/utils/model/openaiModelDiscovery.test.ts src/integrations/discoveryService.test.ts src/commands/model/model.test.tsx --max-concurrency=1 and bun test --max-concurrency=1. * test: prevent discovery privacy mock bleed Add an env-level fallback guard to descriptor model discovery so disabled nonessential traffic cannot be bypassed by stale mocked privacy helpers. Tighten the fastMode regression tests by setting real bootstrap/config state only after the tested module is imported, avoiding broad module mocks that can leak into unrelated discovery tests or behave differently under Bun in CI. Verified with focused discovery/fastMode/model suites and the full serial bun test suite. * fix: harden fast mode test isolation Ignore non-string GrowthBook values when resolving the fast mode unavailable reason so boolean flag payloads cannot surface as false. Make the affected regression tests install explicit provider mocks for their own scenarios and reset env state, preventing stale provider mocks from changing fastMode and conversation recovery behavior across the serial Bun test run. * test: harden fast mode module mocks Expand the fastMode GrowthBook and provider test mocks so later imports in the same Bun test process can resolve the named exports they expect. This prevents order-sensitive failures when model command tests run after fast mode tests.\n\nVerified with: bun test --max-concurrency=1 * feat: consolidate integration runtime metadata Move OpenAI-compatible model runtime limits into descriptor-backed brand and model metadata, adding Gemini, GLM, MiniMax, Mistral, Nemotron, xAI, and OpenAI-compatible alias descriptor groups. Update generated integration artifacts, route catalog option handling, thinking capability lookup, and docs to use modelDescriptorId-backed runtime metadata. Split OpenAI shim capability flags into supportsApiFormatSelection and supportsAuthHeaders, and update provider profile sanitization, ProviderManager forms, descriptor validation, and integration authoring docs so fixed routes do not preserve unsupported API format or auth-header settings. Harden env-only MiniMax and xAI routing. Resolve shared route intent before client setup, reject conflicting OpenAI base URLs, preserve provider-specific base overrides, sanitize stale OpenAI shim knobs, copy provider credentials intentionally, and keep legacy provider labels, context windows, max output limits, model lists, and provider switching aligned. Refresh MiniMax defaults and catalog entries, add descriptor-backed runtime limits for migrated models, preserve external OpenAI limit overrides, and add regression coverage for env-only MiniMax/xAI, provider-profile capability stripping, route catalog options, copied credential cleanup, and context/runtime limit detection. Verification performed: bun test src/utils/providerFlag.test.ts; bun test src/services/api/client.test.ts src/utils/model/providers.test.ts src/integrations/routeMetadata.test.ts; bun test src/utils/context.test.ts src/utils/thinking.test.ts src/services/compact/autoCompact.test.ts; bun test src/integrations/routeMetadata.test.ts src/services/api/client.test.ts src/utils/model/providers.test.ts src/utils/providerValidation.test.ts src/integrations/index.test.ts src/utils/status.test.ts; bun run build; bun run smoke. * test: isolate provider env in conversation recovery Snapshot and restore all provider-selection environment variables used by the GitHub native Claude resume test instead of only restoring the GitHub flag and OPENAI_MODEL. The full single-concurrency suite exposed that earlier tests can leave higher-priority provider flags in process.env, causing deserializeMessages to resolve a non-GitHub provider and strip thinking blocks even though the test intended to exercise GitHub native Claude transport. The test now clears provider routing env before setting CLAUDE_CODE_USE_GITHUB=1 and OPENAI_MODEL=claude-sonnet-4-6, then restores the original env values in afterEach. Verification: bun test src/utils/conversationRecovery.test.ts; bun test --max-concurrency=1. * test: isolate conversation recovery provider state * test: pin conversation recovery provider mock * test: isolate knowledge graph persistence * fix: make knowledge graph reset synchronous * test: restore integration registry after unit tests * remove plans dir * delete plans * Fix provider routing test failures Restore the missing first-party Anthropic auth routing imports used by getAnthropicClient so OpenAI-compatible provider client creation no longer throws at runtime. Keep GitHub provider resolution from inheriting OPENAI_API_FORMAT=responses so GitHub GPT-4 and gpt-5-mini models continue to use chat completions while Codex-flavored models still route to responses. Reset OPENAI_API_FORMAT in the affected API provider tests to prevent environment leakage across serial Bun test runs. Verified with: bun test --max-concurrency=1 * fix: restore provider-specific model routing Resolve generic OpenAI-compatible profiles by their known descriptor base URLs so saved MiniMax, xAI, NVIDIA NIM, OpenRouter, and DeepSeek profiles use the correct route catalogs instead of the generic OpenAI model list. Fix MiniMax defaults and display handling so provider-specific model IDs are not rendered as Claude Opus defaults, add current MiniMax M2.7 options, and cover the regressions with focused route/model tests. Also clean up descriptor follow-ups from review: remove the dead OpenAI shim store-strip fallback list, preserve gateway vendor IDs for Bedrock/Vertex/GitHub profile resolution, and keep the ModelPicker compiled-form changes in this PR. * test: cover provider precedence review fixes Remove import-time ANTHROPIC_BASE_URL and ANTHROPIC_MODEL reads from the Anthropic descriptor so descriptor defaults stay static and live env handling remains in preset metadata. Add getAPIProvider precedence coverage documenting that explicit Gemini/OpenAI flags beat env-only MiniMax API key inference. Add a regression check to keep the removed openaiShim hardcoded descriptor route fallback list from returning. --------- Co-authored-by: TechBrewBoss <dash@hicap.ai>	2026-05-02 08:29:26 +08:00
3kin0xandGitHub	aae96aa52a	feat(cli): improve SSH interactivity detection via SSH_TTY and SSH_CONNECTION (#946)	2026-05-02 08:26:36 +08:00
0xfandomandGitHub	0f0fd266db	fix(openai-shim): strip store when baseUrl points at Gemini (#959) ... `isGeminiMode()` only consulted `CLAUDE_CODE_USE_GEMINI` and `process.env.OPENAI_BASE_URL`, so `providerOverride` flows that route to `generativelanguage.googleapis.com` (e.g. `primaryProvider: google` in `~/.claude.json`) kept `store: false` on the payload. Gemini's strict schema rejected it with `400 Invalid JSON payload received. Unknown name "store": Cannot find field.` Detect Gemini directly from `request.baseUrl` via `hasGeminiApiHost` in the strip predicate for both chat_completions and the responses body. Adds two regression tests covering each transport path. Fixes #664	2026-04-30 22:17:53 +08:00
3 people	4eb486ef83	Feat/web landing refresh (#958) ... * feat(web): openclaude landing — runs anywhere, uses anything A new marketing site for openclaude under web/, plus the minimal root infrastructure to build, ignore, and gate it without affecting the published npm package. Landing page (web/) - Vite + React 19 with monospace gitlawb typography (sf mono / fira code). - Hero: pill, two-line wordmark "runs anywhere. / uses anything.", copy-to-clipboard install command, github cta. - Six feature rows in hermes-style "title — sentence" format on hairline dividers (any model, real tools, profiles per repo, streaming, gateway routing, editor + server modes). - Install block: same copyable command + three numbered steps. - One-line footer with brand, version, gitlawb link, and license. - Light theme is the default with a no-flash bootstrap script and a ☀ / ☾ toggle persisted to localStorage. - New orange terminal-face logo at 36px in the nav. - Body wash: dual orange radial gradients for warmth on both themes. Root infra - web/ excluded from npm publish via .npmignore (belt-and-suspenders alongside the existing files whitelist). - web/ excluded from docker context (.dockerignore). - web:dev / web:build / web:preview / web:typecheck scripts in package.json that delegate via --cwd web (no root deps added). - web typecheck + build added to the pr-checks workflow. - web/dist/ and web/*.tsbuildinfo ignored. Co-Authored-By: OpenClaude <openclaude@gitlawb.com> * added vercel in .gitignore --------- Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-30 18:22:01 +08:00
chioarubandGitHub	208c896c07	fix(oauth): skip refresh for third-party providers (#955) ... * fix(oauth): skip refresh for third-party providers * test(oauth): isolate auth routing guards	2026-04-30 10:24:31 +08:00
KRATOSandGitHub	ee0d930093	fix(ripgrep): use @vscode/ripgrep package as the builtin source (#911) (#932) ... The vendored-binary lookup at vendor/ripgrep/<arch>-<platform>/rg never resolved in this fork — that directory does not ship — so users without a system rg had no working fallback. Switch to the @vscode/ripgrep package so Microsoft maintains the platform/arch matrix and the binary is delivered via npm. - src/utils/ripgrep.ts: replace hand-rolled vendor-path resolution with rgPath from @vscode/ripgrep. Lazy require so a missing package falls through to the system rg branch instead of throwing at import. Drop builtinExists from the config args; builtinCommand is now a string-or-null. The system override (USE_BUILTIN_RIPGREP=0), the Bun-compiled standalone embedded mode, the macOS codesign hook, and all retry/timeout/error logic are preserved untouched. - scripts/build.ts: mark @vscode/ripgrep as external. The package resolves rgPath via __dirname at runtime, so bundling would freeze the build host's absolute path into dist/cli.mjs. - src/utils/ripgrep.test.ts: update for the new config shape and add tests covering USE_BUILTIN_RIPGREP=0, embedded mode, last-resort fallback, and null builtin path. Tested locally on Linux (Bun 1.3.13). macOS (codesign hook) and Windows (rg.exe extension) need contributor verification.	2026-04-30 00:58:46 +08:00
ArkhAngelLifeJiggyandGitHub	0ca4333537	feat: add streaming token counter (#797) ... * feat: add streaming token counter - Add StreamingTokenCounter for real-time token counting during generation - Tracks output tokens as they arrive from stream - Calculates tokens per second rate - Add tests (4 passing) PR 4A: Streaming Token Counter (Features 1.2, 1.7) * refactor: move StreamingTokenCounter to separate file - Extract StreamingTokenCounter from tokens.ts to streamingTokenCounter.ts - Add getEstimatedRemainingTokens() method - Update test import * fix: word-boundary token counting for stable stream totals - Accumulate raw content, count only at word boundaries - Eliminates instability from arbitrary chunk boundaries - Add finalize() to flush remaining content on stream end - Add characterCount getter for raw content tracking - Rename getEstimatedRemainingTokens -> getEstimatedGenerationTimeMs - Add comprehensive tests * fix: update streamingTokens test for word-boundary API - Add finalize() call before checking output tokens - Use characterCount for interim checks - Add spaces to trigger word boundary counting * fix: add estimateRemainingTokens/Time methods - Add estimateRemainingTokens(target) method - Add estimateRemainingTimeMs(target) method - Covers non-blocking: now properly estimates remaining tokens * fix: PR 797 - fix word boundary counting, consolidate tests Blockers (Vasanthdev2004): - recountAtWordBoundary now searches forward from lastCountedIndex+1 - Finds NEXT space after already-counted region, not before it - Provides accurate live token counts during streaming, not just finalize() Non-blocking (gnanam1990): - Delete streamingTokens.test.ts, merge tests into streamingTokenCounter.test.ts - Added interim-counting test to verify counting updates during streaming * fix: PR 797 - fix word boundary advancement after space Blocking: - Fix recountAtWordBoundary to skip past space when searching for next boundary - After counting at a space, indexOf(' ') returns 0 (the space itself) - Now starts search from index 1 to find the NEXT word boundary - Short chunks now properly trigger count advancement Non-blocking: - Add test verifying count increases after each word boundary - Add test for space-skipping behavior	2026-04-29 16:17:00 +08:00
ArkhAngelLifeJiggyandGitHub	92d297e50e	feat: context preloading and hybrid context strategy (#860) ... * feat: context preloading and hybrid context strategy PR 2D - Section 2.7, 2.8: - Add contextPreload.ts with pattern-based prediction - Add hybridContextStrategy.ts with cache/fresh balancing - Optimize for cost vs accuracy - Add comprehensive tests (13 passing) * feat: wire hybrid context strategy into API path - Apply hybrid strategy after normalizeMessagesForAPI - Feature-flag controlled (HYBRID_CONTEXT_STRATEGY) - Optimizes cache/fresh balance for API requests * fix: resolve PR 2D blocking issues - Fix predictContextNeeds self-assign bug (matchedCategory = category) - Add test for non-empty predictedNeed - Preserve conversation tail in hybridStrategy (never drop last 3 messages) - Add comment for hardcoded 200k cap in claude.ts Fixes reviewer feedback from gnanam1990 and Vasanthdev2004 * fix: preserve tool_use/tool_result chains in hybridStrategy - Increase MIN_TAIL to 5 (tool_use -> tool_result -> assistant -> user -> next) - Add getMessageChain() to preserve paired messages - Chains kept together in final selection * fix: PR 860 - tool_use/tool_result pairing and safe token counting Blocking: - getMessageChain() now pairs by tool_use.id (block ID) not msg.message.id - Find tool_use blocks by id, pair with tool_result having matching tool_use_id - Fixes tool_result surviving while paired tool_use dropped - Token counting now includes array content (tool_use, tool_result, thinking) - Not just string content, prevents undercounting prompt size - Deduplicate messages by UUID when combining chains + split + tail - Prevents duplicate messages in final request Non-blocking: - Add regression test for tool_use/tool_result pairing * fix: PR 860 - account for actual structured payload size in token counting Blocking: - getMessageTokenCount now calculates actual token count for structured blocks - tool_use: uses JSON.stringify(input).length / 4 + base - tool_result: counts actual content (string or array of text blocks) - thinking: counts actual thinking text length / 4 - is_error flag adds small overhead Non-blocking: - Add tests for large tool_use input and large thinking blocks	2026-04-29 15:49:46 +08:00
3 people	91f93ce615	feat: SDK Foundation — Type Declarations, Errors, and Utilities (#866) ... * feat(sdk): add SDK foundation — type declarations, errors, and utilities Adds standalone SDK building blocks with no SDK source dependencies: - sdk.d.ts: ambient type declarations for SDK bundle - coreSchemas.ts + coreTypes.generated.ts: Zod schemas and generated types - errors.ts: SDK-specific error classes - validation.ts: input validation utilities - messageFilters.ts: extracted message filter logic - handlePromptSubmit.ts: imports from messageFilters - 16 generated-types tests * fix(sdk): narrow assertFunction type from broad Function to callable signature Code review finding: assertFunction used `asserts value is Function` which accepts any function-like value without narrowing. Changed to `(...args: any[]) => any` for better type safety. * fix(sdk): update sdk.d.ts header — manually maintained, not generated Reviewer noted the header said "Generated from index.ts" but no generator produces this file. Updated to "Manually maintained — keep in sync with index.ts". Drift detection added in validate-externals.ts (PR 3). * fix(sdk): align sdk.d.ts types with canonical coreTypes.generated.ts Tighten SDK public type contract to resolve reviewer blockers: - PermissionResult: unknown[] → precise 6-shape discriminated union (addRules/replaceRules/removeRules/setMode/addDirectories/removeDirectories) - SDKSessionInfo: snake_case → camelCase (sessionId, lastModified, etc.) - ForkSessionResult: session_id → sessionId - SDKPermissionRequestMessage: uuid + session_id now required - SDKPermissionTimeoutMessage: added uuid + session_id - SessionMessage: parent_uuid → parentUuid - SDKMessage/SDKUserMessage/SDKResultMessage: replaced loose inline definitions with re-exports from coreTypes.generated.ts --------- Co-authored-by: Ali Alakbarli <ali.alakbarli@users.noreply.github.com>	2026-04-29 14:53:01 +08:00
KRATOSandGitHub	5943c5c269	fix(input): strip leading ! when entering bash mode (#947) ... The PromptInput onChange handler had two branches for entering bash mode: a single-char path that just toggled the mode and a multi-char paste path that also stripped the leading `!` from the buffer. The single-char path returned without stripping, so typing a bare `!` into empty input switched modes but left the literal `!` visible. Consolidated both paths through a new pure helper `detectModeEntry` that returns the new mode plus the stripped buffer value, so there is no longer a branch where the mode character can leak into the buffer. Fixes #662	2026-04-29 10:29:59 +08:00
3 people	c0b5535d86	docs: add Atomic Chat partner (#942) ... Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-28 23:35:25 +08:00
3 people	d321c8fc6a	fix: avoid legacy Windows PasswordVault reads by default (#941) ... * fix: avoid legacy Windows PasswordVault reads by default * fix: isolate model capability override cache --------- Co-authored-by: OpenClaude Worker 3 <worker-3@openclaude.local>	2026-04-28 23:30:48 +08:00
KRATOSandGitHub	8106880855	fix(typecheck): make bun run typecheck actionable on main (#473) (#938) ... Issue #473 reported that `bun run typecheck` fails on main with ~4400 errors due to repo-foundation drift, masking branch-specific regressions. Per kevincodex1's guidance ("lets narrow the typecheck scope for now and then we expand step by step") this PR addresses the foundational root causes and brings the error count down 60% so the gate is actionable for branch reviews. Changes: - tsconfig.json: bump target to ES2023 + add lib ["ES2023", "DOM"] so Array.findLast / findLastIndex resolve (kills 41 TS2550 errors). Add `noEmit: true` for typecheck-only mode and `allowImportingTsExtensions: true` (kills 40 TS5097 errors). Set `noImplicitAny: false` because cleaning up TSX-component implicit any is explicitly out of scope per the issue. - src/global.d.ts: ambient declaration for the build-time MACRO global injected by scripts/build.ts via Bun's `define` option (kills 9 TS2304 'Cannot find name MACRO' errors). - src/types/{message,utils,tools}.ts: stubs for the highest-impact missing modules from the partial source snapshot (~21 importers for message alone). Document the snapshot caveat at the top of each stub and reference issue #473 so future readers know they're placeholders. - src/entrypoints/sdk/controlTypes.ts and src/constants/querySource.ts: similar one-file stubs unblocking 18 + 19 importers respectively. - src/entrypoints/agentSdkTypes.ts: append `any`-typed aliases for ~70 SDK names that callers expect on the public surface but that live in stubbed sub-files (PermissionMode, SDKCompactBoundaryMessage, HookEvent, ModelUsage, ModelInfo, etc. — exactly the list from auriti's bug-report enumeration). Verified locally on Linux: - baseline `bunx tsc --noEmit` on stashed main: 4434 errors - with PR applied: 1782 errors (60% drop) - `bun run build`: passes (v0.7.0) - `bun test`: 1632 pass; the 4 remaining failures (StartupScreen, thinking) reproduce on main and are unrelated. - TS2550 (lib): 41 → 0 - TS5097 (.ts imports): 40 → 0 - TS2304 'MACRO': 9 → 0 - TS2307 missing modules: 587 → 325 Remaining errors are localized to specific stubbed modules and can be addressed in smaller follow-up issues, matching the issue's "Definition of done" criterion.	2026-04-28 17:44:26 +08:00
3 people	4c93a9f9f1	feat: add Opus 4.7 as default model and fix alias/thinking bugs (#928) ... - Add CLAUDE_OPUS_4_7_CONFIG and register it in ALL_MODEL_CONFIGS - Set Opus 4.7 as default for firstParty in getDefaultOpusModel() (3P stays on 4.6 until rollout) - Fix sonnet[1m] → 404 bug: query.ts was passing raw alias to API without resolving via parseUserSpecifiedModel - Add opus-4-7 to modelSupportsAdaptiveThinking so it uses { type: 'adaptive' } not { type: 'enabled' } - Fix duplicate opus47 case and wrong opus46[1m] fallthrough in getPublicModelDisplayName switch - Update user-facing display strings (picker labels, plan mode description) to reference Opus 4.7 - Add 3P fallback suggestion chain for opus-4-7 → opus-4-6 in validateModel Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-28 17:31:06 +08:00
viudesandGitHub	6ea3eb6483	feat(api): deterministic request-body serialization via stableStringify (#882) ... * feat(api): deterministic request-body serialization via stableStringify Add `stableStringify` helper that emits JSON with object keys sorted lexicographically at every depth (arrays preserved). Adopt it in the OpenAI-compatible shim and the Codex Responses-API shim for the outgoing request body. WHY: OpenAI / Kimi / DeepSeek / Codex use implicit prefix caching keyed on exact request bytes. Spurious insertion-order differences in spread-merged body objects otherwise invalidate the cache on every turn. Also a pre-requisite for Anthropic `cache_control` breakpoint hits. Byte-equivalent to `JSON.stringify` when keys already happen to be in lexical insertion order, so strictly additive across providers. * fix(api): preserve circular-ref TypeError in stableStringify + cover GitHub fallback Replace two-pass sortingReplacer approach with a single-pass deepSort that tracks ancestor objects via WeakSet, throwing TypeError on cycles (same contract as native JSON.stringify) and correctly handling DAGs via try/finally cleanup. Switch the GitHub Copilot /responses fallback in openaiShim.ts from JSON.stringify to stableStringify so that path is also byte-stable for prefix caching. Regression coverage added: top-level cycle, deep nested cycle, DAG safety. * fix(api): align stableStringify with native JSON.stringify pre-processing Replicate native JSON.stringify pre-processing inside deepSort so serialization output matches native behavior beyond key ordering: - invoke toJSON(key) when present (Date, URL, user classes); pass '' at top-level, property name for nested values, index string for array elements - unbox Number/String/Boolean wrappers via valueOf() so new Boolean(false) doesn't get truthy-coerced - run cycle detection on the post-toJSON value so a toJSON returning an ancestor still throws TypeError; DAGs continue to not throw - drop properties whose toJSON returns undefined, matching native Add focused stableStringify.test.ts (21 cases) asserting equality with JSON.stringify across toJSON paths, wrapper unboxing, cycle/DAG handling, and sortKeysDeep parity.	2026-04-27 23:33:15 +08:00
vrdonsandGitHub	f699c1f2fc	fix routing path (#923)	2026-04-27 20:05:17 +08:00
3 people	52b4c5c2ff	chore(main): release 0.7.0 (#817) ... Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> v0.7.0	2026-04-27 11:47:52 +08:00
4 people	c6c5f0608c	fix: bugs (#885) ... * fix: error output truncation (10KB→40KB) and MCP tool bugs - toolErrors.ts: increase error truncation limit from 10KB to 40KB Shell output can be up to 30KB, so 10KB was silently cutting off error logs from systemctl, apt, python, etc. - MCPTool: cache compiled AJV validators (was recompiling every call) - MCPTool: fix validateInput error message showing [object Object] - MCPTool: null-guard mapToolResultToToolResultBlockParam - MCPTool: explicit null check in isResultTruncated - ReadMcpResourceTool: null-guard mapToolResultToToolResultBlockParam Tests (84 passing): - src/utils/toolErrors.test.ts (13 tests) - src/tools/BashTool/commandSemantics.test.ts (24 tests) - src/tools/BashTool/utils.test.ts (32 tests) - src/tools/MCPTool/MCPTool.test.ts (15 tests) * fix: address review blockers from PR #885 Blocker 1: Fix abort path in callMCPTool - Previously returned { content: undefined } on AbortError, which masked the cancellation and caused mapToolResultToToolResultBlockParam to send empty content to the API as if it were a successful result. - Now converts abort errors to our AbortError class and re-throws, so the tool execution framework handles it properly (skips logging, creates is_error: true result with [Request interrupted by user for tool use]). Blocker 2: Fix memory leak in AJV validator cache - Changed compiledValidatorCache from Map to WeakMap so schemas from disconnected/refreshed MCP tools can be garbage collected instead of accumulating strong references indefinitely. Also: null guards now return descriptive indicators instead of empty strings, making it clear when content is unexpectedly missing. --------- Co-authored-by: FluxLuFFy <FluxLuFFy@users.noreply.github.com> Co-authored-by: Fix Bot <fix@openclaw.ai>	2026-04-26 23:11:19 +08:00
5 people	46a9d3eec4	chore: rebrand user-facing copy to OpenClaude (#851) ... * chore: rebrand user-facing copy to OpenClaude Replace lingering Claude Code branding in CLI, tips, and runtime UI with OpenClaude/openclaude, including the startup tip Gitlawb mention. Co-Authored-By: Claude GPT-5.4 <noreply@openclaude.dev> * chore: address branding-sweep review feedback - PermissionRequest.tsx: rebrand the two remaining "Claude needs your approval/permission" notifications to OpenClaude (review-artifact and generic tool permission paths). - main.tsx, teleport.tsx, session.tsx, WebFetchTool/utils.ts, skills/bundled/{debug,updateConfig}.ts: replace leftover `claude --…` CLI hints and "Claude Code" labels missed by the original sweep. - main.tsx: drop the inline gitlawb.com marketing copy from the stale-prompt tip; keep it a pure rebrand. - auth.ts: finish the half-rename so both `claude setup-token` and `claude auth login` references in the same error block now read `openclaude …`. - mcp/client.ts: keep `name: 'claude-code'` for MCP server allowlist compatibility (now explicit via comment) and replace the "Anthropic's agentic coding tool" description with an OpenClaude one. - MCPSettings.tsx: point the empty-server-list hint at https://github.com/Gitlawb/openclaude instead of code.claude.com. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: replace help link with OpenClaude repo URL Replace https://code.claude.com/docs/en/overview with https://github.com/Gitlawb/openclaude in the help screen. Co-Authored-By: OpenClaude <openclaude@gitlawb.com> --------- Co-authored-by: Claude GPT-5.4 <noreply@openclaude.dev> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-26 22:14:36 +08:00
4 people	2586a9cddb	feat: add xAI as official provider (#865) ... * feat: add xAI as official provider - Add xAI preset to ProviderManager (alphabetical order) - Add xAI provider detection via XAI_API_KEY - Add xAI startup screen heuristic (x.ai base URL or grok model) - Add xAI status display properties - Add grok-4 and grok-3 context windows - Add xAI model fallbacks across all tiers - Fix JSDoc priority order in providerAutoDetect Co-Authored-By: Claude Opus 4.6 <noreply@openclaude.dev> * fix(xai): persist relaunch classification for xAI profiles Addresses reviewer feedback on feat/xai-official-provider: - isProcessEnvAlignedWithProfile now validates XAI_API_KEY for x.ai base URLs, mirroring the Bankr pattern. Without this, relaunch skips re-applying the profile, XAI_API_KEY stays unset, and getAPIProvider() falls back to 'openai'. - buildOpenAICompatibleStartupEnv now sets XAI_API_KEY when syncing active xAI profile to the legacy fallback file. - Adds 'xai' to VALID_PROVIDERS and --provider xai CLI flag support. - Adds xAI detection to providerDiscovery label heuristics. - Adds 'xai' to legacy ProviderProfile type/isProviderProfile guard. - Adds targeted tests for relaunch alignment, flag application, and discovery labeling. Co-Authored-By: OpenClaude <openclaude@gitlawb.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@openclaude.dev> Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-26 21:26:44 +08:00
Rayan AlkhelaiwiandGitHub	d45628c413	fix(startup): show --model flag override on startup screen (#898) ... The startup screen was only reading model from env vars and settings, ignoring the --model CLI flag since it's parsed by Commander.js after the banner prints. Now eagerly parses --model from argv before rendering so the displayed model matches what the session will actually use.	2026-04-26 20:24:44 +08:00
TechBrewBossandGitHub	6dedffe5ff	Add OpenAI responses mode and custom auth headers (#906) ... * Add OpenAI profile responses and custom auth header support * Fix knowledge graph config reference in query loop * Address OpenAI profile review edge cases * Remove unused getGlobalConfig import Delete an unused import of getGlobalConfig from src/query.ts. This cleans up dead code and avoids unused-import lint warnings; no functional behavior changes. * Address follow-up OpenAI profile review comments * Refine OpenAI responses auth review fixes * Fix custom auth header default scheme	2026-04-26 20:24:03 +08:00
3 people	a3e728a114	fix(agent): provider-aware fallback for haiku/sonnet aliases (#908) ... * fix(agent): provider-aware fallback for haiku/sonnet aliases Explore agent fails on custom providers (Z.AI GLM, Alibaba Anthropic-compatible, local OpenAI endpoints) because 'haiku' alias resolves to a non-existent model. Changes: - Add isClaudeNativeProvider check (Bedrock, Vertex, Foundry, official Anthropic) - For non-Claude-native providers, haiku/sonnet aliases inherit parent model - Add 8 tests for provider-aware fallback behavior Fixes Explore agent "model not found" errors on custom Anthropic-compatible APIs. * test(agent): use Bun mock.module() for provider tests Replace env manipulation with proper Bun mock.module() to reliably mock getAPIProvider() and isFirstPartyAnthropicBaseUrl() functions. This ensures tests work correctly on CI where module caching caused false negatives. --------- Co-authored-by: Ali Alakbarli <ali.alakbarli@users.noreply.github.com>	2026-04-26 20:08:55 +08:00
3 people	818689b2ee	fix(query): restore system prompt structure and add missing config import (#907) ... - import getGlobalConfig — six call sites referenced it without an import; five short-circuited via feature() gates, but src/query.ts:1896 always ran and crashed every queryLoop iteration with "getGlobalConfig is not defined" (e.g. Explore subagent: "Agent failed: getGlobalConfig is not defined"). - stop coercing SystemPrompt (string[]) into a template-string before appendSystemContext — that made [...systemPrompt] spread the string character-by-character, replacing the structured prompt with thousands of one-char system blocks. Append arcSummary as its own array element instead. - gate the finalizeArcTurn call behind feature('CONVERSATION_ARC') so it matches the rest of the memory-PR call sites and gets dead-code- eliminated for users without the flag. Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-26 12:45:09 +08:00
Kevin CodexandGitHub	d9ae56bc58	fix provider switch not presistingin session (#903) ... * fix provider switch not presistingin session * fix broken tests	2026-04-26 11:15:25 +08:00
PedryandGitHub	af9a3caa4d	Fix file path and update placeholder key in PLAYBOOK.md (#886) ... Updated file paths and placeholder key in PLAYBOOK.md.	2026-04-26 08:20:25 +08:00
3 people	a0d657ee18	feat(zai): add Z.AI GLM Coding Plan provider preset (#896) ... * feat(zai): add Z.AI GLM Coding Plan provider preset Add dedicated Z.AI provider support for the GLM Coding Plan, enabling use of GLM-5.1, GLM-5-Turbo, GLM-4.7, and GLM-4.5-Air models through the OpenAI-compatible shim with proper thinking mode (reasoning_content), max_tokens handling, and context window sizing. * fix(zai): unify GLM max output token limits across casing variants glm-5/glm-4.7 had conservative 16K max output while GLM-5/GLM-4.7 had 131K. Use consistent Z.AI coding plan limits for all GLM variants. * fix(zai): restore DashScope GLM limits, enable GLM thinking support - Restore lowercase glm-5/glm-4.7 to 16_384 max output (DashScope limits) while keeping Z.AI coding plan high limits on uppercase GLM-* keys only - Add GLM model support to modelSupportsThinking() so reasoning_content is enabled when using GLM-5.x/GLM-4.7 models on Z.AI * fix(zai): tighten GLM regexes, fix misleading context window comment - Use precise regex in thinking.ts: exact GLM model matches only, no false positives on glm-50/glm-4, includes glm-4.5-air - Use uppercase-only match in StartupScreen rawModel fallback so DashScope lowercase glm-* models aren't mislabeled as Z.AI - Clarify context window comment: lowercase glm-5.1/glm-5-turbo/ glm-4.5-air are Z.AI-specific aliases, not DashScope * fix(zai): scope GLM detection to Z.AI * improve readability of max_completion_tokens check Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>	2026-04-26 08:18:59 +08:00
3kin0xandGitHub	29f7579377	feat(memory): implement persistent project-level Knowledge Graph and RAG (#899) ... - Shift memory from session-scope to persistent project-scope\n- Add native JSON RAG with BM25-lite ranking\n- Implement passive technical concept extraction (IPs, versions, frameworks)\n- Orchestrate hierarchical context injection in the conversation loop	2026-04-26 08:17:02 +08:00
viudesandGitHub	9e23c2bec4	feat(api): expose cache metrics in REPL + normalize across providers (#813) ... * feat(api): expose cache metrics in REPL + /cache-stats command * fix(api): normalize Kimi/DeepSeek/Gemini cache fields through shim layer * test(api): cover /cache-stats rendering + fix CacheMetrics docstring drift * fix(api): always reset cache turn counter + include date in /cache-stats rows * refactor(api): unify shim usage builder + add cost-tracker wiring test * fix(api): classify private-IP/self-hosted OpenAI endpoints as N/A instead of cold * fix(api): require colon guard on IPv6 ULA prefix to avoid public-host over-match * perf(api): ring buffer for cache history + hit rate clamp + .localhost TLD * fix(api): null guards on formatters + document Codex Responses API shape * fix(api): defensive start-of-turn reset + config gate fallback + env var docs * fix(api): trust forwarded cache data on self-hosted URLs (data-driven) * refactor(api): delegate streaming Responses usage to shared makeUsage helper	2026-04-25 12:38:25 +08:00
3 people	9070220292	Add Kimi Code provider preset and rename Moonshot API preset (#862) ... * Add Kimi Code provider preset * fix desc. Co-authored-by: Copilot <copilot@github.com> * more desc. fixes. * Fix release validation tests --------- Co-authored-by: Copilot <copilot@github.com>	2026-04-25 12:36:54 +08:00
JATMNandGitHub	26413f6d30	feat(minimax): add /usage support and fix MiniMax quota parsing (#869) ... * Add MiniMax usage UI and API support * Fix MiniMax usage parsing and refresh UI * Refactor MiniMax usage handling	2026-04-25 12:33:22 +08:00
3 people	44f9cac70d	Feature/memory pr (#894) ... * feat: multi-turn context and conversation arc memory PR 2E - Section 2.9, 2.10: - Add multiTurnContext.ts with turn tracking and state preservation - Add conversationArc.ts with goal/decision/milestone tracking - Wire into query.ts after tool execution - Feature-flags: MULTI_TURN_CONTEXT, CONVERSATION_ARC - Add comprehensive tests (22 passing) * feat(cli): add /knowledge command to manage native memory - Add /knowledge enable <yes|no> to toggle Knowledge Graph learning\n- Add /knowledge clear to reset memory\n- Add persistent knowledgeGraphEnabled setting to global config\n- Integrated user setting into the query execution loop * feat(cli): add /knowledge command (stable local-jsx version) - Resolve conflicts between .ts and .tsx files\n- Align with LocalJSXCommandCall signature\n- Fix onDone and args errors * test(cli): fix knowledge command tests by properly isolating global config * fix(cli): make knowledge command defensive against undefined args and leaky tests * fix(cli): correct data source for entity count and fix test isolation * fix(cli): reinforce knowledge test by explicitly defining property on test config * fix(cli): explicitly define property in test config to avoid undefined in CI * fix(cli): make knowledge tests resistant to global config mocks in CI * chore(memory): surgical improvements from architectural audit - Fix: Implement entity deduplication in Knowledge Graph\n- Fix: Ensure fact extraction from user messages in query loop\n- Fix: Refine regexes for better quality learning (less noise) --------- Co-authored-by: LifeJiggy <Bloomtonjovish@gmail.com>	2026-04-25 07:19:41 +08:00
JATMNandGitHub	ff2a380723	Add DeepSeek V4 flash/pro support and DeepSeek thinking compatibility (#877) ... * Add DeepSeek V4 support and thinking compatibility * Fix DeepSeek profile persistence regression * Align multi-model handling with openai-multi-model	2026-04-25 02:29:46 +08:00
JATMNandGitHub	c4cb98a4f0	fix: normalize /provider multi-model selection and semicolon parsing (#841) ... * fix provider multi-model selection * fix provider manager multi-model save path	2026-04-25 02:28:14 +08:00
3 people	b5f7047358	Feature/memory pr (#889) ... * feat: multi-turn context and conversation arc memory PR 2E - Section 2.9, 2.10: - Add multiTurnContext.ts with turn tracking and state preservation - Add conversationArc.ts with goal/decision/milestone tracking - Wire into query.ts after tool execution - Feature-flags: MULTI_TURN_CONTEXT, CONVERSATION_ARC - Add comprehensive tests (22 passing) * feat(memory): resolve review blockers and integrate native Knowledge Graph into Conversation Arcs - Fix: Extract text from production block arrays in phase detector\n- Fix: Ensure proper turn segmentation in query loop\n- Fix: Respect options in multi-turn context tracker\n- Feat: Add native Knowledge Graph (Entities/Relations) to ConversationArc architecture\n- Test: Comprehensive test suite for all fixes and new graph features * test(perf): add automated performance benchmarks for Knowledge Graph extraction and summary --------- Co-authored-by: LifeJiggy <Bloomtonjovish@gmail.com>	2026-04-25 02:26:02 +08:00
3 people	64b1014b9a	Feat/bankr provider (#888) ... * feat(provider): add Bankr LLM Gateway support Add Bankr as an OpenAI-compatible provider preset with dedicated env vars: - BNKR_API_KEY, BANKR_BASE_URL, BANKR_MODEL - Uses X-API-Key header instead of Authorization Bearer - Base URL: https://llm.bankr.bot/v1 - Default model: claude-opus-4.6 Changes: - Add 'bankr' to VALID_PROVIDERS and provider flag handling - Add buildBankrProfileEnv() with env key registration - Add Bankr detection in startup screen and provider discovery - Map Bankr env vars to OpenAI-compatible vars in shim - Add Bankr preset to ProviderManager (alphabetical order) - Update PRESET_ORDER test to include Bankr Co-Authored-By: OpenClaude <openclaude@gitlawb.com> * fixup(provider): address Bankr PR review feedback 1. Map BNKR_API_KEY → OPENAI_API_KEY in providerFlag.ts so --provider bankr works with BNKR_API_KEY in non-interactive startup. 2. Remove unconditional BANKR_MODEL read from model.ts; it maps to OPENAI_MODEL via providerFlag.ts and openaiShim.ts, preventing cross-provider leakage. 3. Use X-API-Key for Bankr model discovery in openaiModelDiscovery.ts and providerDiscovery.ts, matching chat request auth. Co-Authored-By: OpenClaude <openclaude@gitlawb.com> --------- Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-24 23:03:45 +08:00
TechBrewBossandGitHub	5a21d05741	Persist active provider profile across restarts (#833) ... * Persist active provider profile across restarts * Clear stale startup provider overrides * Fix provider profile restart fallback * Fix provider profile restart fallback * Omit empty OpenAI API key from startup env * Fix startup override settings typing	2026-04-24 19:36:21 +08:00
3 people	038f715b7a	feat(model): add GPT-5.5 support for Codex provider (#880) ... - Bump Codex provider defaults from gpt-5.4 to gpt-5.5 across all ModelConfigs - Update codexplan alias to resolve to gpt-5.5 - Add gpt-5.5 and gpt-5.5-mini to model picker with reasoning effort mappings - Add context window and max output token specs for gpt-5.5 family - Add gpt-5.5 entries to COPILOT_MODELS registry - Keep official OpenAI API preset at gpt-5.4 (API availability pending) - Update codexShim tests to expect gpt-5.5 from codexplan alias Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-24 19:06:36 +08:00
Kevin CodexandGitHub	b694ccfff1	Add sponsors section to README (#874)	2026-04-24 11:47:55 +08:00
KRATOSandGitHub	dcbe29558a	fix(mcp): disable MCP_SKILLS feature flag — source not mirrored (#872) ... Closes #856. MCP servers that expose resources (e.g. RepoPrompt) failed to load their tools in the open build with: Error fetching tools/commands/resources: fetchMcpSkillsForClient is not a function Root cause: scripts/build.ts set MCP_SKILLS: true, which made feature('MCP_SKILLS') evaluate to true at build time. The guards around the dynamic skill discovery path therefore stayed live. The underlying source file src/skills/mcpSkills.ts is not mirrored into the open tree, so the bundler fell back to its generic missing-module stub — which only exports `default` for require()-style imports, not the named `fetchMcpSkillsForClient` binding. At runtime the require returned an object without that property, and calling it threw. `openclaude mcp doctor` reported RepoPrompt as healthy because doctor does not exercise the skills-fetch path. Fix: flip MCP_SKILLS to false and move it into the "Disabled: missing source" group. With the flag off, every `if (feature('MCP_SKILLS'))` guard becomes a no-op at build time, the require() branch is dead code, and MCP servers with resources load normally via the existing `Promise.resolve([])` fallbacks already present at each call site. Also adds scripts/feature-flags-source-guard.test.ts to fail fast if MCP_SKILLS (or any future flag in the same category) is re-enabled without the corresponding source file being mirrored first. Verification: - Test fails on main, passes with this fix - `bun run build` produces a bundle with no `missing-module-stub:../../skills/mcpSkills.js` reference - Full `bun test` — 1222 pass / 12 fail (same pre-existing 12 as main; new test adds the +1 pass)	2026-04-24 11:35:59 +08:00
KRATOSandGitHub	a4c6757023	fix(shell): recover when CWD path was replaced by a non-directory (#871) ... * fix(shell): recover when CWD path was replaced by a non-directory Closes #844. When the session's cached working directory is renamed on disk and a file is subsequently created at the old path (e.g. `mv orig renamed && touch orig`), every Bash tool invocation failed with `ENOTDIR: not a directory, posix_spawn '/usr/bin/zsh'` (exit 126), and `!`-prefixed commands silently failed. No recovery was possible without restarting the session. Root cause: the pre-spawn guard in `src/utils/Shell.ts:exec()` used `realpath(cwd)` to detect a missing CWD. `realpath()` succeeds on any existing path — file or directory — so a path that was replaced with a regular file slipped past the check. spawn() was then called with `cwd` pointing at a non-directory and failed with ENOTDIR. Fix: replace `realpath()` with `stat().isDirectory()` for both the primary CWD check and the `getOriginalCwd()` fallback check. When the cached CWD is no longer a directory, fall back to the original CWD (as before) and update state so subsequent tools recover transparently. Verification: - Repro: `mkdir -p /tmp/x/orig && mv /tmp/x/orig /tmp/x/renamed && touch /tmp/x/orig`, then exec with stale cwd=/tmp/x/orig - Before: exit 126, stderr "ENOTDIR: not a directory, posix_spawn" - After: exit 0, cwd transparently recovered to originalCwd - `bun test` — no new regressions (pre-existing model/provider test failures are unrelated and present on main) * fix(shell): drop now-unused realpath import	2026-04-24 11:34:08 +08:00
KRATOSandGitHub	6e58b81937	fix(update): show real package version and give actionable guidance (#870) ... The `openclaude update` / `openclaude upgrade` command printed `Current version: 99.0.0` and, in the development-build branch, exited with only `Warning: Cannot update development build` (closes #852). Root cause: `MACRO.VERSION` is hardcoded to `'99.0.0'` in `scripts/build.ts` as an internal compatibility sentinel so OpenClaude passes upstream minimum-version guards. The real package version is exposed separately as `MACRO.DISPLAY_VERSION`. `update.ts` was using `MACRO.VERSION` for both the version shown to the user and for every `latestVersion` comparison, which meant: - Users always saw `99.0.0` as their "current version". - `99.0.0 >= <any real npm version>`, so the "up to date" and "update available" checks could never fire correctly. Fix (scoped to `src/cli/update.ts`): - Use `MACRO.DISPLAY_VERSION` for all user-facing version strings and version comparisons. - Replace the dead-end `Warning: Cannot update development build` (which exited 1 with no guidance) with actionable instructions for both source builds (`git pull && bun install && bun run build`) and npm installs (`npm install -g @gitlawb/openclaude@latest`). - Extend the existing third-party-provider branch to also show the current version and the npm reinstall command, so users who installed via npm aren't told only to rebuild from source.	2026-04-24 11:33:03 +08:00
0xfandomandGitHub	e346b8d5ec	fix(startup): url authoritative over model name in banner provider detect (#864) ... The banner provider branch tested model-name substrings (`/deepseek/`, `/kimi/`, `/mistral/`, `/llama/`) before aggregator base-URL substrings (`/openrouter/`, `/together/`, `/groq/`, `/azure/`). When running OpenRouter/Together/Groq with vendor-prefixed model IDs (e.g. `deepseek/deepseek-chat`, `moonshotai/kimi-k2`, `deepseek-r1-distill-llama-70b`), the banner mislabelled the provider. Reorder: explicit env flags (NVIDIA_NIM, MINIMAX_API_KEY) and codex transport win first; base-URL host checks run before rawModel fallback; rawModel only fires when the base URL is generic/custom. Add unit tests covering the aggregator × vendor-prefixed-model matrix plus direct-vendor regressions. Closes #855	2026-04-24 01:52:27 +08:00
3 people	b750e9e97d	fix: make OpenAI fallback context window configurable + support external model lookup (#861) ... * fix: make OpenAI fallback context window configurable and support external lookup table Unknown OpenAI-compatible models fell back to a hardcoded 128k constant, causing auto-compact to fire prematurely on models with larger windows (issue #635 follow-up). Two escape hatches are added without touching the built-in table: - CLAUDE_CODE_OPENAI_FALLBACK_CONTEXT_WINDOW (number): overrides the 128k default for all unknown models. - CLAUDE_CODE_OPENAI_CONTEXT_WINDOWS (JSON object): per-model overrides that take precedence over the built-in OPENAI_CONTEXT_WINDOWS table; supports the same provider-qualified and prefix-matching lookup as the built-in path. - CLAUDE_CODE_OPENAI_MAX_OUTPUT_TOKENS (JSON object): same pattern for output token limits. This lets operators deploy new or private models without patching openaiContextWindows.ts on every model release. * docs: add new OpenAI context window env vars to .env.example Document CLAUDE_CODE_OPENAI_FALLBACK_CONTEXT_WINDOW, CLAUDE_CODE_OPENAI_CONTEXT_WINDOWS, and CLAUDE_CODE_OPENAI_MAX_OUTPUT_TOKENS with usage examples. Addresses reviewer feedback on PR #861. --------- Co-authored-by: opencode <dev@example.com>	2026-04-24 00:34:08 +08:00
0xfandomandGitHub	28de94df5d	feat: add OPENCLAUDE_DISABLE_TOOL_REMINDERS env var to suppress hidden tool-output reminders (#837) ... Gates three injection sites behind OPENCLAUDE_DISABLE_TOOL_REMINDERS: - FileReadTool cyber-risk mitigation reminder (appended to every Read result when the model is not in MITIGATION_EXEMPT_MODELS) - todo_reminder attachment for TodoWrite usage - task_reminder attachment for TaskCreate/TaskUpdate usage All three reminders are model-only side-channel instructions the user cannot see today. Users who want full transparency over what the model receives can now opt out without patching dist/cli.mjs on every upgrade. Default behavior is unchanged when the flag is unset. Closes #809	2026-04-23 01:37:02 +08:00
0xfandomandGitHub	23e8cfbd5b	fix(test): add missing teammate exports to hookChains integration mock (#840) ... mock.module('./teammate.js', ...) only declared getAgentName/getTeamName/ getTeammateColor. Bun applies module mocks process-globally and mock.restore() does not undo them, so whenever another test file ran after hookChains.integration.test.ts and reached the real teammate module it received undefined for isTeammate/isPlanModeRequired/ getAgentId/getParentSessionId. This surfaced in CI as intermittent failures in src/commands/provider/provider.test.tsx (TextEntryDialog / wizard remount / ProviderWizard hides Codex OAuth), because getDefaultAppState in AppStateStore.ts calls teammateUtils.isTeammate(). Match the mock surface to the real teammate.ts exports so downstream consumers keep working even after the integration test pollutes the module cache. Keeps the same behavioral overrides this test needed. Closes #839	2026-04-23 01:36:42 +08:00
3 people	531e3f1059	feat(tools): resilient web search and fetch across all providers (#836) ... - Add exponential backoff retry to DuckDuckGo adapter (3 attempts with jitter) to handle transient rate-limiting and connection errors. - Add native fetch() fallback in WebFetch when axios hangs with custom DNS lookup in bundled contexts. - Prevent broken native-path fallback for web search on OpenAI shim providers (minimax, moonshot, nvidia-nim, etc.) that do not support Anthropic's web_search_20250305 tool. - Cherry-pick existing fixes: - a48bd56: cover codex/minimax/nvidia-nim in getSmallFastModel() - 31f0b68: 45s budget + raw-markdown fallback for secondary model - 446c1e8: sparse Codex /responses payload parsing - ae3f0b2: echo reasoning_content on assistant tool-call messages - Fix domainCheck.test.ts mock modules to include isFirstPartyAnthropicBaseUrl and isGithubNativeAnthropicMode exports. Co-authored-by: OpenClaude <openclaude@gitlawb.com>	2026-04-23 01:14:00 +08:00