Thymer

Most people’s working lives are scattered across at least three apps: one for notes, one for tasks, and a database-flavored tool for the projects that outgrow both. Thymer, from the Thymer Team, wants to collapse that stack into a single document. It calls itself an “IDE for tasks, notes and planning,” and the label is accurate. Integrated development environments win programmers over by keeping files, search and commands one keystroke away. Thymer applies the same logic to meeting notes, project plans and personal to-do lists.

The project is built by Wim Cools, a co-founder of Papyrs, so it comes from someone who has already shipped collaborative workspace software. That background shows in the engineering choices. The editor was written from scratch instead of being assembled from an off-the-shelf text component, and it treats outlining and long-form writing as equals inside the same page. Tasks, dates and tags are typed inline. Collections turn ordinary pages into lightweight databases. Real-time collaboration, end-to-end encryption, offline sync and a two-way bridge to plain Markdown files sit underneath it all.

That bundle is the pitch. Productivity tools usually pick a lane: fast outliner, flexible database, private local-first vault, or collaborative team wiki. Thymer tries to occupy all four lanes at once, then adds optional AI hooks without making them mandatory.

The ambition comes with caveats that matter for anyone deciding today. Thymer is in beta, and access runs through a waitlist. The iOS and Android apps are still in testing. Android distribution runs through Google Play open testing, with no public store rating to lean on. Pricing isn’t final: the service is free for now, and roughly $10 per user per month is planned for commercial teams. Self-hosting isn’t available yet. We weigh the Android release in that context, as an early look at a desktop-first tool reaching for the phone.

• Hybrid outliner and long-form editor: Indent, fold and zoom into any bullet, then write paragraphs of prose in the same document.
• Inline planning syntax: Type [ ] to create a task, @friday to schedule it, and #tag to file the page. Notes and to-dos live in the same text.
• Collections: Pages become simple databases with table, board, calendar and gallery views.
• Panels and command palette: Open pages side by side, and reach nearly every action through a searchable palette and keyboard shortcuts.
• Real-time collaboration: Shared team workspaces with simultaneous editing, live cursors and presence.
• End-to-end encryption: Covers pages, files and images.
• Offline-first sync: Work continues without a connection and syncs once the device reconnects.
• Markdown Mirror: Two-way sync between the workspace and a folder of Markdown files on your computer.
• Optional AI: Bring your own model, use the AI Terminal, or connect agents through MCP.
• Extensibility and safety nets: Plugins, themes and automatic backups.

The Editor Is the Product

Thymer’s central bet is that the text editor is the right place to organize work, and that tasks, schedules and databases should grow out of it. Writing that editor from scratch is the expensive way to make the bet, and it is the right way. Outlining and long-form writing pull in different directions. One rewards hierarchy and collapse; the other rewards flow. Thymer declines to make users choose. A single page can hold a dense bullet tree of a project’s open questions with three paragraphs of reasoning beneath it.

Zoom is the underrated part. Any bullet can become the root of the view, which turns a sprawling outline into a set of focused workspaces without splitting content across separate pages. Combined with side-by-side panels, zoom supports the reference-and-write pattern programmers take for granted: spec on the left and implementation on the right, or meeting notes on one side and the project plan on the other.

The command palette completes the IDE comparison. Putting nearly every action behind a searchable command and a shortcut keeps hands on the keyboard and keeps toolbar clutter off the page. The cost is discoverability. Palette-driven design rewards users who already know what they want and penalizes those who learn by browsing menus. Thymer is plainly built for the first group. We think that is the correct call for its audience, but it adds onboarding friction for everyone else.

Planning as a Side Effect of Writing

The inline syntax does the most to justify Thymer’s existence. A task typed with [ ] in the middle of meeting notes stays in the context that produced it. Copied into a separate task manager, the same task would lose the reasoning around it. Anyone who has stared at a bare entry like “follow up with vendor” and wondered which vendor, about what, will see the appeal at once.

The same design lowers capture friction. Adding a task, date or tag means typing a few characters, with no form to fill, no modal to open and no app switch. The trade-off is that a planning system built on markup depends on users remembering the markup, which is another reason Thymer favors the keyboard-fluent.

The notable gap is recurring tasks. Thymer doesn’t build them in; a community plugin called Supertask adds them. For a tool that wants to replace a dedicated task manager, missing native recurrence is a real hole, because weekly reviews, bill reminders and standing check-ins are basic planning needs. The plugin route proves the extension system works. Core planning behavior still shouldn’t depend on third-party code.

Collections: Databases Without the Ceremony

