Harry Bayliss
01fc108086
- Palette's per-child "Kill <name>" action is now labelled "Close <name>" (action kind unchanged; still SIGTERM). Matches the existing "Close agent: …" context entry and reads less violent for a graceful term. - New "New Terminal" palette entry spawns a bare interactive $SHELL pane via LaunchTerminal (kind=terminal). Replaces the default "shell" process preset that was seeded on first run. - Exited KindTerminal entries are now dropped from the session in reapChild — terminals have no restart path, so leaving them behind as greyed rows in the Processes sidebar was just clutter. processList also filters defensively.
28 lines
1.8 KiB
Markdown
28 lines
1.8 KiB
Markdown
- [ ] Codex seemed to think that it needed to launch patterm itself to get the mcp working
|
|
- [ ] I cant click and drag to select text from codex
|
|
- [ ] codex uses perl to interact with the socket rather than calling mcp tools
|
|
- when it _did_ open a sub claude it opened it as a separate tab rather than a sub-agent.
|
|
- [ ] codex rendering is VERY slow
|
|
- maybe we need to use diffing rather than rendering the entire viewport for performance
|
|
- We should add a --debug and --profile flag, so we can get detailed performance data and full logs of the agent output to be debugged later on.
|
|
- I don't mind what format this is in, ideally easy for LLMs to understand
|
|
- [ ] Resuming a long claude session takes a couple of seconds for the entire buffer to load in, it looks like it's scrolling down for a couple seconds.
|
|
- In raw alacritty this is instant, so there's some sort of performance issue with patterm's terminal emulation.
|
|
|
|
|
|
# On Hold
|
|
- [ ] There's a unicode <?> being displayed in opencode [ON HOLD]
|
|
- Investigated 2026-05-14: patterm passes ghostty grapheme codepoints
|
|
through unchanged (vt/ghostty.go:452-462), so the `<?>` glyph is
|
|
most likely the *host* terminal's font fallback for opencode's
|
|
Nerd Font private-use codepoints, not a patterm substitution.
|
|
Need a concrete reproduction (which codepoint, which host
|
|
terminal/font) before changing rendering.
|
|
- [ ] After codex rips for like 15 minutes, the terminal becomes quite slow. [ON HOLD / VERIFYING]
|
|
- 2026-05-14: Perf plan P1-P11 landed (see CHANGELOG). Needs a real
|
|
long-running codex session to confirm whether the steady-state
|
|
slowdown is gone or some hotspot remains. Capture a pprof if it
|
|
still feels slow after ≥15 minutes — the structural drivers the
|
|
audit named are all addressed, so a remaining symptom is a new
|
|
one and probably wants fresh profiling.
|