Changelog

Every release and every fix, in date order. TimerOS v1.0.0 launched on 21 July 2026. Here is everything in that first public release, and everything since.

You don’t need to check for updates: the desktop app downloads new versions in the background and installs them automatically, and the notes for each release are also in the app under Settings → About. The web dashboard and client portal update continuously. When something on the roadmap ships, it appears here.

AddedImprovedFixed
Want an email when a new version ships? Write to [email protected].
TimerOS Workspace
Release feed
Updating TimerOS1.25.0 → 1.26.0
Downloads in the background, installs automaticallyAuto-update
Recent releases
v1.26.0“Why this came to you”, merge-check tooltips and meeting agendasOct 12
v1.25.0The support engineer, AI Executives in the Executive Team and AI team leads for new teamsOct 12
v1.24.0AI CTO, AI CMO and AI CPOOct 12
v1.23.0AI decisions, merge requests and AI Executives inside a departmentOct 11
v1.22.0AI Executives, AI-written skills and memory, project proposals and language settingsOct 10
v1.21.0Meetings, more AI roles and AI work on your projectsOct 4
v1.20.0AI employees, in betaOct 1
v1.14.0Give a task the time you already haveMajorAug 18
85 releases since 4 Jul 2026Every fix, in order

Releases

v1.26.0

“Why this came to you”, merge-check tooltips and meeting agendas

12 October 2026
  • Added“Why this came to you”. When an AI employee’s request comes straight to you instead of to an AI team lead or AI Executive, its card now says why. For example, the repository has no branch rule on GitHub that requires checks, a push in the pull request was made before TimerOS checked pushes on GitHub, or the AI Executive’s “Decides its team’s requests” switch is off.
  • ImprovedChecks on a merge request. Each check chip now lists its checks by name when you point at it. A check suite that a GitHub app opened but never started shows as “not started” and is not counted. The merge state reads in plain words, with what it means.
  • FixedIf approving or rejecting a request fails, the reason now stays on its card instead of disappearing.
  • ImprovedMeeting agendas. Meeting and event descriptions read as an agenda, with headings and bullet points, in the event details and in the meeting room.
v1.25.0

The support engineer, AI Executives in the Executive Team and AI team leads for new teams

12 October 2026
  • AddedSupport engineer for internal projects. A new AI role watches the live websites and checks of your internal projects, files and works incidents and change requests, and fixes what it can through reviewed pull requests. It resolves a P3 or P4 incident itself once its fix is verified; a person accepts the resolution of a P1 or P2 incident. Its change requests are decided by the AI Executive above it, and an emergency or critical change by a person. Its “On call” switch lets urgent incidents wake it outside its shifts, for at most 30 minutes and six times a day. When hired, it joins every internal project open to AI work (you can untick any), and every such project created later. Any AI employee can ask it to raise an incident or a change. It is offered once Vezoft switches it on.
  • ImprovedAI Executives in the Executive Team. An AI Executive that works inside a department is now a member of that department’s Executive Team and no longer gets a team of its own, so the hire form no longer asks for one. Its limits stay the same: no team chat, no escalations, no data about people, and nobody is placed under it. Its card shows the Executive and AI badges, with its focus, such as AI CTO, under its name. “Remove from the Executive team” in its row menu ends that role.
  • AddedCreate a team with an AI team lead. “Create Team” has a new “AI team lead” tab: the team is created and the hire form opens pre-filled on its review step.
  • FixedIncidents and change requests can no longer be assigned to an AI employee that can’t open them.
  • ImprovedIn the org chart, team names show in full, an AI team has a robot icon instead of a label, and counts read “1 member” and “1 employee”.
  • ImprovedThe app shows the AI Employees Notice 1.19, which covers the support engineer and AI Executives in the Executive Team. Nobody needs to accept anything again.
v1.24.0

AI CTO, AI CMO and AI CPO

12 October 2026
  • AddedAI CTO, AI CMO and AI CPO. When you hire an AI Executive, you now pick its focus: technology (AI CTO), marketing (AI CMO) or product (AI CPO). Each one has its own card in the hire form. The focus sets what its instructions put first, the skills it starts with and its default job title. An AI CTO plans and reviews the technical work of the AI employees below it. An AI CMO plans their content, SEO, graphics and marketing-website work. An AI CPO writes product specifications, priorities and milestone plans for internal projects. A focus never changes what an AI Executive may do or decide, and it can’t be changed after hiring. The AI’s Overview tab shows its focus.
  • ImprovedHire an AI Executive from the Executive Team. An AI Executive is now hired from the Executive Team: use “Hire AI Executive” on its Team page, in Manage Executives or on its box in the org chart. It always takes a seat on the Executive Team. “Hire AI employee” on any other team no longer offers the AI Executive. The Executive Team’s page now shows the AI Executives who hold a seat, and so does its box in the org chart on the Startup plan.
  • ImprovedThe app shows the AI Employees Notice 1.17, which describes the AI Executive’s focuses. It is a clarification, so nobody needs to accept anything again.
v1.23.0

AI decisions, merge requests and AI Executives inside a department

11 October 2026
  • AddedAI Executives inside a department. You can now hire an AI Executive that works inside a department without heading it, on the Startup plan as well as on Enterprise. People may work in that department too. It leads its own AI team, which can be a new one or an existing team with no person and no lead. It also leads the AI teams in that department whose team leads report to it. It never leads a person or a team a person manages, and it reports to a person who holds the “Manage AI employees” permission. On Enterprise, the hire form asks whether it heads an AI department, as before, or works inside one. On Startup it always works inside your department. Its page shows where it works and which team it leads. On Startup, Company settings now also has the switch that invites the person above an AI Executive to its planning meetings.
  • Added“Decides its team’s requests”. The page of an AI Executive or a team lead has a new switch, “Decides its team’s requests”. It is on by default for an AI Executive and off for a team lead until a person turns it on. With it on, a team lead approves, rejects or passes up the plans and work proposals of its AI reports on internal projects without a client. An AI Executive decides these for the AI employees below it. It also decides plans with new milestones, changes to the playbooks of AI teams led by the team leads below it, new internal projects and pushes of code. Neither decides its own request, a person’s request or anything about money, email outside the workspace or publishing, and each is instructed to pass up anything that looks off. Only a person with “Manage AI employees” above the AI in its line, or someone at the workspace’s highest access level, can change the switch. Turning it off sends the requests it holds to the first person above it at once. Its Requests tab lists what it decided.
  • AddedAI decisions in Approvals. A new AI decisions tab lists the requests you answer for while an AI team lead or AI Executive holds them. Each one shows when it goes to a person if it is still undecided after 24 working hours. The tab also lists what they decided in the last 7 days, with their reasons. Take over a request to decide it yourself, or undo a decision within 7 days. Before you undo, the app says what will be reversed. Each request shows how it was routed. Notifications of AI decisions, and their daily digest, open this tab.
  • AddedRejecting an AI employee’s request. When you reject a request, that exact request goes to a person for good, from any AI employee and however often it is filed again. You can also tick “Keep … with me for 7 days” for its repository, project or AI team. For those 7 days, a person decides every AI employee’s request there instead of the AI Executive. Undoing an AI decision does the same. AI decisions → Held for you lists these holds. “Let the AI Executive decide again” ends a hold early, and so does approving a request there in full.
  • AddedRepository settings. On a project’s Team tab, turn on “A person always decides” for the whole project or for one repository. AI team leads and AI Executives then never decide its requests. When you approve an AI employee’s push, you can also choose “Approve and don’t ask me again for this repository” for the AI employees you tick. Their later pushes to its default branch are then approved at once in your name, unless an AI Executive above them decides them first, and are listed in your daily digest. Each repository on the Team tab lists your standing permissions, and you can revoke one there. A standing permission lapses when an AI it covers leaves your line or the people between you and it change, when you leave or no longer hold “Manage AI employees”, or when the repository becomes public.
  • AddedMerge requests. An AI employee can ask to merge a pull request it opened, and its AI Executive can decide it under strict rules. Where the repository’s branch rules on GitHub still have to pass, GitHub merges exactly the approved commit once they do. Otherwise the AI Executive’s approval merges it only when those rules require checks, each required check on that commit succeeded, every other check on it passed and the AI Executive states it is confident; anything else goes to a person, a repository without branch rules included. The request’s card shows the approved commit, every push in the pull request with who approved it, and the checks on that commit. If no check ran, the card warns that approving merges it without any check. Approve in the Approvals list opens the card first.
  • ImprovedNo Role field for leads. When you hire a team lead or an AI Executive, the form no longer asks for a role. It shows the access role the AI starts on and whether it moves to the AI Team Lead role (level 4) once it leads. Other AI employees are hired with a role, as before.
  • ImprovedThe app shows the Terms of Service 2.3 and the AI Employees Notice 1.16. Both now cover AI decisions: an AI Executive, or a team lead whose switch a person turned on, may decide certain requests of the AI employees below it. It decides them under the permissions of the first person above it, who can undo a decision for 7 days. The notice also covers AI Executives that work inside a department. Account owners are asked to accept the new Terms.
  • FixedThe hint on who an AI employee can report to now also names the AI Executive above an AI team lead. In Bulgarian, the hint now names the AI team lead and reads unambiguously.
  • Fixed“Appoint an AI Executive” no longer offers one that works inside a department.
