2026-09-27 01:53:04 +08:00
..
2026-09-27 01:53:04 +08:00
2026-09-26 14:30:16 +08:00
2026-09-26 14:30:16 +08:00
2026-09-26 13:59:02 +08:00
2026-09-24 12:17:45 +08:00
2026-09-24 12:17:45 +08:00
2026-09-25 01:14:56 +08:00
2026-09-26 13:59:02 +08:00
2026-09-26 13:59:02 +08:00
2026-09-26 14:22:47 +08:00
2026-09-26 14:22:47 +08:00
2026-09-25 21:13:30 +08:00
2026-09-25 21:13:30 +08:00
2026-09-25 02:19:32 +08:00
2026-09-25 02:19:32 +08:00
2026-09-26 14:14:26 +08:00
2026-09-27 01:53:04 +08:00
2026-09-26 01:03:33 +08:00
2026-09-24 01:09:59 +08:00
2026-09-26 14:30:16 +08:00
2026-09-24 17:13:03 +08:00
2026-09-24 17:13:03 +08:00
rtk: an agent left with the hook of an rtk that isn't installed (never was, or removed since) is shown with RTK missing — its shell commands fail — and can still be switched off: magpie takes out just what rtk's installer put in (the hook in settings.json / hooks.json, RTK.md and the @RTK.md line, Gemini's hook script, Copilot's instructions block, the OpenCode / Pi / OMP extension, Hermes' plugin) itself, needing no rtk, the files kept aside first; rtk's own uninstaller is no longer used, which deleted Gemini's GEMINI.md whole and took Claude Code, OpenCode and Cursor away together. Gemini is given rtk hook-only, so the user's GEMINI.md isn't written over. Install RTK on the page (and magpie library rtk install) installs rtk with Homebrew, winget on Windows, or rtk's own script into ~/.local/bin, only when clicked
2026-09-26 21:53:05 +08:00
2026-09-27 01:53:04 +08:00
windows: the desktop app no longer opens a console window for every command it runs (#54) — it is linked as a GUI program and has no console, so each console CLI it started (devin auth status and models list, devin acp for every Devin turn, claude, codex, cursor-agent and grok probes and runs, grok login) was given a new console by Windows, and a Windows Terminal window with it, some every few seconds while the app sat idle. Every command magpie runs is now made through internal/proc, which starts it with CREATE_NO_WINDOW when magpie has no console of its own: the child gets a console without a window, and its output, which magpie always pipes back, arrives as before. A magpie run in a terminal (magpie serve, the TUI, the desktop app started from one with a command) has one, and its children share it as they did, so Ctrl+C there still reaches them. The relaunch after an update keeps its DETACHED_PROCESS, added to rather than replacing the flags it was made with, and a test fails on any command made with os/exec directly, so a new one can't bring the windows back
2026-09-25 14:04:44 +08:00
2026-09-24 12:17:45 +08:00
2026-09-24 12:17:45 +08:00
2026-09-26 14:30:16 +08:00
2026-09-26 14:06:45 +08:00
2026-09-26 14:06:45 +08:00
2026-09-26 14:06:45 +08:00
2026-09-26 14:30:16 +08:00
2026-09-24 01:09:59 +08:00
2026-09-26 21:00:33 +08:00
2026-09-26 21:00:33 +08:00
2026-09-26 19:03:14 +08:00