🌐 中文版:🇨🇳 FAQ
Version: v1.0.5 | Last Updated: 2026-05-28 | For: All Users
Answer: This means a CodeCraft instance is already running, or another program is occupying port 8084.
Solution:
- Windows: Open Command Prompt and run
netstat -ano | findstr 8084, find the PID and use Task Manager to end the process - Mac/Linux: Run
lsof -i :8084to find the PID, thenkill -9 <PID> - Return to CodeCraft and restart
Answer: The default password is 123456. If you changed the password and forgot it, you'll need to reset the database.
Solution:
- Stop CodeCraft
- Delete the
data/directory (this will clear all conversations and settings, be careful!) - Restart CodeCraft — the database will be recreated and the default account
admin/123456will be restored
Answer: Usually a CORS (Cross-Origin Resource Sharing) or port issue.
Checklist:
- Confirm backend has started successfully (terminal shows
Started AgentDeepseekApplication) - Confirm accessing
http://localhost:8084(not port 5173 unless in dev mode) - Confirm
application.ymlhas correct CORS configuration - Try clearing browser cache or using incognito mode
Answer: Providers and API Keys are managed in the「Model Config」page (stored in the llm_provider table).
Steps:
- Open
http://localhost:8084 - Go to 「Model Config」in the left menu
- Add or edit the Provider and enter the correct API Key
- Click Save — changes take effect immediately (hot refresh)
Answer: Usually caused by old version cache conflicts.
Solution:
- Close CodeCraft
- Delete the cache directory:
- Windows:
%APPDATA%\CodeCraft\Cache - macOS:
~/Library/Application Support/CodeCraft/Cache
- Windows:
- Restart the app
Answer: Possible causes include firewall blocking, network issues, or incompatible versions.
Checklist:
- Ensure both devices are on the same local network
- Check if firewall is blocking port 9527 (CodeCraft auto-registers firewall rules on startup)
- Try manually adding a firewall exception rule for port 9527
- Ensure both devices are running the same version of CodeCraft
- If QR code pairing fails, try manually entering the connection string
Answer: Possible causes include insufficient permissions, invalid file paths, or environment issues.
Checklist:
- Check if execution mode is set to "Manual" (manual mode requires confirmation for each operation)
- Check if the file path is within the project directory (path traversal is prevented)
- Check if the target file exists
- View the error message in the tool execution result card
Answer: You can create custom Agents on the Agent Management page.
Steps:
- Click "Configure" → "Agent Management" in the left menu
- Click the "New Agent" button
- Fill in Agent name, description, system prompt, tool selection, etc.
- Click Save
- The new Agent will appear in the Agent selector at the top of the chat page
Answer: Several approaches:
- Optimize prompts: Use the ✨ Optimize button to let AI rewrite ambiguous descriptions
- Use Manual Mode: Manually confirm each operation to ensure accuracy
- Create Skills: Create reusable skill templates for repetitive tasks
- Adjust Model: Try different models (Flash for speed, Pro for quality)
- Enable Thinking Mode: Deep thinking helps with complex tasks
Answer:
- Bug Reports: Go to GitHub Issues, describe the issue in detail with reproduction steps and environment info
- Feature Requests: Also submit via Issues, describe the feature and the problem it solves
- Security Vulnerabilities: Do NOT report via public Issues; contact the maintainer directly via email
💡 Not finding your answer? Check ARCHITECTURE.md and DEV_QUICKREF.md, or submit an Issue on GitHub.