CodeFlicker is an AI-powered code editor that understands your codebase through natural language, helping you achieve code understanding, code generation, bug fixing, and requirement implementation. It helps developers improve coding efficiency and deliver code more effectively.
CodeFlicker is coming soon. Visit the waitlist page to join and get early access.
Autonomous AI coding assistant designed for complex development tasks, featuring autonomous decision-making, environmental awareness, and tool usage capabilities.
Human-AI deep collaboration development mode designed for complex tasks, emphasizing early consensus building and systematic technical design.
Intelligent assistance designed to accelerate coding, providing line-level or function-level code suggestions.
Standardized protocol designed for AI tool integration, allowing LLMs to access custom tools and services.
Extension management features in CodeFlicker
Check our latest updates
Provide us your feedback
Agent chat is divided into multiple modes based on different usage scenarios, each with independent optimization and different available features. You can switch modes via the dropdown near the input box or using the shortcut key (⌘.).
This is the default mode, recommended for complex task scenarios. AI can perform complex logical understanding and implement specific code logic.
Ask mode is a read-only mode that answers user questions by searching the codebase, but does not perform any write operations. Additionally, Ask mode has faster overall response times, making it more suitable for lightweight scenarios like Q&A or understanding.
Autonomous coding agent from idea to release, with deep understanding of your codebase. The agent features autonomous decision-making, environmental awareness, and tool usage capabilities. It can complete coding tasks end-to-end using tools like engineering search, file editing, and terminal based on developer coding needs.
By default, currently open files are automatically filled as content.
Supports using shortcut key ⌘L to add selected code blocks, or quickly add selected areas to the agent via right-click menu.
When copying and pasting multi-line code into the input box, it automatically recognizes and displays in "file + line number" format in the context area.
After the agent completes code generation, it supports automatic checking of incremental lint errors in modified files and provides one-click fix capability.
You can enable or disable lint self-checking and fixing in Settings > Enable Automatic Lint Issue Detection.
During coding, engineers can receive line-level or function-level suggestions from CodeFlicker in the editor.
Duet (/duˈet/) mode is a human-AI deep collaboration development mode designed for complex tasks. It mimics the natural behavior of human expert teams solving complex requirements, emphasizing early consensus building through deep discussion, analysis, and research based on requirements, formulating systematic technical design plans, then executing through division of labor.
Generate coarse-grained research outline plan based on user original input, clarifying goals and boundaries through questions.
Use deep search and tool calling capabilities for comprehensive research, generating standardized user stories and technical design.
Autonomously plan and break down documents into executable and trackable detailed development tasks.
| Concept | Definition |
|---|---|
| Research Plan | Coarse-grained research outline plan generated based on user original input, clarifying goals and boundaries through questions. |
| User Story (requirement.md) | Structured user stories that transform user input into clear, complete, testable/acceptable, and trackable requirements. |
| Technical Design (design.md) | Overall view of complex project engineering, including system architecture, key implementations/components/modules, and sequence diagram interactions. |
| Development Tasks (To-dos) | Independent executable and trackable development tasks, each with clear description, expected results, and necessary dependency definitions. |
The IDE provides comprehensive extension management features, including installation, deactivation, and deletion operations. Extensions can be added to the IDE through multiple channels: built-in extension marketplace, VS Code official marketplace, or direct import of local .vsix packages.
Click the extension marketplace icon in the left sidebar to open the extension marketplace panel.
Browse or search for the desired extension in the available section, select the extension to view details, then click the install button.
When the desired extension is not available in the built-in marketplace, you can obtain it from the VS Code official marketplace. Need to collect the following information:
Access the extension marketplace, locate the menu button (···) in the upper right corner of the panel, select "Install from VSIX", then select the desired .vsix file.
Find the target extension in the installed section, hover over the extension entry and select Settings > Disable.
Find the extension to delete in the installed section, right-click or hover to select uninstall.
When extension versions depend on newer VS Code APIs, compatibility conflicts may occur with the IDE. Solution:
The Figma to code feature enables AI programming in agent mode to convert your input Figma designs into corresponding frontend web implementations. Compared to Figma MCP functionality, our design restoration is more accurate and clear.
Open the IDE and select a project directory.
On the Figma page, select the corresponding design node, then right-click and select Copy/Paste as > Copy link to selection.
Paste the copied URL into CodeFlicker's agent mode input, enter your requirements and send, then complete Figma authorization as prompted.
The preview feature allows the Agent to identify web project "startup scripts" and run corresponding local services. You can choose to view pages within the IDE or in a browser.
Pages opened via preview have a debug toolbar in the bottom right corner, supporting element selection and sending console errors.
Clicking target elements on the page sends corresponding DOM element information to the IDE. You can chat with the Agent directly based on the currently selected element's context, without needing to describe UI-related changes in text.
Use shortcut key (cmd+i) within the page to invoke this feature.
| Feature | React 16 | React 18 | React 19 | Vue 2 | Vue 3 |
|---|---|---|---|---|---|
| tagName | ✅ | ✅ | ✅ | ✅ | ✅ |
| class | ✅ | ✅ | ✅ | ✅ | ✅ |
| attributes | ✅ | ✅ | ✅ | ✅ | ✅ |
| path | ✅ | ✅ | ❌ | ✅ | ✅ |
| Start line number | ✅ | ✅ | ❌ | ❌ | ✅ |
| End line number | ❌ | ❌ | ❌ | ❌ | ❌ |
| style | ✅ | ✅ | ✅ | ✅ | ✅ |
CodeFlicker provides two ways to customize AI behavior: personal rules and project rules.
Open CodeFlicker Settings > Navigate to Rules Settings > Configure your rules
Rules that only take effect when explicitly added in #Knowledge-Rules
Model Context Protocol (MCP) is a protocol that allows Large Language Models (LLMs) to access custom tools and services. Agents in CodeFlicker can act as MCP clients, choosing to make requests to MCP servers to use the tools they provide. You can add MCP servers yourself and integrate them for use in custom agents.
For more details, visit: MCP Official Website
CodeFlicker supports integrating MCP servers, which can extend its capabilities by providing tools or functionality to CodeFlicker through MCP.
MCP servers are built and maintained by third parties. CodeFlicker cannot review or guarantee the validity, stability, or authenticity of data returned by these services. Use with caution. Due to relevant laws and regulations, network restrictions, or the servers' own access policies, some MCP servers may also be unavailable.
Note that some MCP servers may use commands like npx or uvx, please install related tools in advance.
After successfully adding MCP, you can view enabled MCP servers in the agent mode MCP button. CodeFlicker agent will call these MCP servers when needed.
The current agent mode does not support VS Code workspaces. If you need to use agent mode, you can try opening code repositories in single-repository mode in VS Code.
If files/folders are added through the following paths, a "workspace" definition will exist in the VS Code directory. Agent chat is currently not supported in this mode.
You can directly add folders/clone repositories in the left directory, or use Create New File/Open File/Folder under the File menu to use normally.
You can vote in the following actions, we will collect feedback and accelerate support.
We look forward to your feedback! If you have any suggestions or issues about using our products/services, you can communicate with us through the following channels.
There's a feedback button in the top right corner of CodeFlicker, clicking it will open a feedback popup.
You can also directly visit our GitHub and create a new issue to provide feedback.
Below are common issues and solutions during IDE usage.
Auto-update is typically disabled when importing settings. Manually switch to default to resolve.
This occurs when the connected workspace contains many symbolic links.
Solution: Open settings, search search.followSymlinks, set both Remote and Workspace values to False.
CodeFlicker IDE has built-in basedpyright plugin. If the issue persists, try the following solutions:
Usually caused by third-party plugin conflicts with input method.
Troubleshooting:
Change source to official Microsoft gallery in settings:
https://marketplace.visualstudio.com/_apis/public/gallery
IDE provides --crash-reporter-directory <absolute_path> option to output crash dumps.
codeflicker --crash-reporter-directory <absolute_path>