Help center
Detailed product guidance that is available directly inside the portal for signed-in and signed-out users.
Guide 1
Getting around the portal
Today is the home base. It surfaces quick-add actions, today's work, recent logbook context, points, and shortcuts into the areas that are enabled for your account.
Execution groups the places where work is actually done: tasks, habits, checklist runs, and training sessions. The Capture menu starts new recordings, transcripts, notes, links, and logbook entries. Import / Export lives in the account menu with other utilities.
Feature access can hide optional areas. Help, Settings, points history, and the account menu remain available so you can still understand the portal and manage your account.
Guide 2
Tasks and Today
Tasks are quick-capture items with priority, category, due date and time, tags, optional subtasks, recurrence, and drag ordering. Draft tasks stay in Tasks until you move them into a real category.
Due tasks are grouped into overdue, today, upcoming, no-date, and completed sections. Recurring tasks generate the next instance when completed, and recurring instances can be skipped.
Today pulls together overdue, current, planned, and executable work so the task list remains the place to organize while Today remains the place to act.
Guide 3
Points and levels
Points are recorded in a reversible ledger. Completing a task grants +1, a positive habit completion grants +2, and completing a planned checklist grants +2.
A completed day grants +5. Each 7-day completed-day streak milestone grants +7, and every fourth consecutive weekly streak milestone grants an extra +5.
If the underlying completion is undone, the related points are revoked. Levels are derived from the current total: level 1 is the default, level 2 starts at 10 points, and later thresholds grow by 30%.
Guide 4
Checklists and execution sessions
Checklists are reusable todo lists with relational tasks. You can edit checklist tasks, add one level of subtasks, detach a task from a checklist, or delete it entirely.
A planned date lets a checklist participate in Today and points. The planned date is separate from execution history.
Checklist execution starts a session with start and end timestamps. Check and uncheck events are stored per session so a checklist can be reused while each run keeps its own history.
Guide 5
Audio, recordings, and transcriptions
New Recording uses the browser MediaRecorder when available. Saved recordings can keep their system file name and optional custom name, and Telegram-origin recordings appear with a source badge.
New Transcript can use an uploaded audio file or a saved recording. Completed transcriptions show the original transcript, formatted notes, and analysis editors.
When a transcript is complete, Create Task from Audio creates a draft task linked back to the recording and transcription so the source chain remains visible.
Guide 6
Telegram and Google Calendar setup
Telegram: make sure the API has TELEGRAM_BOT_TOKEN configured and the bot is running. In Telegram, send /link, copy the generated code, then open Settings -> Telegram integration in the web app and claim the code. After linking, use Telegram's command menu or the /help keyboard for /task, /add_task_text, /add_task_2, /add_log, /tasks_status, /points, /agent, and wake commands.
Google Calendar: an admin must configure GOOGLE_CALENDAR_CLIENT_ID, GOOGLE_CALENDAR_CLIENT_SECRET, GOOGLE_CALENDAR_REDIRECT_URI, and APP_SECRET_ENCRYPTION_KEY, or save the OAuth client values from Settings. Then each user opens Settings -> Google Calendar and connects their own Google account.
Only dated tasks can be exported to Google Calendar from the task detail panel. Google-side edits sync for events created by this app; unrelated calendar events are not imported into Tasks.
Guide 7
Logbook and chapters
Logbook supports multiple personal logbooks. Each logbook can have named chapters, and entries can be saved directly to the logbook or into a chapter.
The dashboard shows only logbooks marked for dashboard visibility. Capture can save recent notes without leaving Today.
Logbook entries can be exported as Markdown from Import / Export, and a log line can be converted into a linked task.
Guide 8
Training plans and workout history
Training plans store ordered exercises with planned sets, reps, weight, rest, and notes. Plans can be created, edited, duplicated, deleted, and exported as Markdown.
Starting a workout creates a training session from a plan. Sessions store planned versus actual values, session notes, timezone context, and optional gym or location metadata.
Training history lets you review completed sessions. The mobile app also includes a Training tab for browsing plans, starting sessions, updating values, and reviewing history.
Guide 9
Import and export tools
Import / Export is the transfer hub. Tasks can be exported and imported as JSON; imports ignore exact duplicates and update existing tasks when imported content differs.
Todo-list Markdown import parses a checklist draft and sends it into the new checklist flow. Logbooks and training plans can be exported as Markdown.
Admins can also run exercise catalog sync from this area when training features are enabled.
Guide 10
Settings and feature access
Settings manages profile details, avatar upload, password changes, Telegram linking, Google Calendar connection, and admin-only feature activation.
Admins control the global feature map. Turning a feature off removes its navigation and access for users, including admins, but Help, Settings, Today, and account controls stay available.
Registration can also be enabled or disabled by admins. Suspended users can log in and see a banner; banned users are blocked at login.
Guide 11
Admin tools
Admins can list users, change roles, and update user status. Admins cannot suspend or ban themselves.
Admin Overview shows infrastructure health for the backend, Supabase, Whisper, and the Telegram bot, plus summary metrics for transcriptions, prompts, and users.
User list endpoints are paginated. Non-admins only receive their own user entry from user-list APIs.
Guide 12
Agent, avatar, documents, Gantt, and prompts
Agent stores one personal agent profile with name, optional age and gender, an agent-owned image avatar, and optional video-avatar selection from My Avatar.
Documents are a personal rich-text workspace with create, edit, delete, and public access keys through the documents MCP server. Gantt charts manage project timelines and dependencies with app-owned controls.
Prompt templates store reusable prompts and must include the pasted_text placeholder. Avatar provides the visual avatar preview and related experimental controls.
Section 1
How habits work
This section is hardcoded in the portal and available to every visitor, including signed-out users. It explains the current behavior of the habit system, the principles behind its design, and how those principles can help users get results.
What a habit is in this portal
A habit is a personal recurring practice that you track over time. Each habit has a cadence of daily, weekly, or monthly, a target count for the period, and positive or negative events that record how the period actually went.
The habit record is not just a counter. It stores planning context as well: a color label, category, anchor or cue, minimum action, if-then plan, obstacle plan, motivation note, and your custom button labels.
How tracking works
Every time you interact with a habit, you create an event. Positive events move the habit forward. Negative events capture misses, setbacks, or breakdowns in execution. The system aggregates those events into current-period totals, streaks, balance, and recent consistency.
Positive events support three completion levels. Minimum means you did the smallest version that still counts. Target means you completed the normal expected version. Bonus means you exceeded the target or did extra work beyond the standard expectation.
How planning fields are meant to be used
The anchor or cue defines when the habit should happen, for example after breakfast or before bed. The minimum action defines the smallest acceptable win. The if-then plan turns the habit into an explicit response: if the cue happens, then you perform the action.
The obstacle plan is the fallback you want to see when execution gets difficult. The motivation note is your short reminder of why the habit matters. Together these fields make the habit easier to start, easier to recover, and easier to interpret later.
Principles behind the habit system
The habit design in this portal is based on a few practical behavior principles. First, repetition tied to a stable cue is easier than relying on motivation alone, so the system asks for an anchor. Second, small actions lower resistance, so every habit can define a minimum version that still counts. Third, explicit plans improve follow-through, so the habit can store both an if-then plan and an obstacle plan.
Another core principle is recovery over perfection. The product tracks streaks and consistency in a way that rewards returning after a miss instead of treating one bad period as failure. It also separates minimum, target, and bonus completions so users can see whether they are merely keeping the behavior alive, meeting the intended standard, or going beyond it.
How these principles help produce results
Results usually come from repeated execution that survives low-energy days, interruptions, and normal inconsistency. A clear cue makes the behavior easier to remember. A minimum action makes it easier to begin. A target defines the normal standard. An obstacle plan reduces friction when reality gets in the way. Recovery tracking keeps users from abandoning the habit after one weak period.
Over time, this structure improves both adherence and interpretation. Users can tell whether a habit is actually becoming stable, whether the target is realistic, and whether progress is coming from frequent minimum completions or solid target-level execution. That makes it easier to adjust the habit design and get measurable outcomes instead of collecting vague activity.
How streaks and consistency are calculated
A streak is based on whether the current and previous periods contain at least one positive event. It does not require perfection. This keeps the habit system oriented around continuity rather than all-or-nothing tracking.
Consistency over the last seven periods measures how many recent periods had at least one positive event. Recovery marks the current period when you returned after missing the previous period. Minimum, target, and bonus counts are also broken out separately so you can see the quality of execution, not just the volume.
How to use habits well
Start with a cue you already encounter reliably, keep the minimum action small, and treat target completions as the default level instead of the minimum. Use bonus only when the extra effort is real, otherwise your data becomes harder to read.
If a habit stops moving, update the obstacle plan before changing the whole habit. If a habit keeps getting logged as minimum only, that is usually a design signal: the target is too ambitious, the cue is weak, or the environment is fighting the behavior.