Kontext Encyclopedia

KTX Code

/ktx-code · version 3.13 · 2026-10-06

Capabilities

KTX Code (/ktx-code) is the coding app on your computer. The headline is Agents you can trust on your machine. Ask, Plan, and Agent share one feed, with a real editor and terminal. Finish gates hold the line: plan coverage, a verify command, a model review, and your OK before a push or a deploy. It is not the Watch and Drive helper.

The desktop download is included with Pro and above (team and admins included). First installers are unsigned: on a Mac, right-click and Open; on Windows, More info, then Run anyway. Later updates ship inside the app. On a Mac, keep the launcher window open. Closing it quits the app.

Your Kontext, on the laptop. Sign in once. Keys and projects sync from the account. Connector in the status bar can let kontext.network Watch this screen and Drive from your phone. That stays off until you allow it. The connection is outbound only.

Built for the Internet Computer. Typed deploy tooling, Motoko-aware editing, and a finish that needs deploy proof.

What is KTX Code?

KTX Code is the coding app that runs on your computer — Ask, Plan, Agent, a real editor and terminal, and finish gates. You can link it as a computer that can act as you (keys, writes in your name). Keep the launcher window open on a Mac. Closing it quits the app.

Link and cut off

Pair at /ktx-code/connect with the platform chooser. Keep the Mac Terminal launcher tab open — closing it quits Code. Local desk: http://127.0.0.1:4517. A forever “Generating a link code…” usually means no workspace canister yet. Cut off by revoking the ktx_ key under Profile → API keys.

Not the Watch and Drive helper

KTX Connector is the small helper that can see the screen and move the mouse. KTX Code can start that helper. They are not the same product. If you asked Kontext to click something on the desktop, you need Connector with sharing on — not the coding app alone.

KTX Code (/ktx-code) is the local coding-agent IDE — files, terminal, models, and a bridge to your Kontext projects. Link it as a computer that can act as you. It is not KTX Connector (Watch / Drive).

User journeys

KTX-01. Open the KTX Code product page

Path: Module switcher → KTX Code · /ktx-code

You do:

  1. Sign in with the Kontext chooser (Google, Microsoft, Apple, passkey, Kontext ID, or recovery).
  2. Open KTX Code from the module switcher or go to /ktx-code.
  3. Read Ask, Plan, Agent and the finish gates. On a Mac, keep the Terminal tab that launched it open. The first installer is unsigned.
  4. Confirm this page is about the coding app, not Watch / Drive (that is KTX Connector). Sharing on Code stays off until you allow it.

Result: You know how to install and open the local coding cockpit. It binds to this computer only.

KTX-02. Link KTX Code as a computer that can act as you

Path: /ktx-code/connect · Hub → Access · KTX Code desktop

You do:

  1. Open KTX Code on your computer and start the link flow.
  2. In the browser, open /ktx-code/connect and sign in with the chooser if asked.
  3. Wait — the page usually sends the code to KTX Code on this computer by itself. Paste only if it asks you to.
  4. Keep the desktop window open. On a Mac, keep the Terminal tab that launched it open.
  5. Open Hub → Access and confirm this computer is listed among who can act as you.

Result: KTX Code acts as your computer — it can sync keys and write as you. To cut it off, revoke its personal key. This is not a Marketplace app grant.

KTX-03. Tell KTX Code from KTX Connector

Path: /ktx-code vs /ktx-connector

You do:

  1. Open KTX Code if you want a local coding-agent IDE (files, terminal, models, Kontext projects).
  2. Open KTX Connector if you want Kontext or a cloud agent to Watch or Drive this computer.
  3. Either can share the machine when that helper is online — name whichever is actually running.
  4. Do not look for Watch / Drive controls inside the coding app.

Result: You pick the right product. Coding stays in KTX Code; screen sharing stays in KTX Connector.

KTX-04. Build Kontext from an iPad or the cloud desk (team only)

Path: iPad app KTX Code · https://code.kontext.network · /ktx-code (team block) · GitHub coinnation/kontext · /api/ipad/* · droplet runner /root/workspaces/kontext

You do:

  1. Sign in with the Kontext chooser (not Internet Identity login()). If you are not admin or team, you stop on a plain wall. Founding and Pro are not enough.
  2. Open code.kontext.network in a browser, or KTX Code on the iPad. Connect so the desk has your ktx_ key.
  3. Optional: paste a GitHub token (banner) to edit src/kontext_frontend, docs, and project-generation and push main even if the runner is off.
  4. When the runner is up, Ask / Plan / Agent run on the droplet checkout — not in the browser tab, not on the iPad, not inside Zoe’s container, not in /root/kontext.
  5. Approve anything irreversible. Pull so the desk matches GitHub.
  6. Tap be check or Ship fe on the banner. That is the existing ktx path on the factory tree. If a ship is already running, the desk says so.
  7. Someone who is not on the team gets 403 on the job API even if they have the URL.

Result: The team can change and ship Kontext from an iPad or the cloud desk. Customers cannot. The Mac does not need to be awake. This is not Watch / Drive, and it is not a public IDE.

How it works

Route /ktx-code. Product page + connect flow for the local KTX Code cockpit (ktx-code desktop). Local UI binds 127.0.0.1; optional outbound-only connector for cloud→machine jobs. Releases via ktx release ktx-code.

Benefits

Who it's for

Primary: developers building on or with Kontext locally. Not: pure no-code Business operators.