What is in the beta

TaskTreker is in beta, and this page states what works today, what is in progress and what is not there yet. The statuses come from the code and the findings register. Capture with sources, the missed-items list, the context graph, the harness with nine prompts in two languages, the universal path and the MCP server work. Payment, connecting the connectors to capture and a separate digest screen are in progress.

The honest state of the product: what works, what is in progress, and what is not there yet.

Already working

These parts of the assistant are implemented and can be used now. Each line links to the guide that explains how.

What it is	Status	Guide	What that means
Capture: extraction of facts, tasks, decisions and insights from a meeting transcript	Works	/guides/capture-setup	The assistant extracts candidates and keeps the source of each one. Only what a person confirmed enters the context.
The missed-items list: what was said but never became a task	Works	/guides/first-week	A separate list with the source of every item and a confirmation step. How a candidate is judged significant is a formula, not the model's opinion (ADR-0016).
Context instead of a folder of notes: goals, hypotheses, assumptions and decisions with history	Works	/guides/first-week	The assistant answers "why did we do this" and links the answer to the source it came from.
Harness: nine prompts, agent instructions, rituals and templates, in Russian and English	Works	/guides/harness-prompts	Prompts are versioned, and every version is scored against a quality bar.
The universal path: import and export in Markdown, JSON and CSV	Works	/guides/capture-setup	For stacks that have no connector: the context can be brought in and taken out as files.
A live sizing document with assumptions and a version for the sales conversation	Works	/guides/sizing-document	Decisions and numbers have to be explainable; the document shows why each figure is what it is.
Artifacts for the handoff to sales and to development	Works	/guides/handoff	The package is assembled from the accumulated context, and each artifact keeps its source.
An MCP server over your own company data	Works	/guides/mcp-setup	External agents can ask questions about the data that is already in the assistant.
A bilingual product: interface, harness and prompts in Russian and English	Works	—	The product is English-first, and the Russian version is complete rather than partial.

In progress

These parts are announced in the roadmap of the product, but they are not finished. We do not promise what is not there yet.

What it is	Status	Guide	What that means
Capture from external sources: Notion, GitHub, Confluence and the other connectorsFinding in the register: T-83	In progress	/guides/capture-setup	The connectors are registered and covered by contract tests, but they are not yet wired into the capture pipeline. Until then, channels are filled manually or with demo data.
The daily digest ritual runs on its own schedule	Works	/guides/first-week	The ritual "Daily digest" delivers the digest into the app. Every run is recorded in the journal: a skip or a failure is visible instead of being lost silently. Delivery to email and chats is honestly marked as unsupported — the product has no sender for them (ADR-0023).
The digest in the interface	Partly	/guides/first-week	The digest is delivered into the app on schedule, but there is no separate screen for it: it is read through the API.
Background reading of connected channelsFinding in the register: T-83	In progress	/guides/capture-setup	Automatic polling of connected sources is part of the same work as connecting the connectors to capture.
Payment and subscription managementFinding in the register: F5-3	In progress	/pricing	The price list in roubles is approved, but the payment path is not wired up yet.
What is included in Free, 299 ₽, 499 ₽ and 999 ₽, and what the limits areFinding in the register: F1-08	In progress	/pricing	This is an open decision in the PRD: we will announce the breakdown before the public beta instead of publishing a guess.
A demo that works without registration, in Russian as wellFinding in the register: F5-6	In progress	/guides/first-week	Demo channels can only be enabled after registration, and only with English synthetic content.

Not there yet

An honest list. The absence of a feature is information too: it is better to know it now than to discover it later.

What it is	Status	Guide	What that means
Version numbers and release dates	Not there yet	—	There is no release process yet, so changelog entries carry no labels. Made-up versions and dates do more harm than their absence.
A customer-facing analytics dashboard	Not there yet	—	Metrics are collected inside the product, and the analytics screen is shown to the product owner only. It is not a client dashboard.
Public limits per tariff and per plan	Not there yet	/pricing	The limits are decided together with the payment path; publishing them before they are decided would be a guess.