The fixed Export Settings file stores Git and local-folder destinations for generated frontend, assets, and optional backend output.
Property: Path · Current behavior: settings/export
Property: Target kinds · Current behavior: Git and Local Folder
Property: Output fields · Current behavior: React source, assets, optional Node.js backend
Property: MCP · Current behavior: get/add/update/remove target; run all local targets
Property: Addressing · Current behavior: current zero-based index; targets have no stable item ID
Property: Security · Current behavior: Git token is secret-bearing project content
Local targets store description and absolute frontend/asset/backend directories. Git targets additionally store repository URL, email, username, token, and a branch label; their output paths are relative to the checkout. A blank/whitespace backend path disables backend output.
The stored path/asset keys correspond to visible React src path and Asset path labels.
Read targets immediately before an index-based mutation. export-code-to-folder writes the complete project to every configured Local Folder target and does not push Git targets. One destination can succeed while another fails.
Current get-export output includes the Git token. Ask for redacted summaries, never place raw output in documentation/transcripts, and rotate any exposed credential.
Configuration edits persist/synchronize and use the file's transaction model. Running export writes external files and can replace hand edits in generated paths; file undo does not restore the destination. Snapshot and diff it.
Current Git branch handling and push behavior have documented limits; use Configure local and Git targets.