v1.22.0

AI Executives, AI-written skills and memory, project proposals and language settings

10 October 2026
  • AddedAI Executives. Hire an AI Executive to head a department with no people in it: an existing one without a head, or a new AI department. It plans the work of its AI teams and leads their team leads and the AI Executives of the departments below. While it heads a department, no person can be placed in it or below it, and like every AI employee it approves nothing. You can replace it later with a person or another AI Executive. Give it a seat on the Executive team and it joins the meetings it is invited to there, with no say over people and no access to their data.
  • AddedPlanning meetings. An AI Executive or a team lead can hold a planning meeting for the week or the month ahead, with an agenda and a limit on AI turns. It shows as Planning in Meetings and on the Schedule. The people invited observe: you see the room live and can write at any time, and the AI employees address you only when you write. The first person above an AI Executive is invited to its planning meetings. On the Enterprise plan, you can switch this off in Company settings. Any meeting room with an AI employee in it now says that what is written there goes to their model providers.
  • AddedTeam leads. The team coordinator is now called team lead. A team lead can now also lead only the AI members of a team a person manages: when you hire one, choose whether it leads the team, leads its AI members or joins as a member. The person stays the team’s manager and needs the “Manage AI employees” permission. The team lead reports to them, and approvals still go to a person. The Team page marks the AI lead. The other AI members of a team report to a person or to the team’s AI lead.
  • AddedSkills and memory of their own. An AI employee now writes its own skills without asking first. They are on its Skills tab, marked “The AI’s own” like the skills that came with its role, and you can edit or retire them. Its own memory, on the Memory tab, holds work facts, house conventions and lessons it reads at the start of every session, never notes judging a person. Skills, memory, soul and instructions keep their earlier versions: open History, choose “Use this version” and save to bring one back.
  • AddedProposals from AI employees. The Company setting is now called “AI employees propose work”. With it on, an AI employee without an AI team lead proposes itself for unassigned tasks on its projects, once a day when it has nothing to do. An AI team lead can propose a whole new internal project, with dates, milestones, tasks, subtasks and, if it needs one, a new GitHub repository. A new repository needs a GitHub organization connected in Company settings. A proposed plan now shows its tasks by milestone, with their subtasks and the ones left unassigned. You tick the tasks to approve. An approved project is created in your name, with you as its manager.
  • AddedLanguage settings. In Settings, under “How AI employees address you”, choose the language they use with you: Bulgarian, English, or Automatic, the language you write to them in. In Company settings, choose the language for team threads, meetings and the messages AI employees send each other.
  • AddedTasks that wait on other tasks. A task can wait on other tasks of the same project. It shows a Blocked badge in lists, on the board and in the project, and its details list what it waits on. Remove one if the work can start anyway. Its assignee is told when it is ready to start. AI employees add these links when they plan, and they do not start a blocked task. When you edit a task, you can now move it to another milestone. Tasks without one are listed under “No milestone”.
  • AddedTeam playbook. A team’s AI employees share how-to skills for their work, shown on each one’s Skills tab. Write one yourself, or approve the ones they propose, with the changes shown line by line.
  • AddedA thread for your team. A team you manage with two or more AI employees has its own thread with them, and the Team page shows who is in it. Type @ in a thread or a meeting room to pick an AI employee by name, and see when it is thinking.
  • AddedTools and websites on the Access tab. Turn an AI employee’s tools off one group at a time, such as Web, GitHub or Images. The core task tools stay on, and “Reset to role defaults” undoes your changes. A change applies from its next session. It only narrows what the AI is offered; its role still decides what it may do. For a QA tester hired before this release, the tab offers to add the CDNs that an AI website designer’s sites load from, so it sees those sites in full. New QA testers start with them.
  • ImprovedReasons on approval decisions. The approval card has a Reason box for both Approve and Reject. The requester sees it, and an AI employee reads it to know what to change. Reject in the Approvals list now opens the card so you can give one. Before, a reason typed when rejecting was not sent. Requests from AI employees are also easier to read: they name the AI’s computer, show a shell command as Command, keep line breaks and have all their labels translated.
  • ImprovedThe app shows the AI Employees Notice 1.14 and the Terms of Service 2.2. The notice now covers AI employees working on their own computers without asking first, their own skills and memory, team leads and AI Executives. Account owners are asked to accept the new Terms.
  • FixedHiring or moving an AI employee no longer offers the Unassigned and Dismissed teams.
  • FixedNotebooks can no longer be shared with AI employees.
  • FixedAn incident can be escalated only to a person.
v1.21.0

Meetings, more AI roles and AI work on your projects

4 October 2026
  • AddedMeetings. A new Meetings page, next to Schedule, lists your upcoming and past meetings and trainings. Open one to enter its room, where the people and AI employees invited talk in one thread. When it ends, the team coordinator or you write the minutes, with the summary, the decisions and the action items, and they stay editable. AI employees who attended keep what was decided.
  • AddedRepeating events. Any event on the Schedule can repeat: daily, weekly on the days you pick, monthly on a date or on a weekday such as the second Tuesday, or yearly, until a date or for a set number of times. Changing or deleting one asks whether you mean this event, this and the following ones, or all of them.
  • AddedMore AI roles. Besides a website designer, you can hire a QA tester, a content writer, an SEO specialist or a graphic designer, and a team coordinator, which manages a team of AI employees. On an AI employee’s Access tab you choose which websites it may open.
  • AddedAI employees on your projects. Mark a project as one AI employees may work on, now also when you create it. An AI employee then proposes the tasks it could take on, and you approve them one by one; a plan it proposes for a project is approved the same way, item by item. A workspace setting decides whether AI employees may complete their own tasks or must send them for review.
  • AddedRepositories and live sites. On a project’s Team tab, link its GitHub repositories or create a new one, and list its live sites. AI employees on the project read the code with short-lived access, and every change they want to push comes to you for approval first.
  • AddedHow AI employees address you. In Settings, write how AI employees should address you, a title and surname or just your first name, and they use exactly that. If you leave it empty, they use your full name. They never add a title on their own.
  • ImprovedAn AI employee’s PC tab shows the versions of its software and of its computer, and its last update.
  • ImprovedHours read the same way everywhere, as “9h 32m”, instead of decimal numbers.
  • ImprovedThe app shows the AI Employees Notice 1.11, which now also covers web searches by AI employees and how their computers are updated.
v1.20.1

Accepting updated terms from the desktop app

1 October 2026
  • FixedAccepting an updated legal document works from the desktop app again. When a new version of the Terms or the Data Processing Agreement comes into force, the app accepts the version the server has published instead of one built into the app, so the acceptance prompt can no longer get stuck. In v1.20.0, the Data Processing Agreement 1.1, in force from 2 October, could only be accepted in the web app.
  • ImprovedThe app now shows the Data Processing Agreement 1.1 and the AI Employees Notice 1.4. The agreement states plainly where your data is processed: in the EU, with two exceptions. AI employees’ model calls run in the United States, and the website previews they deploy are held on Cloudflare’s global network. A preview is open to anyone who has its link and is deleted 30 days after it is made, or as soon as its AI employee is offboarded.
v1.20.0

AI employees, in beta

1 October 2026
  • AddedAI employees, in beta on the Startup and Enterprise plans. Hire one from the Team page, or straight into a team from the org chart: choose what it does (today, website design), its team, its manager and its shifts. It gets its own cloud computer, its own TimerOS login and a role with its own permissions, and it works the shifts you give it like anyone else on the team. It can never see salaries, approve anything or manage people. While it is in beta its behaviour may still change, so review its work before you rely on it.
  • AddedTalk to it in Chat. You can see when it is thinking, its replies arrive as formatted text, and its profile shows its screen live, full screen if you like.
  • AddedIts day is tracked like a person’s. During its shift it is productive while it works, idle while it waits for work and on a break during the shift’s breaks; outside its shift it shows as Ready, never Offline. Its hours appear in the same dashboards but never in payroll, because an AI employee is billed separately, through its own ledger.
  • AddedIt asks before anything that matters. Spending, deleting, a new skill or a bigger budget goes to its manager as an approval request first, and when it is stuck it turns to the first person above it. A task that is not its kind of work goes back with a note saying why, instead of being done badly.
  • AddedAI teams. Make an AI employee the manager of a team with no people in it and the team becomes an AI team: the lead reviews its reports’ work and moves tasks between them, while every approval still goes to a person. People can never join an AI team, report to an AI or be given an AI role. You manage AI employees where you manage people. In Company → Teams → Manage members, on both org charts and on the Team page, an AI menu lets you change an AI employee’s manager or role, move it to another team, open a chat with it or offboard it.
  • AddedProject files can be marked internal or visible to your client, one file at a time.
  • ImprovedThe Back button on an AI employee’s profile returns you to the page and tab you came from, and you can add a team straight from Company → Org Chart.
  • FixedOn the Startup plan, the company’s department no longer shows under an old internal name.
