Changelog

The new changelog page shows all new functions, improvements and fixes.

See how a dashboard can be a résumé. The developer example shows one developer. The team example shows a small team. Each example has a short note and some reports. Both examples use demo data. All examples are under Examples in the menu.

Team owners and managers can search their team by skills. Select a tech group, a technology and, if necessary, a detail (for example Programming languages › Python › Django). Then set the minimum level, the number of weeks at that level, and the last week of use.

Make each criterion required or optional. The people who match all required criteria are at the top. Each optional match moves a person higher. The table shows the criteria that each person matches. To open the search, select Find team members under "Team reports" on your home page.

See the team search before you set up a team. The team search preview has a demo team of seven people. Open one of the example searches, or add your own criteria. You do not need an account.

On a team Skill Radar, each member has a button below the chart. Point to a name to show that member above the other members. Click a name to hide or show the member. Double-click a name to show only that member. The Team average has a button too.

Each member line has a dot on each axis. Point to a dot to see the weeks of that member. Point to a point of the team average to see the value of each member on that axis.

All reports show the same tooltip, with the same text size. The Bus Factor and the Proficiency Summary use it too.

• The Treemap tooltip shows next to the pointer again, on the Treemap page.
• The Proficiency Summary shows "1 week", not "1 weeks".

The demo data of the report examples has more variation. The Skill Radar examples show different values on the axes, also for one week and for many technologies.

The report filters use less space. The filter line above the report shows each active filter. Click its × to remove it, or click Clear all. Open the line to see all filters: the tech groups are buttons, and the minimum level is a list of the level names. All reports, Velocity too, use the same filters.

• The tech groups in the report filters are easy to read in dark mode.
• Velocity shows your full history until you set a history limit. Before, a change to an other filter set the limit to 52 weeks.

• The account emails use your first name.
• The plain-text emails do not show HTML codes.
• The registration form shows its errors correctly.
• The Skill Radar labels and the Velocity legend fit in the image.
• The home page has better labels for screen readers.

See what Trekme creates from your weekly records. Open each report with demo data, for one developer or for a team: the Array timeline, the Treemap, Velocity, the Skill Radar, the Proficiency Summary and the Bus Factor. The Examples page shows all of them. You do not need an account.

The tooltips of the Array report show your weekly notes. The report always shows the technology boxes, also when a technology has details.

You can add your data, without your name, to the anonymous technology reports. This setting is off until you set it to on.

Add a short note to a week, for example what you built or learned. Each row also shows the age of its data.

The dashboard page has a new widget panel, scroll hints and a simpler share function.

Your account settings show where you are signed in, and your sign-in history. If you do not know a session, you can end it. The new Trust & Security page tells how we protect your data.

The home page shows new users the first steps: complete the first week, select technology groups and open the first report.

Create your own technology groups. Put them in the sequence that you want. The reports use your groups.

If you use the MCP integration across multiple projects, you've likely hit this problem: your AI assistant only sees the project it's currently working in. It logs FastAPI for Project A — but when you switch to Project B, the assistant sees Django but not FastAPI, and may suggest removing it as unused this week.

Project contexts fix this. Each AI assistant instance tags its entries to the current project, so logs from different projects stay separate and don't interfere with each other.

Project names never appear in reports — your data is merged into a single unified profile. Contexts are purely an input mechanism, not a reporting dimension, so there's no risk of one project's stack being visible where it shouldn't be.

How it works:

• Each project gets a named context: work, client-x, freelance — whatever fits
• Context names are created automatically on first use
• Your AI assistant tags technologies to the current project automatically, without touching other projects' entries

The weekly email shows the changes in your technologies: the new technologies, the technologies that you use again, and the technologies that you do not use any more.

The week page is clearer. You can complete it faster, on a computer and on a mobile phone.

Each report can show only your top technologies and details. It can also hide the technologies that you recorded only a small number of times. You can also select an accent colour for a report and for a dashboard.

A new account starts with a report and a résumé dashboard. Thus you see your data from the first week.

Trekme now exposes an MCP server — the protocol used by Cursor, Claude Desktop, Cline, and OpenCode.

You can connect your AI coding assistant and let it log your weekly technologies without leaving your editor. Just ask it: "log that I used Django and Postgres this week".

What's supported: - Bearer token auth (quick setup) - OAuth 2.0 (for shared/team setups) - View and revoke active integrations from Settings - list_weeks, add_technology, update_technology, and more tools

Setup instructions are in your account settings under Integrations.

Five new ways to visualize your technology data:

• Radar — spider chart of your tech spread, per person or team
• Velocity — week-over-week change rate, including technologies you've stopped using
• Proficiency — depth breakdown across every technology you've recorded
• T-Shape — breadth vs. depth balance across categories
• Summary — high-level activity overview

All reports support filtering by technology group, member selection, and time range. Tooltips are interactive and scrollable.

The dashboard has been rebuilt as a unified hub. Personal and team reports are now listed together, consistently styled, with direct links to every report type.

Dark mode applies everywhere too — pick your theme in Preferences.

You can now log in with your Google account — no password needed. Existing accounts can link Google from profile settings.

You can record the project in which you used a technology or a detail. The reports and your history keep this data.

AI assistants use two tools, set_technology and set_detail, to add or change an entry. This gives fewer steps and fewer mistakes.

You can sign in with your Google account, without a password. If you have an account with the same email, Google signs you in to that account.

A dashboard shows your personal and team reports on one page. You can add, move and resize the widgets. To share a dashboard, make it public.

Trekme has an MCP server. Connect Cursor, Claude, Cline or OpenCode to it. Then your assistant can record your weekly technologies while you work. For example, write: "log that I used Django and Postgres this week".

To sign in, use a token or OAuth. Your account settings show the connected assistants. You can remove their access there.

Five new reports show your technology data:

• Skill Radar shows the range of your skills, for you or for a team.
• Velocity shows how your technologies change each week. It also shows the technologies that you do not use any more.
• Proficiency shows the level of each technology that you recorded.
• T-Shape shows the balance between the range and the level of your skills in each category.
• Summary gives a short overview of your activity.

Trekme has a dark theme. In Preferences, select Light, Dark or System.