@drael/code 0.1.0 → 0.2.0

package/README.md

@@ -0,0 +1,84 @@
+# @drael/code
+
+Points a coding client at [Drael](https://drael.sh). One command, and it asks before it
+writes.
+
+```sh
+npx @drael/code
+```
+
+It asks for your key and which client, and nothing else. Both can be flags instead:
+
+```sh
+npx @drael/code --key dk-YOUR-KEY --client kilo
+```
+
+## What it configures
+
+| Client     | File                          |
+| ---------- | ----------------------------- |
+| `opencode` | `~/.config/opencode/opencode.json` |
+| `kilo`     | `~/.config/kilo/kilo.jsonc`   |
+| `env`      | `~/.config/drael/env.sh`, for anything reading `OPENAI_BASE_URL` |
+
+All three are written `0600`, because a file holding an API key is not a file other
+accounts on the machine should read.
+
+The `kilo` file is **merged** rather than replaced: it is the whole extension's
+configuration and not ours, so the other providers and everything else in it are kept.
+
+## Undoing it
+
+```sh
+npx @drael/code --uninstall
+```
+
+Every file is copied before it is written, under `~/.local/state/drael/installer`.
+Uninstall puts the originals back byte for byte and removes the files that did not exist
+before. Installing twice keeps the **first** copy, so what an uninstall restores is the
+state before this ever touched the file.
+
+`--dry-run` prints exactly what would be written and changes nothing, including the copy.
+
+## The flags
+
+| Flag          | What it does                                                     |
+| ------------- | ---------------------------------------------------------------- |
+| `--key`       | The API key. Falls back to `DRAEL_KEY`, then to a prompt.         |
+| `--client`    | `opencode`, `kilo` or `env`. Without it you are asked.            |
+| `--host`      | For a local build or your own box. Defaults to `https://drael.sh`. |
+| `--list`      | Prints what it knows how to configure, and exits.                |
+| `--dry-run`   | Prints what would be written, and changes nothing.               |
+| `--uninstall` | Restores every file it changed, and exits.                       |
+
+## Why npx rather than `curl | sh`
+
+Piping a URL into a shell is exactly the pattern this product's own users are right to
+refuse. npx is already on the machine of anybody running an editor extension, and it
+makes Windows work without a second implementation to keep in step.
+
+It makes one network call: `GET /v1/models` against the host it is configuring, to write
+the id that host actually serves rather than one assumed here. A host that does not
+answer is no reason to refuse to configure anything, so the published id stands in.
+
+That call is not a check. The last thing it prints is the `curl` that verifies the host
+and the key, for you to run yourself.
+
+The source is one file with one dependency, and it is short enough to read in a sitting.
+The people most right to distrust an opaque installer are this product's own users, so it
+earns the trust by being readable rather than by asking.
+
+## Doing it by hand
+
+There is nothing privileged in what it writes. Any OpenAI-compatible client takes the
+same two values directly:
+
+```sh
+export OPENAI_BASE_URL="https://drael.sh/v1"
+export OPENAI_API_KEY="dk-YOUR-KEY"
+```
+
+The model id is `drael-v1`, and `GET /v1/models` is where it comes from. Full documentation at
+[drael.sh/docs/install](https://drael.sh/docs/install).
+
+MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drael/code",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Point your coding client at Drael.",
   "type": "module",
   "bin": {
@@ -10,7 +10,8 @@
     "src"
   ],
   "scripts": {
-    "ci": "node --check src/code.js"
+    "ci": "node --check src/code.js && node --test \"test/*.test.js\"",
+    "test": "node --test \"test/*.test.js\""
   },
   "engines": {
     "node": ">=20"
@@ -21,5 +22,15 @@
   },
   "dependencies": {
     "@clack/core": "^1.0.0"
-  }
+  },
+  "homepage": "https://drael.sh/docs/install",
+  "keywords": [
+    "drael",
+    "openai-compatible",
+    "installer",
+    "cli",
+    "opencode",
+    "kilo-code",
+    "llm"
+  ]
 }

