Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>TimeLodgeNew to Visual Studio Code? Get it now.
TimeLodge

TimeLodge

TimeLodge

| (0) | Free
Control your own TimeLodge timer without collecting code or editor activity.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

TimeLodge for VS Code and Cursor

Control your own TimeLodge timer from the editor status bar and command palette. Start or switch pinned and recent work, search projects and tasks, stop your timer, edit a short note, and open TimeLodge for full time-entry corrections.

Install

  1. Install TimeLodge (timelodge.timelodge) from the editor’s Extensions panel. For a manual installation, run Extensions: Install from VSIX… and select the TimeLodge VSIX.

  2. Run TimeLodge: Sign In, finish the TimeLodge browser consent screen, and return to the editor. If the browser does not open, choose Copy sign-in link in the editor notification, paste it into your browser, and finish connecting within five minutes.

  3. Select your team and use TimeLodge: Start or Switch Pinned / Recent Work.

A TimeLodge account and access to a workspace are required. The extension is free to install; TimeLodge subscription requirements apply to the service. It connects only to TimeLodge.

Compatibility

Editor Supported Native host checks
VS Code desktop 1.96 and newer in the 1.x series 1.96.0 and 1.135.0 on macOS arm64
Cursor classic editor 3.19.x 3.19.13 / VS Code API 1.128.0 on macOS arm64
Browser editor Unsupported Use TimeLodge in the browser

Cursor's agent window does not load this extension; use its classic editor window. Unsupported editor versions retain the browser link and display a compatibility message. Native checks cover activation, command registration, and callback resolution. Windows, Linux, and VS Code Insiders have not received native host validation in this build.

Timer controls run locally in Remote SSH and container windows. Workspace mapping and context capture are disabled in remote, virtual, and untrusted workspaces. Multi-root workspaces require an explicit folder choice.

Offline stops

An explicit stop is saved in editor SecretStorage with the original timer ID, version, operation ID and intended stop time. It survives an editor restart and retries after reconciliation. A retry never stops a replacement timer. Conflicts remain visible in TimeLodge: Review Pending Stop, where you can retry, open TimeLodge for corrections, or discard the saved action. Starts and note changes are never automatically replayed. Clock changes or sleep require a fresh sync before recording an offline stop.

Privacy and sign-out

The extension does not inspect source files, Git history, selections, terminal output, AI conversations, completions, or editor activity. Workspace mappings are optional local suggestions. Context capture requires device consent, an explicit preview, and confirmation. Repository, branch and issue context is manually entered.

Credentials, installation identity, mappings and pending stops use SecretStorage rather than settings or Settings Sync. TimeLodge: Sign Out and Revoke This Client clears local data and requests revocation of this installation's session. If the server is unreachable during sign-out, revoke the client from TimeLodge when reconnected.

Support

Email support@timelodge.com with the editor name, version, extension version and a description of the issue. Do not send credentials or private client information.

Data use

TimeLodge receives authentication and device information, timer actions, notes and context you explicitly confirm. This enables sign-in, workspace access, timer synchronisation and requested context attachment. Mapping choices remain in editor SecretStorage. Saved service records remain until removed through TimeLodge’s supported correction or deletion controls, subject to account retention and legal obligations. Service providers may process information to host, secure and support TimeLodge. The extension does not add advertising or editor-activity analytics.

Development and release checks

npm ci
npm run check
npm run test:host
VSCODE_VERSION=1.96.0 npm run test:host
CURSOR_EXECUTABLE=/path/to/Cursor npm run test:cursor
npm run package

VSCODE_EXECUTABLE can select an installed VS Code executable. Host checks use temporary isolated profiles. Cursor checks use --classic and require an actual Cursor executable. Run npm run release:check with both editors available before producing a release.

The same timelodge.timelodge identifier and VSIX are intended for Marketplace and Open VSX. Confirm publisher ownership, licensing, listing details, and production backend readiness before publishing; publication is a separate step.

Licence

Proprietary. Free to install and use with TimeLodge for personal or business work. A TimeLodge service subscription is separate. Source modification and redistribution require permission, except where applicable law provides otherwise. See the bundled LICENSE file.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft