Linelark Notepad Studio
What shipped in 1.18.0.
A model proxy that follows your shells
- CLIProxyAPI runs on your Mac and puts the AI accounts you have signed in to behind one local address, so Claude Code or Codex pointed at it can use a model from another provider — a GPT or Gemini model from inside Claude Code, say. It only has to be up while there is a shell to use it, so Studio now runs it for exactly that long: it starts with the first terminal in any window and stops a few seconds after the last one closes, or when you quit. The pause is so that restarting a shell does not restart the proxy with it.
- Switch it on under Preferences ▸ Terminal ▸ Model Proxy. EasyCLIProxyAPI’s install is found without typing a path, and EasyCLIProxyAPI stays where the proxy is configured — Linelark starts and stops it, nothing more. The Proxy dot in the status bar says whether it is running and starts or stops it with a click; with no proxy installed it shows no error, and a click explains what it is for and where to get it.
- It stops only what it started. A proxy already running when the first shell opens is used as it is and left running afterwards, and one left behind by a crash is recognised at the next launch by its program as well as its process number, so an unrelated process that inherited the number is never touched.
The terminal sits between the side panels
- The terminal panel ran the full width of the window, so opening a shell cut the bottom off the folder tree and the right dock. It now sits under the editor alone and the side panels keep their full height. The full-width panel is one switch away — in the titlebar next to the terminal’s own, under Terminal ▸ Terminal Between Side Panels, or in Preferences ▸ Terminal.
Known limits in 1.18.0
- The model proxy is Studio-only and yours to install: Linelark does not install CLIProxyAPI, sign you in to a provider, or point Claude Code or Codex at it — the address and key are in EasyCLIProxyAPI. Turn off EasyCLIProxyAPI’s own start-on-launch if you want the terminals to decide when it runs.
- A vault holds up to 5 MiB of encoded documents, and changing its password rewraps the same content key rather than replacing it — rotation answers a credential you no longer trust, not the key itself having escaped.
- Touch ID and Mac-password unlocking need a build signed with a provisioning profile, which the download here is; a vault still opens with its password and recovery key everywhere else.
- There is still no watchdog over a plugin’s own script: one that never returns hangs the app, because the only way to interrupt it is private API that cannot ship on the App Store.
- Code folding and recorded macros remain roadmap items with no promised date.