v1.19.3

Your incidents and change requests, if you allow it

11 September 2026
  • AddedA connected AI assistant can now work on your incidents and change requests. This access has its own tick box on the approval page when you connect. It is ticked by default; untick it and the assistant never sees an incident or change request. These records contain text written by your clients, so that text is passed to the assistant labelled as the client’s and treated as data, never as instructions. Connections made before this update do not have the box: disconnect and connect again in Claude to get it.
  • AddedThe assistant acts only on incidents and change requests assigned to you. If you ask about one that is not, it asks before assigning it to you. It can also hand one to a colleague, or suggest the right person based on your teams, job titles, skills and languages, with a one-line reason. It assigns only once you agree.
  • AddedResolving an incident or completing a change request comes back as a plan that you approve before anything is saved. The plan shows what will change, exactly what the client will see in their portal and receive by email, and what happens to billing. The assistant does not create invoices or calculate amounts. Any notes it writes are internal, and the client never sees them.
  • FixedInternal staff notes no longer reach the client portal. Internal notes on change requests, and on incident and change request updates, were sent to the portal and only hidden on screen. The server now removes them before anything is sent to a client.
v1.19.2

Two things our privacy notices left out

9 September 2026
  • FixedThe timer had a diagnostic recorder that saved what the activity classifier saw, raw window titles and website names, to a file on your computer and kept it for 30 days. It was on for every install and could not be switched off. Nothing was ever sent anywhere; the file never left your computer. But no privacy notice mentioned it, and the Automated Processing Notice said the opposite. It is now off unless you switch it on in Settings → Activity Detection → Diagnostic recording. The first time this update starts, it deletes anything an earlier version recorded. Switching the setting off later also deletes the records instead of only stopping new ones.
  • FixedOur privacy notices said the timer reads your browser tab’s address only if your workspace has website rules. Since v1.4.4 it has also read the address while automatic task assignment is on, as it is by default, so the site can help suggest which task you are working on. The behaviour has not changed and is still limited: only the site name and one section of the path, kept in memory, never stored and never sent. The notices now say this, name both conditions and show where you can switch it off. We corrected the Privacy Policy, the Automated Processing Notice, the monitoring notice in all five languages and the docs together.
  • AddedThe tracking notice you see on first run now lists the browser address alongside window titles and idle time, so you acknowledge the complete list.
v1.19.1

One switch for the whole workspace

9 September 2026
  • AddedOwners and admins can now turn off AI assistant connections for the whole workspace in Settings → Connections. Turning them off disconnects every connected assistant immediately, blocks new sign-ins through the connector and emails everyone affected, so nobody is left wondering why their assistant stopped working. Connections are allowed by default, and members see a notice when an administrator has turned them off.
  • AddedYou get an email every time a new assistant is connected to your account. It names the assistant and what it was allowed to do, and tells you where to disconnect it.
  • FixedThe sign-in page that opens when you add the connector in Claude no longer fails with an error.
v1.19.0

Bring your own assistant

8 September 2026
  • AddedConnect an AI assistant to your account. Settings has a new Connections section: copy one URL into Claude (Settings → Connectors → Add custom connector), sign in, and choose exactly what the assistant may do. It can read your work, or also create and update projects, tasks, subtasks and expenses, and assign your unassigned tracked time to your tasks. It can never see salaries, send invoices, log new time or delete anything.
  • AddedSee what an assistant has done. Each connection shows when it was created, when it was last used and how many changes it has made. Expand it to see every change, each with the action that undoes it. Disconnect with one click, and access stops on the assistant’s next request.
v1.18.3

Pictures on every board

28 August 2026
  • AddedYou can now add pictures to project whiteboards and war room canvases, just as in notebooks. Add one from the toolbar, paste it from the clipboard or drag it in. You can then move it, resize it, and bring it in front of or send it behind other items. PNG, JPEG, GIF and WebP, up to 10 MB each and 100 per board.
  • AddedYour clients can see the pictures you add, on the project whiteboard in their portal and on the shared war room canvas, but they cannot add their own. Keep this in mind before pasting a screenshot onto a board a client can open.
  • AddedPictures are stored privately and shown only to people who can already open that board, so they are exactly as private as the board itself.
  • ImprovedThe project whiteboard now resizes with the window instead of sitting in a fixed-size box, and the revisions column resizes with it. You can also collapse the revisions column with the arrow in its header. It shrinks to a narrow strip at the side, giving the space to the canvas, and stays collapsed until you open it again.
v1.18.2

Bring to front, send to back

