[AnnatarHe]

Summary

An end-to-end check of the editor plugins (plugin → CLI daemon → server) found heartbeats that were silently dropped and activity that wasn't the user's. This PR fixes the Neovim plugin; the companion PRs are listed below.

Delivery

• {"status":"disabled"} counted as delivered. Heartbeats are now kept; a warning and :ShellTimeStatus explain how to turn code tracking on.
• The queue went out as one message, which servers failed to store past about 2,800 rows; messages now carry at most 500.
• A reply arriving after the timeout ran the callback twice, requeuing delivered heartbeats (measured: 600 → 1,200 → 2,400 pending). The callback now runs once.
• Heartbeats left when Neovim quits with the daemon down go to the daemon's resend file. The exit flush waits for every send in progress and saves what each left, and :ShellTimeDisable keeps the queue the same way.
• An empty reply counts as delivered only when the daemon still takes connections: daemons 0.1.42–0.1.47 took heartbeats without replying, and a current daemon skips the reply only while stopping, when its listener is already closed.
• Without git on PATH every heartbeat threw; the branch is now read from HEAD, which also keeps git off the main loop (git runs only for reftable repositories, whose HEAD is a stub, cached for 30 s).

Accuracy

• :bufdo, :argdo, :cfdo and session restore count only the buffer current when they finish; a reload from disk (:checktime after an outside change) isn't editing, while an undo back to the saved state still is; :wa attributes each write to its own buffer and cursor.
• Saves count once per debounce window, since auto-save plugins write after every change, but a save inside the window is kept with its own time and sent with the next flush, so the last save before :wq always arrives.
• The project is the git repository, so a monorepo's packages don't split into projects. Languages are VS Code ids (sh → shellscript, text → plaintext, ...), and an extensionless file under a dotted directory (john.doe/TODO) no longer reports a path as its language.
• The config comes from the files the CLI reads (config.yaml, .yml or .toml, plus config.local.*); trailing comments and yes/no booleans parse the way the CLI reads them, [[array]] TOML tables no longer overwrite the keys before them, and turning tracking on in the file applies without restarting Neovim.
• A lazy-loaded nvim-dap is no longer loaded by the first heartbeat, and the update check leaves the clipboard alone.

Tests that reached a real daemon

tests/socket_spec.lua sent its test heartbeats to /tmp/shelltime.sock, so on a machine with a running daemon they were uploaded to the developer's account. tests/minimal_init.lua now gives the tests a temporary HOME and points connections to the default socket at a path where nothing listens (with XDG_DATA_HOME pinned so the child processes still find plenary).

Testing

• ./scripts/test.sh: 306 passed, 0 failed (Neovim 0.11.4).
• End to end with a real headless Neovim driven over RPC against a local daemon and server: the stored rows have the right file, language, project root, branch and cursor; :argdo over three files stored only the last; a reload after an outside change stored nothing; the writes of :wa arrived with their own cursors; an edit and a save made while the daemon was down reached the server through the resend file after the daemon restarted.

Related

The same end-to-end check, one PR per repository: shelltime/server#567, shelltime/cli#336 (daemon), shelltime/coding-extension-vscode#25, shelltime/coding-extension-jetbrains#18, shelltime/coding-extension-vim#20 and shelltime/web#727. They can be merged in any order: every plugin keeps working with the current daemon and server, and the daemon with the current server.

🤖 Generated with Claude Code

https://claude.ai/code/session_019PvzR6GVwT4zShCyuHopyi

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-24T13:28:17.205943Z We couldn’t complete this review. Comment @codex review to try again.	463c1ab	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[shelltime]

☁️ Claude Code cloud · Audit, fix, test, and merge editor activity pipeline

Audited all three editor plugins end to end, fixed activity accuracy and reliability issues across the plugins, CLI daemon, and server, expanded regression coverage, and merged the completed changes.

💰 Cost	🔢 Tokens	⏱️ Duration	🧠 Model	💬 Prompts	✏️ Lines
$230.80	637.9M	8h 1m (3h 36m active)	claude-opus-5-5	3	+3101 / −298

_{637.9M tokens: 15.9K input · 2.4M output · 625.9M cache read · 9.4M cache write}

📝 AI summary

The session exercised the VS Code, Vim/Neovim, and JetBrains integrations against the Shelltime CLI/service and server, reviewing the full activity path rather than only isolated plugin behavior. Fixes included VS Code heartbeat collection/offline handling and Git metadata logic (src/heartbeat/collector.ts, src/heartbeat/offline.ts, src/utils/git.ts), plus Vim socket lifecycle, initialization, TOML parsing, and Git utilities (lua/shelltime/socket.lua, init.lua, and utils/*). JetBrains received test-infrastructure improvements for diagnosing coroutine/test timeouts.

The CLI daemon’s heartbeat resynchronization and timing behavior were corrected and covered with additional tests in daemon/heartbeat_resync.go, heartbeat_resync_more_test.go, and cc_info_timer_test.go. Server-side activity handling and coding-activity timeseries/schema behavior were also updated and validated, notably in server/handler/activity.go and related tests. End-to-end and targeted regression checks were added or run across repositories, including Vim socket tests and temporary independent review/verifier suites. The resulting changes across the editor extensions, CLI, and server were then merged together.

View this session on ShellTime →

_{Updated 2026-10-24 15:03 UTC by ShellTime · totals for the whole session so far · the session page is visible to its owner}