commits in ptr.pet/prime-agent

The label derives its ttl text from the clock, so a loaded machine lands a second past the four-minute mark and the exact string flips to `4m 1s`. Assert the ratio and the minute instead; the seconds are the clock's, not the view's.

open commit browse files

73ecb005 test(coding-agent): keep the deadline test under the cell sleep limit Sep 17

test(coding-agent): keep the deadline test under the cell sleep limit

The cell-deadline test blocked with `time.sleep(30)`. The cell sleep guard (3cfe321e5) refuses a cell-code sleep above RLM_CELL_SLEEP_LIMIT (default 10 s), so the cell ended with status "error" before the 1.5 s deadline could abort it. Block for 5 s instead: under the guard's default limit, still well past the deadline, so the test keeps covering the deadline rather than the guard. Negative control: with `time.sleep(30)` restored the test fails again (expected "aborted", received "error"); with 5 s the file is 11/11.

open commit browse files

eedee091 test(coding-agent): keep the deadline test under the cell sleep limit Sep 17

test(coding-agent): keep the deadline test under the cell sleep limit

The cell-deadline test blocked with `time.sleep(30)`. The cell sleep guard (3cfe321e5) refuses a cell-code sleep above RLM_CELL_SLEEP_LIMIT (default 10 s), so the cell ended with status "error" before the 1.5 s deadline could abort it. Block for 5 s instead: under the guard's default limit, still well past the deadline, so the test keeps covering the deadline rather than the guard. Negative control: with `time.sleep(30)` restored the test fails again (expected "aborted", received "error"); with 5 s the file is 11/11.

open commit browse files

63cf36e8 fix(coding-agent): set the agent-message key in the huge-body render case Sep 17

fix(coding-agent): set the agent-message key in the huge-body render case

Agent-message bodies follow the fork's own expansion key, so the regression case that guards the JavaScript argument limit has to expand that key too; its subject is the huge body, not which key reveals it.

open commit browse files

f640661b feat(coding-agent): keep the fork's per-category expansion keys and the tray model label Sep 17

feat(coding-agent): keep the fork's per-category expansion keys and the tray model label

The rebase left upstream's single conversation-detail cycle in place and dropped the fork's two extra keys. Restore them on top of the cycle: - app.messages.expand (ctrl+p) and app.edits.expand (ctrl+j) are back in KEYBINDINGS with their editor scope, their onAction wiring, the summary line's chat-action path, and their shortcuts-help hints - agentMessagesExpanded is tri-state: undefined follows the detail level, a key press pins it, so ctrl+p flips what is on screen either way while ctrl+o keeps cycling overview -> details -> all - applyChatExpansion and the component-creation sites use that state, and ToolExecutionComponent/IPythonCellComponent carry it so sent agent messages expand on their own key (the ipython cell shows the key hint) - conversation-components honors options.agentMessagesExpanded - the tray context label carries the model id, its effort and the fast tier again, with the fork's cached-ratio wording and the cache ttl on their own segments; getModelContextLabel stays plain so callers style it - keybindings-migration now asserts the two actions exist, and the tray test fakes declare the model getter they rely on

open commit browse files

2026-09-18

2026-09-17

commits on main

2026-09-18

2026-09-17