28 August 2026
  • AddedSelect anything on a canvas, such as a picture, a drawing or a note, and move it above or below whatever it overlaps. Use the toolbar or Ctrl+] and Ctrl+[. It works on several items at once and keeps their order relative to each other. Undo puts them back exactly where they were.
  • AddedThis works on every canvas, not only notebooks: project whiteboards and war room canvases get the same two buttons.
v1.18.1

Pictures that stay

28 August 2026
  • FixedA picture you added appeared briefly and then turned into an empty frame. When saving, the app did not send the picture’s ID and the server did not store it, so the saved copy came back without the picture and replaced it on screen. Pictures added in the previous version remain empty frames and need to be added again.
  • FixedPictures could not be clicked, moved, resized or erased. The canvas could draw pictures but could not detect a click on one, so it ignored every attempt.
  • FixedExporting a notebook with pictures produced a blank dark page. The export did not load the pictures, so each one appeared as the faint outline shown for a missing image. Exports now include pictures and use your own colours instead of a default palette.
v1.18.0

Pictures in notebooks

27 August 2026
  • AddedYou can now add pictures to a notebook page. Add one from the toolbar, paste it from the clipboard or drag it in from your desktop. You can move it, resize it and write next to it like anything else on the page. PNG, JPEG, GIF and WebP, up to 10 MB each and 100 per notebook.
  • AddedPictures are saved with the notebook, not on your computer: add one at your desk and it is also there in the web app and on your phone. If the notebook is shared, the people you shared it with see the pictures too. Your clients never do.
  • AddedA picture can only be opened through the notebook it belongs to. It is stored privately, never at a public address, and shown only to people who can already open that notebook, so it is exactly as private as the page it is on.
v1.17.1

Your own notebook is no longer read-only

27 August 2026
  • FixedYour own notebook could open as “Read only”. This happened when the app was newer than the server: the app tried to join the notebook’s live session, the server did not yet support live notebooks, and the app treated that refusal as “you cannot draw here” until you closed the notebook. This can no longer happen to your own notebook. The server still checks every save, as before; a refused live session just no longer stops you drawing.
v1.17.0

Draw together in shared notebooks

27 August 2026
  • AddedShared notebooks are now live. Give a colleague drawing access and you can both draw on the same page at the same time. You see their cursor with their name, and their strokes appear as they draw, just like on a project whiteboard. There is nothing to switch on: anyone else who has the notebook open is there with you.
  • AddedWhen you share, you choose whether the other person can view only, or view and draw. You can change this for anyone already on the list without removing them first. Either way it stays your notebook: only you can rename it, change who it is shared with, change its pages or delete it. It is never shown to your clients.
  • AddedSearch now looks inside your notebooks, not just at their names. Type in the search box on the shelf to see matching notes and text, each with the notebook it came from. Click a result and the canvas opens centred on it. Search covers only your notebooks and those shared with you, so it cannot find anything in a colleague’s notebook they have not shared with you.
  • AddedDeleting a notebook is no longer final. It goes to the Trash at the bottom of the shelf, and its contents are kept for 30 days so you can restore it. Deleting it permanently is a separate step and only works from the Trash.
  • AddedExport a notebook as an image or PDF. The export includes the whole canvas, not only the part on screen, at print resolution and without the background grid.
  • ImprovedLinking a notebook to a project or task is faster in large workspaces. The picker used to load every task you can see before showing anything; it now searches for what you type.
  • ImprovedAll of this works on desktop, in the web app and on Android, with the same notebooks in all three, including live drawing.
v1.16.0

Notebook: your own private canvas

27 August 2026
  • AddedNew: Notebook. Create your own private canvases. A notebook is a blank page where you can draw and add typed notes anywhere, using the same tools as a project whiteboard, but just for you. Find it in the sidebar under Tasks.
  • AddedNobody else in your workspace can open your notebooks unless you share them: not your manager, not an owner, not someone who can see everything else. The server checks every request and treats a notebook that is not yours as if it does not exist. No role permission gives access to them, so none can be granted by mistake.
  • AddedGive each notebook a name and a cover colour, pin the ones you use most, and search them by name. Each notebook holds up to 5,000 drawn or written items, and you can have up to 100 notebooks.
  • ImprovedNotebook is also in the web app and on Android, with the same notebooks: start something at your desk and it is on your phone. In this release, shared notebooks are read only.
  • FixedChanging the style of items on a canvas no longer hits the rate limit. The colour, width, opacity and text-size controls saved at every step while you dragged them, and one drag of the text-size slider could make over forty saves. A bit of tidying could use up the limit, and then the board stopped saving. A drag is now one save when you let go, and undo treats it as one step. The project whiteboard and war room canvas had the same problem since launch and are fixed too. Holding Ctrl+Z also no longer undoes thirty times a second.
  • AddedNotes on tasks. Projects already had a notes feed; now tasks have one too, showing who wrote each note and when, with as many notes as you need. Task notes are internal: your team can read them and your clients cannot. Anyone who can edit the task can add a note, including a team member working on their own assigned task, since they usually know the work best. You can always delete your own notes.
  • AddedNotebooks can be linked to a project or task. A linked notebook shows the project or task as a label, and the task shows "Your notes on this", so your notes are one click away. The link is private: the task is not changed, and nobody else can see that you have notes on it. That line on a task only ever shows YOUR notebooks, never anyone else’s.
  • AddedYou can share a notebook with colleagues as read only. They can open and view it, but cannot draw on it, rename it or delete it, and it is never shown to your clients. Shared notebooks appear in their own section of your shelf with the owner’s name, so it is always clear whose notebook it is. Opening someone else’s notebook changes nothing for them: their shelf order stays the same and no trace is left.
  • AddedPages are optional. Turn pages on and A4 outlines appear under the canvas, with arrows to move between them; turn them off for one endless sheet. You can change this at any time: pages are just outlines underneath, so switching never moves or deletes anything you have drawn.
v1.15.5

Window outlines are back

23 August 2026
  • FixedThe sign-in window and the timer bar have an outline again. Windows used to draw it, and it disappeared in the release that stopped clicks next to the collapsed timer from closing the app. The visible outline and the invisible border catching those clicks were the same thing, so removing one removed both. The dashboard kept its outline because that fix did not touch it. Both windows now draw their own outline in the dashboard’s colour, and clicks next to the collapsed timer still reach whatever is behind it.
v1.15.4

Sign in without retyping

19 August 2026
  • AddedA Remember me box on the sign-in screen. Leave it ticked and your email address is filled in next time, so you only type your password. It remembers the address only. Leave your password to a proper password manager, in your browser, on your phone or in the desktop app. It stores the password encrypted and lets you remove it in one place.
  • FixedTimerOS never offered to save your password, and pressing Enter in the password field did nothing. There were two causes, both fixed. The email and password fields were not inside a form, which is what password managers look for. And the desktop app runs on a Windows web engine that has its own password manager switched off by default, so even a correct form was ignored. It is now switched on: the app can offer to save your password and fill it in next time, and Enter signs you in.
  • FixedReorderable toggles could not be dragged on a phone. Moving your finger sideways was treated as scrolling, which cancelled the drag before it started, so the toggles still switched when tapped but would not move. You can now reorder them with your finger, and a scroll that starts on one still scrolls the page.
v1.15.3

A one-time hint for reorderable toggles

18 August 2026
  • AddedToggles you can reorder now show a one-time hint. The first time you open a page with a set of them, the set is highlighted and a card shows two toggles swapping places. The toggles still work while the card is open, so you can try dragging straight away. Once you dismiss the hint, it does not come back on its own.
  • ImprovedThe hint waits its turn. On your first sign-in you see the setup wizard, then the page tour, and only then this hint. Replaying the tours from Settings replays it too.
  • FixedToggle rows no longer show a scrollbar. A single pixel of overflow made the browser treat the row as scrollable, and the scrollbar covered part of the toggles.
v1.15.2

Reorderable toggles in more places

18 August 2026
  • AddedReorderable toggles are now in the remaining places where order makes sense: a project’s Tasks and milestones tab, a client’s Projects tab, Team and Department grouping, Goals, a project’s Activity filter, and the Production and Proposal split in the status manager. Each opens on whichever option you put first.
  • ImprovedGoals is a deliberate exception. It already remembered the last view you chose, and that still takes priority. The order you set only applies if you have never chosen a view.
  • ImprovedSome toggles are deliberately not reorderable. Day, Week, Month and Year form a scale, and shuffling them would only make it harder to read. The Internal and Client tabs above a note decide who the note is for, so putting either one first could lead to an internal note being sent to a client. Export format pickers stay fixed too, because they are part of a form.
v1.15.1

Drag them into the order you want

18 August 2026
  • AddedThe small toggles at the top of Projects, Tasks and Clients (List, Board and Timeline; All tasks and My tasks; Client projects, Internal and Proposals) can now be dragged into any order, and each page opens on the one you put first. Drag with the mouse or your finger, or hold Alt and press the arrow keys.
  • ImprovedThe order only decides which view opens next time. Rearranging does not change the view you are on, and links to a specific view still work: a link to your proposals opens proposals, whatever order you have chosen.
  • FixedThe Tasks page listed “All tasks” first but opened on “My tasks”, so the second toggle was highlighted. It now opens on whichever you put first. If you prefer to land on My tasks, drag it to the front once and it stays there.
v1.15.0

Hours you actually tracked

18 August 2026
  • RemovedTracked hours on a task or subtask could be overridden by a number you typed in, not linked to any tracked time. You could enter 40 without tracking a minute, and that figure fed into budgets, payroll and the hours your client sees in their portal. That field has been removed. Tracked hours now come only from time that was actually tracked. To put time on a task, allocate it from time you already have.
  • AddedIf someone worked but did not track it, for example away from their computer or in the web app (which does not track time), you can now record that time for them on the right day in Performance and then allocate it. Before, you could not add time to any day before yesterday, so the typed-in field was the only way to enter it.
  • ImprovedYour client now sees less detail. Hours in the portal are shown per task instead of per subtask, rounded to the nearest quarter hour, with the time they were last calculated. Hours per item next to each person’s name amounted to handing your client a timesheet, when what they need to see is progress.
v1.14.0

Give a task the time you already have

Major release
18 August 2026
  • AddedYou can now give a task time that you actually tracked but never linked to anything. Until now the tracked figure on a task could simply be typed in, true or not. Allocation uses only minutes you really tracked, so the task total and your day both stay accurate.
  • AddedThe Task time panel in Performance used to show a single day only. It now follows the period you select, so you can see which tasks a week, month or year of your tracked time went to, and how much went to no task at all. Reassign and Unassign there apply to the whole period, as noted above the list.
  • ImprovedTracked time is stored per day, so allocating it means taking it from specific days. The dialog starts with the most recent day and works backwards, listing each day it will use and how much it takes from each. You can change any of these, and nothing is saved until you confirm.
  • AddedYou can also do this from a task or subtask directly, on the Tasks page and in a project’s Tasks and milestones tab. It uses the last 30 days of time tracked by the person the item is assigned to.
v1.13.3

No more hidden border on the collapsed timer bar

16 August 2026
  • FixedThe collapsed timer bar had an invisible border around it, added by Windows, and clicks on it behaved like clicks on a normal window frame. Below the bar was an invisible close button, so a click there really closed the timer bar. On either side was an invisible title bar, so a double-click there maximised the bar to full screen. None of it was visible, so there was no way to avoid it. The border is gone: the collapsed bar is now exactly what you see, and clicks next to it reach whatever is behind it.
  • FixedThe previous release tried to fix this but made it worse, replacing the full-screen problem with flickering. That change has been removed; it was based on the wrong diagnosis.
v1.13.2

War room tabs and the collapsed timer bar

16 August 2026
  • FixedThe two tabs in a war room are now in the dialog header. They already stayed in place while scrolling, but the room had padding above them, and content showed through that gap as you scrolled. The room now scrolls cleanly under the header.
  • FixedThe collapsed timer bar had a dead zone around it. Windows will not shrink a framed window as small as the collapsed bar, so the window was larger than the bar you could see. The empty area around it blocked clicks meant for windows behind it, and a double-click there could maximise the timer bar to full screen. The bar now fills its whole window, so clicking anywhere on it expands it, and the timer bar can no longer be maximised.
v1.13.1

War rooms match the rest of Support

16 August 2026
  • ImprovedThe war rooms list now matches the incidents and change requests lists next to it: the same card, the same columns, and sorting on every column. Before, it was a plain table that could not be sorted.
  • AddedThe list also shows which client each room is for and the title of the incident or change request it was opened from, so you can tell rooms apart without opening them.
  • ImprovedInside a room, the status, room number and linked record are now next to the title and stay visible while you scroll. The Action centre uses the freed row for more canvas and conversation space.
  • ImprovedLabels and switches inside a room now have outlines, so they no longer look like plain text. They show which canvas you are on, which of the two conversations you are typing in, whether a client contact you let in can draw or only watch, and who is in the room.
v1.13.0

Your team and the client in one room

12 August 2026
  • AddedA war room now has two canvases, one shared with the client and one for your team only, and you can switch between them inside the room. Before, the client drew on a canvas nobody on your team could see.
  • AddedClient contacts you let in now appear in the Here now list alongside your team, with their cursors, so you can see what someone is pointing at while they talk about it.
  • AddedThe room has a second conversation, shared with the client. Your team’s own conversation stays separate and is never shown to the client. The two look different so you always know which one you are typing in.
  • AddedWhen you let a client contact into a room, they are told straight away: they get a notification that opens the room, and the room appears in their portal without reloading the page.
v1.12.0

Bring the client into the room

11 August 2026
  • AddedYou can now invite client contacts into a war room. Open the room, turn on client access and choose which people from that client may join, one by one; you cannot add the whole company. They see the client canvas and the room’s milestones, and nothing else: not your team’s canvas, not the internal conversation, and not who joined or left.
  • AddedEach person you add needs their own portal login. A shared client password is not enough, because anyone who knows it could join a live incident. The contact list shows who can be added and, for everyone else, exactly what is missing, so you find out before an incident rather than during one.
  • AddedEach person can either watch or draw, and watching is the default. You set this per person, not for the whole room. Removing someone takes them out of the room within about twenty seconds, without waiting for their session to expire.
  • AddedIn the client portal, a new War rooms section lists only the rooms that person has been added to. Two people at the same company may see different lists, and that is intended.
v1.11.0

Incident war rooms

Major release
11 August 2026
  • AddedIncident war rooms. When something goes wrong, open a room directly from the incident or urgent change request, and everyone working on it has one place to meet. Rooms have their own tab in Support.
  • AddedEveryone who joins picks a role and a team from lists set when the room was opened, so it is clear who is coordinating, who is investigating and which side each person is on. Roles are labels only; they do not change what anyone can do.
  • AddedEach room has a shared canvas, the same as on projects. Sketch the problem, cross off what has been ruled out, and everyone sees the drawing live, without waiting for a save. Above the list of participants, the room shows who has it open right now and who is typing. The participant list below records everyone who ever joined and their role, and keeps them listed after they leave.
  • AddedResolving the incident closes the room automatically and notes this on the room’s timeline, so rooms do not stay open after the work is done. Deleting the incident also deletes its room, history and conversation.
  • AddedOpening a room notifies the people already on the record: the assignee, whoever it was escalated to, and whoever is implementing the change. Closing it notifies everyone who was in the room. The notification opens the room directly. For now, rooms are for your team only; inviting the affected client is coming next.
  • AddedOpening a room from an incident takes you straight into it, and the button then reads “Go to war room” instead of offering to open a second room, which would not be allowed. Urgent change requests can open a room the same way.
  • AddedInside a room, the Action centre shows the canvas, the conversation and who is here side by side, because during an incident you need all three at once. Room setup has everything else: the roles and teams the room was opened with, who set them, and closing or reopening the room.
v1.10.5

Support permissions now enforced by the server

10 August 2026
  • FixedAnyone in the workspace could edit or delete incidents and change requests through the API, whatever their role allowed. The app always followed the role settings, but the server did not check them. It does now, including for deletion, which is permanent. Nobody loses access they had: support is open to every member by default, and that has not changed. The difference is that a workspace can now actually restrict it.
  • AddedThe role editor has a new War rooms permission. Nothing uses it yet, because incident war rooms are still being built, but roles include it from today so it is ready when the feature arrives.
v1.10.4

Move a proposal forward from the proposal itself

10 August 2026
  • ImprovedWhen you opened a project proposal, you could see its stage but had to go back to the list to move it forward. The advance and move-to-production actions are now on the project itself. The status dropdown greys out moves that are not possible from the current stage and shows why on hover, instead of letting you pick one and then rejecting it.
  • ImprovedIn the client portal, status labels used bright colours that stood out from everything else. They now use the same muted colours as the rest of the portal, in light and dark mode. Milestone descriptions also ran straight on from the title; they now start on their own line.
v1.10.3

The client approves the structure first

9 August 2026
  • AddedClients now approve a project’s structure before you price it. If a proposal includes a breakdown of the work, the client signs that off first. You then prepare a budget for what was agreed, and the client approves it separately. The stages are Submitted → Under Review → Structure Proposed → Structure Approved → Budget Proposed → Client Approved.
  • ImprovedThe client portal used to show “Structure Proposed” as the current step with nothing to click, so it looked stuck. Now it asks the client to decide, and every step says whether it is waiting on the client or on your team. Recording a decision on the client’s behalf (with the quick-advance button, by dragging a card between board columns, or from the status dropdown) now asks you to confirm first. Clients often approve by phone or email, so you can still record it, just not by accident.
  • FixedA proposal could be moved into production without client approval. Also, any workspace member could rename or delete project statuses, task statuses and project roles through the API, whatever their permissions. Both rules were only enforced in the app. The server now enforces them too.
v1.10.2

The budget a client asked for

9 August 2026
  • FixedA project requested through the client portal showed a budget of zero in the app, even though the client had entered an amount. The amount was saved in one budget field and read from another. The Budget tab now shows it as the client’s proposed budget, and one click sets it as the estimated cost. It stays separate from the cost you agree internally, so the client’s original request is kept after you price the project. The budget tile in the project overview now shows the proposed amount instead of “of 0”.
  • FixedBudgets submitted through the client portal are now saved in your workspace’s currency. Until now every workspace saved them in euros, so an amount a client entered in dollars was recorded as euros. The budget field on the project request form also shows which currency to use; before, it showed none.
  • ImprovedA proposal waiting on your team no longer looks like it is waiting on the client. The portal’s progress steps now show whether the current step is with you or with the client, and a proposal with a proposed structure explains what happens next instead of just saying “Processing”.
v1.10.1

Start a project from a template

9 August 2026
  • AddedA project’s Tasks & Milestones tab can now start from a template. Pick a ready-made plan and its milestones and tasks are spread between the project’s start and end dates, with each task given time in proportion to its estimated hours. These are the same templates as in the new-project wizard, now available for existing projects too, including empty proposals from the client portal. You can edit everything before adding it: change a title, move a date, or remove a row.
  • AddedA template is added alongside anything already in the project. Nothing existing is changed or removed, so you can add a template to a plan you built by hand. If the project has no dates yet, the dialog asks for them and saves them with the plan, so you do not have to go to another tab.
  • FixedProposals submitted from the client portal showed a string of letters and numbers instead of the sender’s name in the project’s activity, both for your team and for the client in their portal. Client approvals, rejections and revision requests had the same problem. Names are now saved correctly; entries from before today show “Unknown user” instead of the code.
v1.10.0

A shared canvas on every project

Major release
9 August 2026
  • AddedEvery project now has a whiteboard. The people assigned to the project and the client can draw on it together, with freehand, shapes, text and sticky notes, and see each other’s drawing and cursors live, without waiting for a save. The same board is in the desktop app, the web dashboard and the client’s portal, so you no longer need to send screenshots.
  • AddedSave a sketch as a revision to freeze it at that moment. This matters for approvals: when a client approves a revision, they approve exactly what they saw, even if the board has changed since. Clients approve or reject with a note, and restoring a revision puts the board back for everyone at once. Shapes, text and freehand drawing are available now; image uploads will come later.
  • FixedUploaded files and activity entries from project presets showed the wrong name for the person who did the work. Both looked for a first and last name that workspace records do not have, so they showed the account that created the item instead, or “Unknown” if it had no name. Names saved before today keep the old value; new ones are correct.
v1.9.0

Matching pages by similarity

Major release
8 August 2026
  • AddedThe timer can now recognise a page by its overall similarity to your projects, not only by words it shares with your tasks. Before, a window with no words in common with any task got no suggestion, and that is most windows. The timer now compares the page with each project’s work, entirely on your device, and suggests the closest project when it clearly stands out from the rest. It never logs time this way, never overrides a task already matched by words, and suggests at most once an hour for any one website or app.
  • ImprovedBefore release we tested it on all 190 pairs of the built-in project plans. The projects it suggested this way were correct 99.9% of the time, and on pages about work the workspace does not have, it suggested a wrong project 0.4% of the time.
v1.8.2

The same check for suggestions

8 August 2026
  • ImprovedThe check “Is this window about work you actually have?” used to apply to logged time only, yet every wrong match we investigated came through suggestions. Now it applies to suggestions too: a project is suggested only if the words it recognises cover enough of what is on screen. Words are counted across the whole project, so two tasks matching the same word count as one match.
  • ImprovedOne exception is deliberate. When the page title says nothing and only the web address identifies the page, there is no title to check. In the Play Console, for example, the tab is called “Dashboard” and the identifying words are in the address. In those cases the suggestion must instead pass the second opinion and match a website you linked to the project.
v1.8.1

Fix for the self-calibrating threshold

8 August 2026
  • FixedAn hour after release we found a flaw in the new self-calibration: it could report the edge of its allowed range as if that were a measured value. In a workspace with two projects, the confidence threshold it calculated fell below the range and was raised to the minimum. That was looser than the previous fixed value, so a feature meant to make time logging stricter made it less strict, on the very machine it was tested on. And in workspaces created from our project templates, the reference set of “work you don’t do” contained work the workspace does, which pushed the suggestion threshold to its maximum and switched suggestions off. Now, when the workspace does not provide enough data, the timer keeps the previous value and records which value it could not calculate.
v1.8.0

The timer sets its own confidence threshold

Major release
7 August 2026
  • AddedInstead of a fixed number we chose once, the timer now calculates its confidence threshold from your workspace. Every few minutes it scores your task titles against your projects and checks two things: what a correct match looks like and what the best wrong match looks like. The threshold is set above the best wrong match. Tested with 481 tasks describing work deliberately left out of a workspace, this halves wrong time logging, from 11.4% to 5.6%, while still recognising 98.7% of what it recognised before.
  • AddedIf your projects are too similar to tell apart by their words, the timer now says so and stops logging time automatically instead of guessing. Everything becomes a one-click suggestion, and the reason is saved in the session record.
  • ImprovedThis work revealed two problems with how we measured accuracy. A task title that appears word for word in two projects cannot be matched to one of them, and counting it as a failure raised the threshold for every other window. And workspaces built from our templates were compared against those same templates, so the “work you don’t do” reference contained work they did.
v1.7.4

Shared words now count, with less weight

7 August 2026
  • ImprovedUntil now, a word used in two of your projects was ignored completely, which is why a project called “Website Design” could not use the word “design”. Now each word is scored by how strongly it points to one project, adjusted for how many projects you have. This matters most with few projects: with two projects, a word used equally in both tells the timer nothing, but it used to look half useful. Across the twenty built-in plans the timer now recognises 459 of 481 task titles, up from 452, with no new wrong matches.
  • ImprovedWords that appear everywhere, such as your product’s name or a milestone every project has, now count once per project rather than once per task. They get the low weight they deserve and can no longer act as the second piece of evidence that leads to a wrong task.
v1.7.3

One word is not enough to suggest a project

7 August 2026
  • FixedWhen suggesting a project, a word that appeared in only one of your tasks was still treated as strong evidence because it was rare in your workspace, even if it was an everyday word. In 19 hours of real use the timer asked 379 questions, and 264 of them were each triggered by a single common word: “monitor” on UptimeRobot, “console” on cron-job.org and on our own status page, “model” on GitHub, and “links” in Google Search Console. All five suggested the same unrelated project. Suggesting a project now requires two different matching words, which the correct matches already had.
  • ImprovedQuestions based on a website or app you had linked to a project were correct all along and are unchanged.
v1.7.2

App names must match exactly

7 August 2026
  • FixedWe introduced this bug in v1.7.1. The change that made “Claude Code” match its program also let a single word from a longer name match the wrong program. “Visual Studio Code” contains “Studio”, which was enough to match Android Studio, so a website project could suggest its tasks while you wrote Android code. Worse, when two projects claimed the same program, detection switched off for both, including the project that was set up correctly, because each program may belong to only one project. A word now has to match a program’s name exactly.
  • ImprovedThe cost of this fix is that “Android Studio” on its own no longer matches studio64.exe. To make up for it, the detection editor now lists the program names it has actually seen on your computer, so you can pick the right one instead of guessing.
  • FixedThe tasks suggested when a website or app identifies your project no longer keep reordering. Since v1.7.1 they had been sorted by what the page was about, so the list changed as you moved between pages of the same site. Each change restarted the timer’s wait, so the question could take a very long time to appear.
  • ImprovedThe app you are in no longer outweighs what the page in front of you says. A website usually belongs to one project, but an editor or terminal is used for all your projects, so its guess is now shown alongside the page’s guess rather than ahead of it.
v1.7.1

Apps linked to projects now match

7 August 2026
  • FixedApps you linked to a project never actually matched it. The check looked for what you typed inside the program’s name, which only works if the program’s name is the longer one, and it almost never is. People write “Claude Code” and “VS Code”, but Windows reports “claude” and “code”, so neither could ever match. The new session record measured the cost on a real computer: 13 minutes of work in an app correctly linked to that project, and none of it recognised.
  • ImprovedWhen the timer knows the project from the website or app but not the task, it now suggests the tasks the page is actually about. Before, it always suggested the first tasks in the project, so in larger projects the right one was often not among the eight shown.
v1.7.0

A record of what the timer decided

6 August 2026
  • ImprovedThe temporary diagnostic log has been replaced by a proper session record: what the timer saw, what it decided and why, and what you did in response. It stays on your computer, keeps 30 days of entries and deletes older ones automatically. The old diagnostic file, which nothing cleaned up, is deleted the first time you run this version. This lets us measure things we could only guess at before: how much time is logged to work you never confirmed, how often you really switch windows, and how much is logged in the minutes after you return from a break.
v1.6.8

No hours for work a task cannot explain

6 August 2026
  • ImprovedThe timer now checks how much of what is on screen a task actually explains. When most of a window is about something else, the task becomes a one-click suggestion instead of having time logged to it automatically. Tested with 481 tasks describing work deliberately left out of the workspace, this removes a third of wrong time logging, and four fifths of those windows now correctly get no suggestion at all. No correct matches were lost.
v1.6.7

Words in task titles count again

6 August 2026
  • FixedA word shared by two projects was being removed from every task title in the workspace, not just from the project and milestone names where it was shared. With an “Android App” project and a “Website Design” project using the same milestone names, the word “design” stopped working for the project named after it, so a page about design could not be recognised at all. Shared project and milestone names are still ignored, but a word in a task’s own title counts again.
v1.6.6

Diagnostic build

6 August 2026
  • ImprovedTemporary: the diagnostic log also recorded which detection signals reached the timer, and why a website or app linked to a project did or did not match a page.
v1.6.5

Second opinion, re-tuned

6 August 2026
  • ImprovedWe raised the second-opinion threshold again, this time based on pages recorded on a real computer rather than the built-in templates. Measured on the templates, it removes another 30% of wrong suggestions without losing any correct ones.
v1.6.4

Second-opinion threshold reset

6 August 2026
  • ImprovedThe previous release changed what the second-opinion check reads: it now sees the web address as well as the page title. That shifted every score, so the old threshold no longer fit. Reset using real browsing data, the new threshold removes another 40% of wrong suggestions without losing any correct ones.
v1.6.3

Both checks now read the same information

6 August 2026
  • FixedThe second-opinion check saw less than the timer. It only read the window title, while the match itself often came from the web address, so it rejected correct suggestions for lacking evidence it never saw. In the Play Console it rejected everything: Google names those tabs after your own app, so “play” and “console” never appear in the title and only the address identifies the page. Both now read the same information.
v1.6.2

Web address words and small workspaces

6 August 2026
  • FixedThe Play Console dashboard stopped suggesting its milestone. Its tab is just called “Dashboard”, so once the shared product name was correctly ignored, the title said nothing and only the web address identified the page. A rule added two releases earlier rejected that. The rule exists to stop a project being suggested just because you are on its website. It now tells the two cases apart: words describing actual work count wherever they appear, but a project’s own name still does not.
  • FixedThe second-opinion check never ran for anyone with fewer than four projects, which is most people. It was switched off there to avoid a real mathematical problem: with only two projects the comparison becomes a coin toss. The fix uses a fixed reference, calculated once, to filter out wording common to all project work, instead of deriving it from your own project list. The check now works with any number of projects.
v1.6.1

Diagnostic build

6 August 2026
  • ImprovedTemporary: this build logged how task matching made its decisions, so we could study a real problem instead of guessing. The log stayed on your device and has since been replaced.
v1.6.0

A second opinion on every suggestion

Major release
6 August 2026
  • AddedTask suggestions now get a second opinion before you see them. Matching words alone cannot tell a real match from a couple of words that happen to coincide. That is how the marketing site of a time-tracking product could suggest tasks from an Android project, based on the words “time” and “track”. The timer now also checks whether the page actually resembles that project’s work, entirely on your device, and drops the suggestion when it clearly does not. Tested on the twenty built-in project plans, this removes 87% of wrong suggestions without losing a single correct one.
  • ImprovedDirect task matches are deliberately unchanged. They are already reliable, and a second opinion only slightly better than a coin toss would make them worse. So it reviews suggestions only, never logged time.
  • ImprovedWords are now weighted by how much they tell the timer, not by how rare they are. “Stakeholder” is uncommon but appears in half the plans, so it looked distinctive while saying nothing about which project you were in.
v1.5.4

The thinking indicator starts on time

5 August 2026
  • ImprovedThe thinking indicator now starts as soon as productive time starts, not a few seconds later when the timer has something to analyse. Before, it sat still at exactly the moment you looked at it, then started moving for no visible reason. It stops when it finds a task, a suggestion or a question, or after a few seconds of finding nothing. Finding nothing is also a result, so it is shown as a still indicator rather than an endless animation.
v1.5.3

A word shared by project names is not evidence

5 August 2026
  • FixedWhen several projects share a word in their names, such as “TimerOS Android App” and “TimerOS Website”, that word says nothing about which one you are working on. Yet it counted as the second piece of evidence needed to suggest one project’s tasks, while the other project’s tasks were dropped for having only that word. The project the page was actually about could end up with no suggestions at all, so the rule that keeps the timer quiet when two projects are equally likely never got a chance to apply. Such a word no longer counts as evidence.
v1.5.2

Consistent scoring

5 August 2026
  • FixedThe web address and app name were counted at full weight in one part of the calculation and at reduced weight in the other. This made every suggestion look stronger than its evidence, and could let a project recognised only from the address bar outrank the one your window title actually names. Both parts now use the same weight.
  • FixedA suggestion no longer gets full confidence just because it is the only thing recognised. A faint trace of a project, such as its name in a client’s web address on a page sharing no words with any task, could be suggested at maximum confidence, one click away from logged hours.
v1.5.1

When the project is clear but the task is not

5 August 2026
  • ImprovedIn a tool’s own console, such as the Play Console, no single page is about one task, so the timer now weighs the evidence for the project as a whole instead of making its tasks compete. Before, the more tasks a page related to, the lower each one scored, so busier pages gave weaker results. Every Play Console page now suggests the same milestone, not just the dashboard.
  • FixedThis revealed a bug that logged time to the wrong task: when your project is named after the product you work in, its name is in every window title, and one ordinary word plus that name was enough to log hours to the wrong task. A word that appears on every page of a product no longer counts as evidence for any task in it.
v1.5.0

Pinned tasks check in

5 August 2026
  • AddedA pinned task no longer runs all day without a check. If another task clearly takes over your screen for a few minutes, the chip asks “Still on <task>?”. One click keeps the pin, one switches. Your time keeps going to the pinned task until you answer, so ignoring the question is safe.
  • ImprovedOnly a clear, sustained match with another task triggers the question. Searching, reading docs, checking Slack or working in a terminal never will, because that is part of working on any task.
  • FixedA pin now belongs to the day you set it, so tracking past midnight no longer logs today’s work to yesterday’s task.
v1.4.4

Website clues now work

5 August 2026
  • FixedWebsite clues were off for almost everyone: the timer read web addresses only if your workspace had a custom website rule. So task matching could not use the site you were on, the section of its address, a project’s websites or the sites you had confirmed, and the “working on” match did not work in any browser. Turning on automatic task assignment now also turns on address reading, as the previous release intended.
  • FixedWe also fixed three privacy cases in window reading: it now stops however you sign out, not only through Exit; it also stops when you start a break; and a break that failed to end no longer keeps it switched off for your whole next session.
v1.4.3

What the address bar says about your work

4 August 2026
  • AddedIn supported browsers the timer now reads one more clue: the first section of the web address. Tab titles often name the page rather than the tool (the Play Console dashboard is just called “Dashboard”), while the address clearly says /console. It never reads the full address or the query string, and discards it after each check like everything else.
  • AddedWebsites that you or your employer have linked to a project now count as a clue even when the page title says nothing useful: while you are on one, the timer suggests that project’s tasks. It is only a suggestion, and nothing is logged until you choose.
v1.4.2

Matching gaps found in testing and fixed

4 August 2026
  • FixedWe set out to break the earlier matching fixes, found several gaps and closed all of them in this release. Word matching is now stricter and more forgiving at once: a word on screen that is longer than a task’s word matches it only when the extra letters are a real ending, such as a plural or a Bulgarian article like “сайтът”. So “timer” no longer matches “TimerOS”, while product names written as one word and ticket numbers written without the dash match again.
  • FixedThe browser’s name no longer counts as evidence: “- Google Chrome” at the end of every tab title can no longer match a task named after a browser.
  • ImprovedThe “working on” match now treats a product’s subdomains as one site, does not move to a site you visited for only five seconds, and ends as soon as it no longer applies.
v1.4.1

Evidence about the task itself

4 August 2026
  • FixedTask matching could pick a task without real evidence for it. Parts of words no longer count (“time” inside “TimerOS” is not a match), while plurals and Bulgarian word endings still do. A project’s name, its milestone names and its keywords now only point to the project, never to a specific task. To match a task, there must be evidence about that task itself.
  • FixedThe “working on” match no longer follows you across the web. It remembers which site it was confirmed on. There, and in regular apps, it logs time as before, but on an unrelated website it pauses and logs nothing until you return.
v1.4.0

Clues beyond the window title

Major release
4 August 2026
  • FixedThe timer bar now reliably stays on top. It used to get hidden behind other windows while still acting as if it was on top, and the only fix was to click it. It now checks every few seconds whether anything covers it and moves back on top, but deliberately stays out of the way of real full-screen windows such as screen sharing or video.
  • ImprovedTask matching now recognises much more of your work. It compares screen text and task names in both directions, so a short window title can match a long, detailed task name. It no longer penalises you for working ahead of schedule while the project is running. Milestone names, project names, the website you are on and the app you are in now all count as clues.
  • AddedWhen the timer can tell the project but not the task, the chip now shows the project with a question mark instead of nothing, and one click picks the task. Nothing is logged until you do.
v1.3.4

More careful task matching

3 August 2026
  • ImprovedTask matching is now much more careful. The timer considers a task’s description and scheduled dates as well as its title, requires real evidence (two meaningful matching words, or one truly distinctive word), and only starts logging time after the same task has won for a full minute. When it is not confident, the time simply stays productive.
  • ImprovedA task opened inside TimerOS logs time only while it is actually on screen. Closing it no longer leaves the timer thinking you are still working on it.
  • ImprovedTracked hours on tasks now fill in automatically and update live. The number on the Tasks page, in project plans and in the task window is the automatically tracked time, marked with a timer icon. If you type hours in yourself, your number is used and marked with a pencil, and one click switches back to automatic.
v1.3.3

Tracked time on every task

2 August 2026
  • AddedTasks now show their automatically tracked time in a small chip on the Tasks page, in every project’s task and subtask list, and in the task window. It updates live as time is logged, and changes immediately when you assign, reassign or unassign blocks in the Task time panel. Every view reads the same data, so the numbers always agree.
  • AddedFrom the task window, one click copies the tracked total into the task’s reported hours. The chip turns amber when the estimate is reached, but marking the task complete is always up to you.
  • ImprovedThe Unassigned row in the Task time panel now appears whenever there is unassigned time, even on days with nothing logged to a task yet, so you can always allocate it with one click.
  • ImprovedThe “working on” match now ends on its own: after 30 minutes without new evidence, the timer stops logging to the last matched task instead of continuing all afternoon.
v1.3.2

Twenty project plans, scheduled by effort

2 August 2026
  • AddedTen more project presets: design systems, UX research, cloud and data migration, third-party integrations, security audits, product launches, content programmes, recruitment drives and video production. That makes twenty ready-made plans, and they appear in existing workspaces automatically.
  • ImprovedPreset tasks now get realistic dates. Each task gets a share of its milestone in proportion to its estimated hours, so a 60-hour build spans three weeks and a 4-hour setup takes a couple of days. Before, every task in a milestone started and ended on the same two dates.
  • AddedEach milestone shows the planned hours against the hours its dates allow, and warns you when there are too many. You can no longer fit three hundred hours into a five-day milestone without noticing.
v1.3.1

More precise time assignment

1 August 2026
  • ImprovedTime is now logged only to tasks and subtasks, plus incidents and change requests. It is no longer logged to a project as a fallback: when nothing clearly matches, the time stays as plain productive time instead of being guessed onto a project. Blocks already logged to a project still show and can be moved like any other.
  • AddedSubtasks are detected and matched just like tasks, and you can also pin a subtask from the chip in the timer bar.
  • AddedUnassigned time can now be allocated from the Task time panel: one click books the day’s unassigned hours onto the task or subtask you pick.
v1.3.0

Automatic time assignment to tasks

1 August 2026
  • AddedTracked time is now assigned automatically to the task you are working on. The timer compares what is on your screen with your assigned tasks, on your own device and without sending anything. Hours go to the task when it is sure, to the project when that is all it can tell, and stay as plain productive time when there is no clear match. Unassigned time is perfectly normal, and the app never nags you about it.
  • AddedA “working on” chip in the timer bar shows the current match. Click it to pin a task yourself; your pin always overrides the automatic match. A single switch in Settings turns automatic assignment off completely.
  • AddedA Task time panel in the Performance day view shows which tasks the day’s hours went to, block by block, and lets you reassign or unassign any block in two clicks.
  • AddedActivity inside TimerOS counts too. Working with a project, task, incident or change request open in the app logs the time to that item, so support work is tracked alongside project work. Time spent viewing your own performance, payroll or settings is deliberately not logged to any item.
  • ImprovedThe classification dialog now explains each time assignment the same way it explains productive and idle decisions: what matched, how, and why.
v1.2.0

Project presets

1 August 2026
  • AddedStart a project from a ready-made plan instead of a blank page: website design, Android and iOS app development, a SaaS MVP, an e-commerce launch, brand identity, a marketing campaign, an SEO overhaul, client onboarding or a maintenance retainer. Each comes with its milestones and tasks already laid out.
  • AddedYou can change anything before creating the project: rename a milestone, remove a task you do not need, add your own or change the hours. The whole plan adjusts to the project’s actual start and end dates.
  • AddedBuilt a structure worth reusing? Save it as your own preset from the last step of the wizard. Managers can rename, delete and restore presets under Projects → Manage presets.
  • FixedCreating an internal project with a department selected no longer fails. The selected department used to be rejected.
  • FixedMilestones and tasks now keep the order you put them in. A new one added to an existing plan used to jump to the top of the list.
v1.1.1

Sleep and wake tracking

1 August 2026
  • FixedLeaving your computer asleep no longer logs the entire sleep as a break. Only the part inside your shift counts as break time; the hours outside it stay untracked, as the tracking rules always promised.
  • FixedWaking up during your shift now returns the timer to normal tracking right away. It used to keep recording overtime until you signed out and back in.
  • ImprovedBoth problems happened in the first seconds after waking, while the network reconnects. The app now waits for the connection instead of guessing, and uses the last schedule it knew if needed.
v1.1.0

Chat

30 July 2026
  • AddedChat: message your clients and your team without leaving TimerOS. Each client has a conversation that appears in their portal instantly, and chat works in the desktop app, the web dashboard and on your phone.
  • AddedGroup chats that include people from your team and the client contacts you choose, plus team-only group chats and private one-to-one messages visible only to the people in them.
  • AddedInternal notes in client conversations: comments only your team can see, so internal discussion and the client conversation stay in one place.
  • AddedClients can also start conversations from the portal and choose who from your team to include, from the people already working on their account.
  • AddedEdit or delete your own messages, react with emoji, rename or delete conversations, and follow unread counts in the sidebar and the notification bell.
Platform

Dedicated status page

26 July 2026
  • Addedstatus.timeros.ai is a public status page for TimerOS. We check the service every minute from outside our own network, and the page shows the live status of each part, a 90-day history, past incidents and monthly uptime. It runs on separate infrastructure, so it stays up even when TimerOS is down.
  • AddedIf our monitoring stops reporting, the page says so instead of showing an outdated “all clear”, so you can trust it during an incident.
  • AddedThe page also has an Atom feed and a JSON endpoint, so you can follow incidents in a feed reader or add service status to your own tools.
v1.0.2

Portal domain fix

22 July 2026
  • FixedPortal Domain settings now shows and copies the address your clients actually use: your custom domain once it is live, instead of always the free subdomain. The subdomain keeps working, so existing links and older emails still work.
v1.0.1

Right-click and invite fixes

21 July 2026
  • FixedRight-clicking in the desktop app no longer opens the browser menu. Text fields still offer Cut, Copy and Paste.
  • FixedIf your workspace has no free seats, inviting someone now tells you so and explains how to add seats, instead of failing with a generic error.
v1.0.0

Initial public release

Major release
21 July 2026
  • AddedWindows desktop app with a frameless, always-on-top timer bar and the full dashboard. This is where time is tracked: automatic activity detection, idle handling, and hours split into regular and overtime based on scheduled shifts (or simple all-day tracking for solo users).
  • AddedYou control how your time is classified. Mark any app, window title or website (by domain, such as a client’s tool or a distraction) as productive or idle, and switch between Automatic, Rule-based and Manual tracking modes. It all runs on your own computer.
  • AddedThe same dashboard in any browser, on desktop and phone: review and manage projects, teams, clients and reports wherever you are. Time tracking itself stays in the desktop app.
  • AddedProjects, tasks, subtasks and milestones with per-project budgets, plus goals and awards to keep teams motivated.
  • AddedTeam management for growing companies: departments, an org chart, shifts, scheduling and time-off management, approvals, role presets and team performance.
  • AddedClient management and a branded client portal for every workspace. Clients can follow projects, raise support and change requests, and share files, on your timeros.ai subdomain or your own custom domain.
  • AddedInvoicing and billing, including invoices created automatically from project budgets and billable support work, plus expenses, Stripe card payments and a clear profit overview.
  • AddedReal-time updates across the desktop and web dashboards and the client portal: changes appear everywhere without refreshing.
  • AddedOffline support in the desktop app: the timer keeps running if your connection drops and syncs when you reconnect.
  • AddedTwo-factor authentication (TOTP) for workspace users and client portal contacts.
  • AddedPrivacy first: activity classification runs on your own computer and nothing is sent to a cloud AI. Clear monitoring notices and in-app legal documents are built around GDPR and the EU AI Act.
  • AddedLaunched with the Freelancer and Startup plans, both fully supported. Enterprise is in early access, with payroll, custom roles and permissions, full expenses and client SLA tiers available now, and SSO / SAML and an audit log coming soon.
v0.2.7

File name fixes

17 July 2026 · Pre-launch
  • FixedFiles with Cyrillic or other non-Latin names now upload, preview, and download with the correct name.
  • ImprovedThe upload confirmation now shows the name of the file you uploaded.
v0.2.6

Custom portal domains

15 July 2026 · Pre-launch
  • AddedNew Portal Domain settings show the web address your clients use to reach their portal.
  • AddedStartup and Enterprise plans can connect a custom domain to the client portal, with copy-paste DNS records and live verification status.
v0.2.4

Timer bar reliability

14 July 2026 · Pre-launch
  • FixedThe timer bar moves back on top after you unlock the screen, after sleep and wake, and whenever another window takes focus.
  • ImprovedMulti-monitor: the timer bar docks to the top of the monitor you log in from, and stays on that monitor when collapsed, expanded, or dragged.
v0.2.3

In-app changelog

14 July 2026 · Pre-launch
  • AddedSee what’s new in every release from Settings → About.
  • FixedThe login window now shows the real app version.
  • ImprovedInstaller polish: separator line under the title bar, cleaner Welcome and Finish pages.
v0.2.2

Faster update detection

14 July 2026 · Pre-launch
  • ImprovedThe app now checks for updates every 30 minutes and whenever the dashboard window regains focus.
  • ImprovedThe full warm-paper installer look now covers every page.
v0.2.1

Silent updates

14 July 2026 · Pre-launch
  • ImprovedUpdates now install silently: no installer window, the app just restarts on the new version.
  • AddedBranded installer with TimerOS artwork, in English and Bulgarian.
  • ImprovedSmarter update checks: automatic retry after a failed check, plus a check when the dashboard opens.
v0.2.0

Automatic updates

14 July 2026 · Pre-launch
  • AddedTimerOS checks for new versions, downloads them in the background, and offers a one-click restart.
  • AddedSettings → About now shows the real installed version and a Check for updates button.
v0.1.0

First desktop build

4 July 2026 · Pre-launch
  • AddedInitial release of the Windows desktop app.

Versions before 1.0 were pre-launch builds of the Windows desktop app, shipped while TimerOS was in final testing ahead of the public launch.

Follow what’s next

The roadmap shows what we’re building now that v1.0 is out, and what we’re not building yet.

See the roadmap