# LiftTrace v1.3.0 released: multiple sessions per day, timed sets, and more — retained record

> Retained reddit record from reddit:selfhosted.

Canonical: https://highsignal.app/data/records/71848e9520c84f45

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:selfhosted)  published 2026-09-20 11:58 ingested 2026-09-21 02:37

[original source ↗](https://www.reddit.com/r/selfhosted/comments/1wlf5w2/lifttrace_v130_released_multiple_sessions_per_day/)

## retained text



```
LiftTrace is a self-hosted weightlifting tracker, an alternative to Strong, Hevy, FitNotes and Jefit. AGPL-3.0, single Docker container, native Android app, no telemetry and no cloud sync. Your training log is a SQLite file on your own machine.

Part of the TraceApps family: **NutriTrace** (nutrition), **CookTrace** (recipes / pantry / shopping), **LiftTrace** (strength / lifting), **NoteTrace** (notes / tasks / reminders).

## New here?

- **It is a training log first.** Tap through sets with weight, reps and RPE, mark warm-ups, group supersets, and let the rest timer start itself. Last session's numbers sit above the row you are filling in, so you know what to beat. Type or speak "bench 3x5 185" if that is faster.
- **It runs your routine, not just records it.** Programs and templates with multi-week progression that raises the targets for you, an exercise library of thousands of movements with images, and statistics that answer the real questions: volume over time, per-exercise progress, estimated 1RM, automatic personal records and a muscle recovery map.
- **It works in the gym, where the signal does not.** The Android app logs offline and syncs when you are back, or runs entirely local with no server at all. It also imports your old log from Strong, Hevy, FitNotes, Jefit and Garmin, and has OIDC SSO, multi-user with roles, full backups, and an MCP server, REST API and webhooks that are off by default.
- **It does not phone home.** No telemetry, no cloud sync, no account anywhere else. Your log is a SQLite file on your machine, and the whole thing is one container.

## What v1.3.0 adds

- **Multiple sessions per day.** A day is no longer one workout. Log a lifting session and a separate mobility session on the same date, each tracked on its own, with a tab strip once a second one exists.
- **Timed sets.** Planks, dead hangs, wall sits and carries are tracked by how long you held them, not by reps. A hold timer counts you in, times the hold and ticks the set off, and records track your longest hold. Programs, CSV export and the Strong, Hevy, FitNotes and Garmin importers all understand it.
- **Progress photos.** Dated photos on their own page: a timeline with the weight logged that day, a draggable wipe between any two, and a scrubber that plays the whole record as a time-lapse. iPhone HEIC photos are converted in the browser, and photo files are only served to the account that owns them.
- **MCP server, REST API and webhooks.** All three are off by default. Scoped tokens work across MCP and the REST API, and webhooks fire a signed POST into n8n, Home Assistant or anything else without polling.
- **A weekly summary worth reading.** Sessions against your goal, sets, volume, time trained and records, each compared with your average week over the month before.
- **A redrawn muscle recovery map**, on correct proportions this time.

Community contributions this cycle from nine people: code, detailed bug reports and feature ideas. Everyone is named in the release notes.

## Security

Progress photos are served behind authentication, and full-backup archives are no longer reachable by URL. Uploads now take their extension from the file's real type and are served with a sandboxing content policy. Dependency advisories cleared this cycle covered moderate and high severity denial of service, validation bypass and prototype pollution issues.

## Upgrade note for Docker users

The container now listens on port 3002 instead of 3003, matching its sample host port. If your compose file maps `"3002:3003"`, change it to `"3002:3002"` before or right after the pull, or the app will not respond. Anything that reaches the container directly on the old port, a reverse proxy on the same Docker network, a Traefik port label or a tunnel, needs the same change. The host port does not change, so bookmarks and the Android app's server address keep working. Installs that set `PORT` themselves are not affected.

## Links

- Repo: https://github.com/TraceApps/lifttrace
- Full release notes + signed APK: https://github.com/TraceApps/lifttrace/releases/tag/v1.3.0

## AI Disclosure (per Q2 2026 sub rules)

AI is used as a coding assistant in development. Rough breakdown:

- Implementation: roughly 50/50 human/AI pair. AI drafts, I review, test on real hardware, only commit what I've verified. Every commit is manually reviewed
- Design / architecture: I make the architectural calls; AI suggests trade-offs and edge cases
- Documentation (README, CHANGELOG, release notes): also ~50/50 pair
- Testing / QA: real-device manual (I test on my own devices before every release). AI helps draft test plans and think through edge cases
- Review: I'm the reviewer; AI helps with security sweeps and audit passes on complex changes
- CI/CD: mostly conventional, AI-suggested improvements only


```



document fetched 2026-09-21 00:28 · canonical https://reddit.com/r/selfhosted/comments/1wlf5w2/lifttrace_v130_released_multiple_sessions_per_day
