CarterIDE
CarterIDE setup: build your first tweak on iPhone
Follow this CarterIDE setup guide to check Doctor, connect a model, review edits, and build on your iPhone, with verified iOS support and known limits.
CarterIDE setup starts with Doctor: get the required toolchain checks green before asking the Coding Agent to change a project. Then connect your model, make a small edit, review it, and build on the phone before moving on to installation.
CarterIDE setup starts with the toolchain
CarterIDE is our on-device IDE for Dopamine rootless. It combines project workspaces, an editor, a file tree, a terminal, build output, and a Coding Agent.
Install it from the CarterWare source, https://tweaks.carterware.net/, using Sileo or Zebra. CarterIDE costs $0.99 as a one-time purchase and is also covered by an active Tweak Pass.
Open CarterIDE and run Doctor until the required rows are green. Doctor checks the on-device Theos toolchain, including clang, make, ldid, and the project directory. It also checks gzip, which Theos needs for packaging.
Use Doctor's repair controls when a required component is missing. A model connection does not replace a working compiler or packaging tool, so keep those checks separate from agent setup.
If the supporting carterd service is down, installation and respring actions can stall. Resolve an unhealthy Doctor result before treating that stall as a problem with the tweak you are writing.
For a first attempt, choose a tiny change such as renaming a string. That lets you check the edit, build, and installation sequence without combining it with a large new feature.
Connect the model you want to use
Open Tools → Settings → Coding Agent in CarterIDE. Choose a Provider, enter its key where required, and use Test connection.
Version 1.4.0 added provider selection for Ollama Cloud, Ollama on your computer, Claude through its native API, OpenAI, OpenRouter, Groq, Gemini, Grok, and other OpenAI-compatible servers.
The same release added Fetch models, which lists models available to your key and marks tool and vision capabilities. Each provider keeps its own key in the Keychain, so switching providers does not mean treating every service as one shared credential.
Doctor's network check now checks the selected provider instead of always checking OpenAI. That makes the result relevant to the service you actually configured.
You supply the model and any required API key; the CarterIDE purchase does not include a model subscription.
If you are not using an agent for the first build, the setup flow also offers Offline Recipes. Keep the immediate goal simple: establish that you can open a project and build it before adding more moving parts.
Choose Ask, Edit, or Agent deliberately
The Coding Agent has three modes with different levels of involvement in your project:
- Ask is read-only.
- Edit proposes diffs for you to approve individually.
- Agent saves a checkpoint, writes and builds, and lists changes for you to keep or revert.
Start with Ask when you want an explanation before changing anything. For the first modification, use Edit so you can inspect the proposed difference and compare it with your request.
CarterIDE warns if a file changed after the agent read it. Take that warning seriously when you have also been editing the file yourself; the proposed diff needs to be checked against the work currently in the project.
Agent mode is useful when you want a broader write-and-build loop, but the checkpoint and change list still matter. Review what changed before deciding to keep it.
Since 1.3.0, Agent mode asks before running shell commands, with Run, Allow All This Run, and Deny choices. Safe build commands such as make and git status run without asking, and the behavior has a Settings toggle.
A successful agent response is not proof that the resulting tweak behaves as intended. You still need to review the change and test the result.
Build, inspect the output, then install
The basic project flow is New Project → edit → Build → Install. Start with a project or recipe, make your small change, and inspect the build output.
Build output streams live, and you can stop a build. The build can report substantial error output without leaving you waiting on a frozen view.
CarterIDE 1.2.7 changed installation to use only the package produced by that project's current build. The combined Build · Install · Respring sequence stops when the build fails, rather than carrying on with an unrelated package.
That distinction is useful during troubleshooting. If compilation fails, work from the build error before retrying installation. If the package builds and installs but the behavior is wrong, describe that as a separate result.
On-device arm64e builds include the Objective-C metadata signing needed for iOS 17. Version 1.2.8 fixed the earlier problem where phone-built tweaks could crash on iOS 17, including SpringBoard tweaks that entered Safe Mode.
Builds run locally when the toolchain is ready. A remote build fallback is used only when a configured remote Mac is actually reachable.
Use the terminal and logs for specific problems
CarterIDE's terminal runs in the project folder and supports colors, vi, less, Ctrl+C, and a key row. It survives closing the terminal sheet and follows project switches.
Use it when you need to inspect or work in the current project directly. Check which project is active before entering a command, especially if you have been switching between several workspaces.
For runtime investigation, Inspect → Logs shows device logs for a selected process. Inspect also provides views for processes, tweaks, and crash logs.
Keep a useful distinction in your notes: build output explains what happened during the build, while process logs help investigate what happened when the software ran. Send the evidence from the stage that actually failed.
We verified New Project / Recipe → Build → Install → Respring, the agent edit-review-keep/revert loop, and the terminal on iPhone 15 Pro Max with iOS 17.1 and Dopamine. iOS 15–16 has not been re-tested for this release, and Swift/Orion tweaks built on the phone remain untested.
To report a CarterIDE problem, open Settings → CarterIDE → Report a Bug. The report fills in the tweak version, iOS version, and iPhone model. Explain the Doctor result, the stage that failed, and the error you received; the website's Report a bug form is another route.
FAQ
Does CarterIDE include the AI model?
No. You choose the provider and supply any required key. Model access is separate from the $0.99 CarterIDE purchase.
Can I review changes before accepting them?
Yes. Edit mode presents diffs for individual approval. Agent mode saves a checkpoint and lists applied changes with Keep or Revert controls.
Should I install again if the build fails?
Fix the build error first. The combined build, install, and respring sequence stops on a failed build, and installation uses the package from the current project's build.
Open CarterIDE, get Doctor's required checks green, and try one small edit before requesting a full tweak. Review the diff, read the build result, and move to installation only after that first change builds successfully.