Image understanding
Choose the dedicated DeepSeek Vision Responses model or a custom OpenAI-compatible endpoint. Image detail, credential state, limits, usage, and privacy remain explicit.
Tools and capabilities
Tooling is part of the runtime, not an afterthought.
CodeSeeX exposes a bounded set of hosted tools, preserves Codex-native client tools, and keeps community tools behind explicit local trust boundaries.
Image understanding and generation
Image understanding and generation
Separate DeepSeek Vision or custom image understanding, plus an independent image generation endpoint.
Image generation
Enable image_gen separately with its own endpoint, model, and credential. Selecting DeepSeek Vision never changes the generation provider.
Usage and privacy
Vision usage is a separate session phase. Default logs keep counts and normalized usage, not original images, base64, API keys, full prompts, or full provider responses.
Web Search
Choose CodeSeeX web scraping or the official DeepSeek Search/Fetch API. Both are CodeSeeX-hosted and return bounded evidence to the model.
Workspace inspection
Read-only file and repository inspection tools support large-codebase reasoning without turning every operation into a shell script.
Native Apply Patch
Patch application is handed back to Codex in the expected client-tool shape, with repeated failure diagnostics instead of silent loops.
Image understanding and generation
Separate DeepSeek Vision or custom image understanding, plus an independent image generation endpoint.
Community tools
Local command manifests under ~/.codeseex/extension/tools are disabled by default and require explicit trust.
Tool safety boundaries
Diagnostics store summaries and hashes where possible, not raw prompts, image data, or full tool output.
Tool safety boundaries
Tool safety boundaries
Tool access is useful only when the runtime can keep it bounded, observable, and scoped.
- Tool output is compacted before replay to reduce token pollution.
- Web opening rejects local, private, link-local, and non-global targets.
- Community tools execute as child processes declared by manifests you choose to trust.
- Diagnostics store summaries and hashes where possible, not raw prompts, image data, or full tool output.
Community tools
Local command manifests under ~/.codeseex/extension/tools are disabled by default and require explicit trust.