package/src/code.js

@@ -63,6 +63,12 @@ const KILO_CONFIG = join(homedir(), '.config', 'kilo', 'kilo.jsonc')
 // it. Asking for the address was the installer failing to know its own address.
 const DRAEL = 'https://drael.sh'
 
+// The id the backend publishes today (`chat/transport.ModelID`), and a test holds the
+// two together. It is the fallback rather than the answer: what goes into the file is
+// what the host says it serves, so a version bump on the box reaches a config written
+// months earlier without anybody editing this.
+const MODEL = 'drael-v1'
+
 /* ──────────────────────────────────────────────────────────────────  the clients  ── */
 
 /**
@@ -76,7 +82,7 @@ const clients = {
   opencode: {
     label: 'OpenCode',
     file: () => join(CONFIG_HOME, 'opencode', 'opencode.json'),
-    contents: (host, key) =>
+    contents: (host, key, model) =>
       json({
         $schema: 'https://opencode.ai/config.json',
         provider: {
@@ -84,10 +90,10 @@ const clients = {
             npm: '@ai-sdk/openai-compatible',
             name: 'Drael',
             options: { baseURL: `${host}/v1`, apiKey: key },
-            models: { drael: { name: 'Drael' } },
+            models: { [model]: { name: 'Drael' } },
           },
         },
-        model: 'drael/drael',
+        model: `drael/${model}`,
       }),
   },
 
@@ -95,7 +101,7 @@ const clients = {
     label: 'Kilo Code',
     merges: true,
     file: () => KILO_CONFIG,
-    contents: (host, key) => {
+    contents: (host, key, model) => {
       const existing = readJson(KILO_CONFIG)
       return json({
         ...existing,
@@ -104,10 +110,10 @@ const clients = {
           ...existing.provider,
           drael: {
             options: { baseURL: `${host}/v1`, apiKey: key },
-            models: { drael: { name: 'Drael' } },
+            models: { [model]: { name: 'Drael' } },
           },
         },
-        model: 'drael/drael',
+        model: `drael/${model}`,
       })
     },
   },
@@ -268,6 +274,25 @@ const askClient = () =>
     }),
   )
 
+/**
+ * What the host says it serves, which is the same question `/v1/models` answers for the
+ * product itself. The one call this makes, and the only one: it is to the host being
+ * configured, with the key being configured, and a host that does not answer is not a
+ * reason to refuse to write anything, so the published id stands in.
+ */
+async function servedModel(host, key) {
+  try {
+    const response = await fetch(`${host}/v1/models`, {
+      headers: { Authorization: `Bearer ${key}` },
+      signal: AbortSignal.timeout(4000),
+    })
+    const served = (await response.json())?.data?.[0]?.id
+    return typeof served === 'string' && served ? served : MODEL
+  } catch {
+    return MODEL
+  }
+}
+
 /**
  * Whether the client's own directory is on this machine. It is a hint and never a gate:
  * a fresh install may not have written its directory yet, so every client stays on the
@@ -303,7 +328,7 @@ async function install(args) {
   }
 
   const file = client.file()
-  const contents = client.contents(host, key)
+  const contents = client.contents(host, key, await servedModel(host, key))
 
   // An answered prompt leaves its frame on screen and needs a gap after it. With every
   // answer given as a flag there was no frame, and the masthead's own gap is already it.
@@ -321,13 +346,16 @@ async function install(args) {
     return
   }
 
+  // Asked before the write, or it inspects the valid JSON we are about to put there.
+  const replaced = client.merges && !parses(file)
+
   const kept = backup(file)
   mkdirSync(dirname(file), { recursive: true })
   writeFileSync(file, contents, { mode: 0o600 })
   chmodSync(file, 0o600)
 
   console.log(row(client.merges ? 'merged' : 'wrote', tilde(file)))
-  if (client.merges && !parses(file)) {
+  if (replaced) {
     console.log(under(dim('it was not plain JSON, so it was replaced rather than merged')))
   }
   console.log(row(kept.label, dim(kept.detail)))