AssetStore概要 优惠信息 beta

- 实时检查资源价格变化 -

Sidekick brings the Claude Code CLI into the Unity Editor, with streaming chat, context, and safe edits.Sidekick is a tool that embeds the Claude Code CLI workflow directly in Unity. Chat with it while staying in your project context, attach assets and scene details, and review/approve file edits from a UI designed for development work.What you can do- Chat inside Unity with streaming responses and rich Markdown rendering.- Keep using your existing CC setup: Sidekick validates and runs your local `claude` CLI and reads conversation history from the CLI’s native storage.- Attach context fastAdd project files as context (smart text/binary detection + truncation for large files).Attach the current selection (GameObjects or assets) with hierarchy + component metadata.Capture Scene View / Game View screenshots and send them as context.Paste images from clipboard or drag & drop them into the chat.- Use slash commands like VS CodeBuilt-in command palette for common actions (attach context, screenshots, open settings, new chat, model selection).Auto-discovers CLI slash commands and lets you insert/execute them from the palette.- Safe editing workflowPermission UI for edit/write/command tools (Allow / Deny / Allow & Remember).Three permission modes: Ask before edits, Plan mode, or Edit automatically.- Quality-of-life featuresModel picker (Sonnet/Opus/Haiku + custom model ID).Optional Extended ThinkingAutomatic or manual AssetDatabase.Refresh() after assistant edits.Domain reload auto-resume for interrupted turns after Unity recompiles.Optional: MCP for Unity integrationIf you use MCP for Unity plugin, Sidekick can generate/pass an MCP config to Claude Code, enabling deeper “tool-like” workflows that can interact with the editor more directly (see Sidekick Project Settings → MCP).Quick startInstall the package.Open Window → Sidekick.Go to Project Settings → Sidekick and click Validate CLI (or set a custom CLI path).Log in (Claude.ai subscription, Console API key, or a supported third-party provider).Start chatting, and use Add Context (files/selection/screenshots) for better results.RequirementsUnity 6.0+ (6000.x).Claude Code CLI installed and accessible (by default via `claude` on PATH).Internet access for the Claude CLI to authenticate and run requests.Third-party noticesAsset uses Markdig under BSD-2-Clause and Roboto Mono under SIL OFL 1.1; see Third-Party Notices.txt file in package for details.Key features (high level)Unity Editor window: Window → SidekickProject settings: Project Settings → Sidekick (CLI path, working directory, model, thinking, permissions, MCP, refresh modes)Conversation history: read-only sync from `~/.claude/projects/…`Attachments:Images via clipboard, drag & drop, file path/URL, Scene/Game view screenshotsContext attachments for project files and GameObjects (hierarchy + components), serialized as XML for CLI contextPermission workflow:Modal permission overlay with previews (diff/content/commands)"Allow & Remember” to auto-accept a tool for the sessionPermission modes: `default`, `plan`, `bypassPermissions`Diff & review:Tracks edit/write tool activity per tool callShows per-file diff with revert capabilityAsset refresh automation:Refresh modes: Off / After assistant completes / After edit+write tools / ManualOptional MCP integration:Generates/passes an MCP config file to the CLIOptional local bridge (experimental)Supported platformsUnity Editor on macOS, Windows and LinuxAuthentication & credentialsSupports Claude.ai OAuth, Console/API key, and third‑party providers (via environment configuration)Dependencies`com.unity.nuget.newtonsoft-json` (JSON parsing)Markdig (Markdown parsing/rendering, included under `ThirdParty/`)Roboto Mono (font assets, included under `Assets/`)How AI/ML was used in creationThis package was built as an integration layer for the Claude Code CLIAI/ML tools were used extensively during development, primarily Cursor assistant along with Codex. Roughly half of the codebase (including significant parts of the UI Toolkit layout and styling) was drafted with AI assistance, then iterated and integrated by the authors.What AI/ML helped createUI Toolkit layout and styling drafts (UXML/USS) and UI copyC# editor tooling scaffolding and refactoring proposalsCandidate implementations for small utilities and edge-case handlingWhat the authors didDesigned the feature set and UX, selected architectures, and integrated all changes into the projectReviewed and edited AI-generated output for correctness, security, and Unity editor constraintsTested behavior in Unity and fixed issues found during manual testing and EditMode tests