Claude Code Workbench
- Dominant language
- No language data
- Stars
- 16
- Forks
- 13
- Avg merge
- 10h 26m
- Merged PRs (30d)
- 18
Description
### π π₯π²π½πΌππΆππΌπΏπ
https://github.com/jacquesh82/FreeCAD-ClaudeCode
### π π‘πΌππ²π
Claude Code Workbench adds a dockable chat panel that lets an AI agent (Claude Code) drive FreeCAD on the user's behalf: it inspects the scene, executes FreeCAD Python in small steps, and verifies its work with screenshots of the 3D view.
Transparency about external connections (per the Index Qualities):
- The addon itself makes no network connections except to 127.0.0.1 (a local RPC bridge between the panel and the agent process).
- It launches the user's locally installed `claude` CLI (Claude Code by Anthropic), which connects to Anthropic's services using the user's own subscription login. Nothing is sent anywhere unless the user types a prompt; this is stated in the panel and in the README.
- No API keys are stored or handled by the addon; no user data is collected.
Technical notes:
- Requires FreeCAD >= 1.1; uses the FreeCAD-provided PySide (Qt6) wrappers; no sys.path manipulation.
- The MCP bridge subprocess uses only the Python standard library β no third-party dependencies.
- By default the agent is restricted to three FreeCAD tools (exec_python, get_scene, screenshot) via Claude Code's --allowedTools; broader access requires an explicit opt-in checkbox.
- Tagged release: v0.1.0. Valid package.xml manifest, MIT license (LICENSE file included), icon, README with screenshot.
External dependency (documented in the README): the user must have Claude Code installed and logged in with their own Claude subscription. The addon degrades gracefully with a clear message if the CLI is absent.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the linked FreeCAD-ClaudeCode repository, starting with its README, package.xml, LICENSE, and v0.1.0 release details. Compare the workbench with the Addons repositoryβs submission requirements; the payload does not state which Addons files should change or define acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100