CarterIDE

CarterIDE 1.4.3: DeepSeek and connection fixes

Set up CarterIDE 1.4.3 with DeepSeek, understand the HTTP and Base URL fixes, and separate provider connection problems from build-toolchain failures.

CarterIDE 1.4.3 adds DeepSeek as a built-in model provider and fixes connections to plain HTTP model servers outside your home network. It also changes how a Custom Base URL without a scheme is handled: internet addresses now default to HTTPS. If a model connection previously failed with an App Transport Security error, update before rebuilding the rest of your setup.

What changed in CarterIDE 1.4.3

CarterIDE is our on-device development environment with projects, an editor, a terminal, Theos builds, and a Coding Agent. Version 1.4.3 focuses on connecting that agent to the model you choose.

The release fixes two distinct connection problems.

First, iOS could block a plain HTTP model server outside the home network with an App Transport Security error. The error could tell you to update even when you already had the newest version. CarterIDE 1.4.3 allows those connections.

Second, a Base URL entered without either http:// or https:// now uses HTTPS for internet addresses. This fixes hosted APIs such as DeepSeek when configured through Custom.

DeepSeek also has its own provider entry now. You can choose it directly, supply your key, and fetch the models available to that key.

These are connection changes. They do not replace a working model account, a valid key, or the local tools needed to compile a tweak.

Set up the built-in DeepSeek provider

Install or update CarterIDE from the CarterWare source, https://tweaks.carterware.net/, in Sileo or Zebra. Then configure the provider inside the app.

  1. Open CarterIDE.
  2. Go to Tools → Settings → Coding Agent.
  3. Choose DeepSeek as the provider.
  4. Paste your provider key.
  5. Tap Fetch models to see the available model choices.
  6. Use Test connection to check the configured connection.

Provider selection and Fetch models were introduced in CarterIDE 1.4.0; 1.4.3 adds DeepSeek to that system. The model list marks tool and vision capabilities, helping you inspect what is available instead of guessing a model name.

Each provider keeps its own key in the Keychain. When switching providers, check that you are configuring the intended provider rather than treating every service as one shared account.

CarterIDE costs $0.99 once and is also included with an active Tweak Pass, currently $2.99/month. You supply the model and any required API key separately.

Start with a small read-only question in Ask mode after the connection test. That gives you a simple first request before introducing project edits or build failures into the same investigation.

Check the Base URL separately from the model

If you use Custom, inspect the Base URL as its own setting. The URL identifies the endpoint, while the model choice identifies what you want to use through that endpoint.

Version 1.4.3's default applies when the scheme is missing from an internet address. It does not mean every address should be changed to plain HTTP, or that a server configured for one protocol automatically supports another.

For a server on your computer, CarterIDE also offers Ollama (Mac / LAN). Use the computer's network address as the Base URL, rather than the phone's own loopback address. The server needs to accept connections from the phone; a service listening only to itself is a different problem from the iOS restriction fixed in this release.

The app's connection errors distinguish problems such as the wrong host, a server bound only to loopback, and confusing the phone's address with the computer's address.

Change one setting, then test again. If you change the provider, address, key, and model at once, a successful connection will not tell you which change mattered.

Separate a provider failure from a build failure

Doctor checks the toolchain and project environment, including clang, make, ldid, and Theos. Since version 1.4.0, its network row checks your selected provider instead of always checking OpenAI.

That distinction matters when you are diagnosing a failed session. A provider connection problem and a missing build tool can both interrupt your work, but they require different fixes.

Use the stage of failure to organize the next check:

  • If Test connection fails, record the provider and the exact error before changing project code.
  • If a model responds but the build fails, inspect the build output and Doctor's required rows.
  • If the build succeeds but installation stalls, check Doctor and the supporting service status.
  • If an agent edit is wrong, review the proposed change separately from whether the connection worked.

A model response is not proof that a generated tweak is correct. Edit mode lets you approve diffs individually, while Agent mode saves a checkpoint and lists changes you can keep or revert.

For an initial check after updating, keep the task small enough that you can explain the intended change in one sentence.

Know the verified setup and report the right details

We verified the project or recipe, build, install, and respring flow, the agent review loop, and the terminal on iPhone 15 Pro Max with iOS 17.1 and Dopamine. iOS 15–16 has not been retested for this release, and phone-built Swift/Orion tweaks remain untested.

That verification does not establish that every model behind every compatible endpoint behaves identically. Choose the provider and model around the task you need, then review the result.

For a connection bug, open Settings → CarterIDE → Report a Bug. Your tweak version, iOS version, and iPhone model are filled in.

Describe whether you used a built-in provider or Custom, whether the address had an explicit HTTP or HTTPS scheme, and whether the failure occurred during Fetch models, Test connection, or an agent request. Include the error text without including your API key.

The web report form is another way to send the same information. Keeping the report tied to one failing stage makes it easier to distinguish the fixed transport issue from an account, endpoint, or build problem.

FAQ

Do I still need Custom to use DeepSeek?

No. CarterIDE 1.4.3 adds a built-in DeepSeek provider. Select it, supply your key, and tap Fetch models.

What happens if I omit the URL scheme?

For internet addresses, CarterIDE 1.4.3 now defaults to HTTPS. Check the endpoint you intend to use rather than assuming a missing scheme is harmless.

Does updating CarterIDE include model access?

No. You bring your own model and any required API key. The CarterIDE purchase and Tweak Pass provide access to the app, not a provider subscription.

Update CarterIDE, select the intended provider, and run Test connection before asking the agent to modify a project. If it still fails, report the exact stage and error so we can investigate the connection you actually configured.

← All posts · Report a bug