Thymer calls Collections simple databases, and the qualifier matters. They add enough structure to track a reading list, a content calendar or a hiring pipeline without leaving the document environment. The four views cover the common cases: tables for scanning fields, boards for status-based workflows, calendars for anything dated, galleries for visual material.

Individuals who want light structure layered over their notes should find that scope appropriate. Teams that model complex relationships across many datasets should treat “simple” as a warning label rather than modesty.

Privacy, Portability and Collaboration

Three features address the question every workspace app eventually faces: who controls the data?

End-to-end encryption covers pages, files and images. Pairing it with real-time collaboration, including live cursors, presence and simultaneous editing, is the hard engineering combination here, because the sync service handles content it cannot read. For teams handling sensitive material, offering both is a serious commitment. Offline support completes the picture. Editing doesn’t depend on a live connection, and changes sync on reconnect.

Markdown Mirror is the feature we would single out as Thymer’s smartest. It keeps the workspace in two-way sync with a folder of Markdown files on the user’s computer. Notes therefore exist as plain text outside Thymer. They can be edited in other tools, searched with standard utilities, put under version control and recovered if the service ever goes away. Lock-in is the silent tax of most workspace apps, and Markdown Mirror largely removes it. Automatic backups add a second safety net.

Self-hosting is the missing piece. It isn’t available yet, and that will matter to organizations with strict data-residency rules, encryption or not.

AI on Opt-In Terms

AI is optional, and the options are developer-friendly: bring your own model, use the AI Terminal, or connect agents through MCP. That is the right structure for a privacy-focused product. Users who want no AI get none, and users who want it choose the provider instead of accepting a bundled one. MCP support shows Thymer expects external agents to read and act on a workspace, which fits the IDE framing.

There is a design tension worth stating plainly. Unless the chosen model runs locally, sending workspace content to it moves that content outside the encrypted boundary. Thymer’s opt-in approach puts that decision with the user, where it belongs, and users should make it deliberately.

Thymer’s visual design follows its IDE framing. Text and structure take priority, controls retreat into the command palette, and themes let users restyle the workspace. That approach suits long stretches of writing and planning, where interface chrome competes with content. The weakness is the same one noted above: a palette-first interface gives newcomers fewer visual cues about what the app can do.

On performance, we can speak only to design. A from-scratch editor gives the team full control over input handling and rendering. That control matters most for the workloads Thymer encourages: long documents with deep nesting, frequent folding and zoom. The offline-first architecture means editing doesn’t wait on the network. On a phone, end-to-end encryption also means the device does the cryptographic work itself. How the Android beta copes with very large workspaces remains an open question while the app is in testing.

• Distribution: The Android app is a beta delivered through Google Play open testing, and access to Thymer runs through a waitlist. It has no public store rating yet.
• Input method: The command palette, keyboard shortcuts and side-by-side panels are central to Thymer’s design, and all three favor a physical keyboard and a wide screen. On a touchscreen phone, the app loses its biggest ergonomic advantage.
• Inline syntax on touch: [ ], @ and # still beat filling in task forms. On most phone keyboards, though, they sit on a secondary symbol layer, so capture is less fluid than at a desk.
• Markdown Mirror: The feature is described as syncing with a folder of Markdown files on your computer, which makes it a desktop feature by design. Android users benefit indirectly through workspace sync.
• Offline and encryption: The phone is where offline work matters most, on commutes and flights. Offline editing that syncs on reconnect, combined with end-to-end encryption, suits mobile use well.
• Pricing: Thymer is free during the beta. The planned commercial pricing of about $10 is framed per user per month, not per device.
• Recommended role: Treat the Android app as a companion for capture, review and quick edits alongside the browser or desktop versions on macOS, Windows or Linux, not as a primary workspace.

Thymer gets the hard parts of the design right. Treating planning as something that happens while writing, instead of in a separate app, solves a real and common problem, and building a custom editor around that idea shows conviction. End-to-end encryption, offline sync and Markdown Mirror add up to an unusually strong answer to data-ownership concerns. The opt-in AI respects users who want none of it while giving technical users real hooks through MCP.

Maturity and fit hold the score back, and they hold it back hard. The Android app is a beta reached through a waitlist and open testing, on a platform where Thymer’s keyboard-first interface works against touch input. Recurring tasks depend on a plugin, self-hosting hasn’t arrived, and pricing is still a plan rather than a commitment. For most people, that is too many open questions to build a working life around. We recommend Thymer only to keyboard-driven individuals and privacy-conscious teams willing to adopt early, with the Android app as a companion to the desktop or browser version. Anyone who needs a finished, phone-first task manager today should join the waitlist and wait.