Tasks & Projects

Structure. Project → branches (sub-projects, one level deep) → sections → tasks → steps. A branch is part of its project and moves with it. A project may hold only notes and still be a real project. Steps are counted on their task, never as tasks of their own.

Focus is not a date. Putting a task into Focus or taking it out never touches its deadline. A task set to in progress anywhere is in Focus automatically. It stays there until you finish it or remove it.

Sessions. The timer lives inside Focus (the old Pomodoro page opens Focus, and a session that was running keeps running). A focus session records its real minutes; a task shows how many sessions and minutes went into it. While a session runs, the head shows today and this week. Every fourth session of the day is followed by the long break unless you choose otherwise. When a task has not had a session for a few days, its card opens with Where you stopped — a line OnePuls writes and you can correct.

The session summary (stage B). Every session gets one, a session without a task too: its minutes and what got done in its time — steps and tasks closed, materials saved, what your own AIs did over MCP — read from what PulsOne recorded, never asked for; and Where you stopped. Another session on the same task (without a task — the same project) within two hours adds to the same summary: «50 min · 2 sessions». When something got done, one progress record goes into the project's History. Nothing to fill in.

The session feed (stage B, desktop app on Windows only). With Feed switched on next to Done, the app notes which programs and windows you worked in while a session runs — Feed is recording · steps stay on this computer, with Pause feed. The steps never leave the computer (encrypted, erased after 7/30/90 days). After the session its feed waits in Focus: remove any row, then Send — or it goes by itself in ~10 minutes; Leave the feed out drops it. OnePuls then writes a short Summary and Details (the work told by its parts) into the session's summary; you can Edit them or ask OnePuls to add to them. The team never sees it.

What to take next. One rule for the project's What next and for Focus: in Focus, deadline within a week, the task you touched last, in a starred branch, in progress. Focus also names quieter reasons — quick, a later deadline, an open question. When nothing of the chosen project is in Focus, Focus offers one task with its reason and Take and start.

Materials. For this task shows up to three saved links: those saved on the task first, then the project's ones that match it by words. Not it hides one under this task for good. Links the Telegram bot is still asking about are never shown.

Thoughts find their place. There is no Backlog to tend. Anything you capture — in the Island, in Focus, during a session, in its summary, or from OnePuls and your own AI — goes to the archivist, and it files the thought by itself: decisions, questions and thoughts become History, ideas go to the project's Ideas, and something to find out becomes a Find out task. It first decides where the thought belongs across all your projects. Thoughts from a session wait about ten minutes before they are filed, so you can change where they go; everything else is filed every 15 minutes. Each thought shows a label like idea · PulsOne › Marketing; click it to move the thought. Ideas go further — a piece of an idea you already have, or a new idea on its step; the session summary's To ideas shows where each went, with not that (see Ideas).

Inbox — only what the archivist could not settle. A project's Inbox tab appears with a count when something waits, and disappears when it is empty. Three kinds of rows, each with where it came from (a session, you, OnePuls, Claude, ChatGPT…) and when: not sure where (pick one of 2–3 places, then Accept · Not needed · Later), decisions disagree (a new decision contradicts the one in force — Keep … · Replace with the new one · Later; an AI never overturns your decision on its own) and looks like a duplicate (two open tasks — Merge makes the newer one a step of the older, nothing is deleted; Keep both). Later hides a row until tomorrow. Every settled row leaves a service step in History (visible under All); the tab shows Sorted today: N → to History. There is no input field.

Suggestions, never silent changes. From what you said, OnePuls may suggest a step, a task or an idea — with the reason — in the session review and on the Overview. Nothing changes until you press Apply, and Undo is right there. Tasks untouched for 60 days, with no deadline and no open steps, are listed as Not touched in a while — a rule, not the AI.

The project's memory. The Overview is the snapshot (mockup 3-01), in white cards: Where you are — OnePuls's summary in large type, the line that changed since your last look marked, «you were away 3 days», «updated by OnePuls · 09:12 · versions» — with the project's History under it (Main / All, «2 new since last time», five steps that open into why, was → became and how it was done, All history); What next — up to three tasks with their reason, the first one starts a session right away; Open questions, answered right there or taken into work as a Find out task; OnePuls's suggestions to the plan; Branches with ★ and «2 in Focus · yesterday». Your last look is remembered on this device (src/lib/projectSeen.ts). Team day (stage B, B6; mockup DtInb) opens the Overview of a shared project: Today · Yesterday · Week; links between people one line each, only when there is one — two in the same stage, an agent waiting for an answer (Answer opens the task), someone's open question; then a card per person or AI with only the lines that are not empty — Did (closed tasks and steps by stage, credited to whoever closed them — tasks.completed_by, set by the database — else the assignee, else nobody), Decision (from History, with the reason and time), Result, Asked (an agent's question and the answer), Stuck, Next (the next open step of the task worked on last) — and the time from focus sessions on this project. Built by rules from rows the team already shares; the minutes come from project_team_day. Admin and manager see everyone; a member sees only their own card, and your card says «how the team sees you». More detail on a card asks OnePuls to connect the same lines into a few sentences — from those lines only, shown in the card, not saved. The session feed and private thoughts are never shown. History is the one feed of what happened. All of it is selected from what was actually recorded — your words, closed tasks, settled hypotheses — the screen never invents a sentence. What your own AI wrote into the project over MCP is there too, under its name and logo: a note it made (Main), a note it changed and a task it added (All), its questions and the answers they got — read from the write receipts (aiWritesIn in src/lib/projectSpine.ts). Find what you need with the search (by words for now — by meaning comes with stage A's backend) and the filters: kind (Done · Decisions · Dead ends · Tools · Results, the rest under more; a kind with nothing in it is not offered), Who and Period; picking a kind shows all of it, not only Main. When the project has stages (stage A, docs/stage-a-data.md) there is also Stage (with its smaller steps) and Topic, each row says its stage and topics, a record written in another language shows in yours with translated from EN (click — the original), and correct fixes its kind, stage or topics — never the text (src/lib/historyFilters.ts, src/lib/historyEditApi.ts; the correction is bench-only until the migration). Build a report in History's header opens a wide window (mockup 3-03): on the left the brief — period (week / month / your own dates), for whom (myself / client / manager / team), what to include (done, decisions and why, what's next, open questions, time and sessions, how it went), tone and length, and your own request with + deadlines, + risks, + no numbers; on the right a white A4 sheet. Nothing is written until you press Build: OnePuls then writes the sheet live from the History's records for the period. Change the brief and Update takes the lead («brief changed»); the sheet as it is can still be downloaded. Download saves a PDF or a .md. Save the brief as the «Client» template keeps the brief for that audience — picking it next time fills the brief in. The report is not stored; nothing is written into History.

Materials. A saved link — a video, an article, a reel, a post, a file — lies where you saved it: on a task, on a project, or on the shelf Sort later. In an open task, + material → paste a link → Save: the type and the app show at once, the page's own title comes back with the saved link. A project's Notes tab has a Materials filter: the project's links, its tasks' and its branches', grouped by type, each with the place it lies on; ⋯ moves a link (to the task in Focus, a project, Sort later) or removes it. In the Island, a bare link — or a link with a few words and no question — goes to Sort later; a question about a link goes to OnePuls. With PulsOne installed on an Android phone, Share → PulsOne opens a sheet with three places — the task in Focus, the project touched last, Sort later — and one tap saves. Search through an aggregator (Recall, Remly, Glean…) is listed, but cannot be connected yet.

On hold. Put on hold folds a project, with its branches, into the On hold box. Its tasks leave Today and the counters, and OnePuls remembers it but does not bring it up. Its page stays readable under a veil with Back to work.

Moving in. /projects/move brings work over from Todoist, Notion, Evernote, ChatGPT or Claude and plain files, in three steps. From: pick several apps at once; each gets its simplest way in — an export file, a phrase for your own AI connected to that app over MCP, or a prompt for your AI chat whose answer you paste back. Nothing is read while you add files or paste: Next reads them all at once (a row says «added — read on Next» until then), and stays on From when nothing could be read. What to take: everything found, by app. One project kept in two apps arrives as one (merged: Notion · Todoist), duplicate tasks fold, and a project with the name of one you already have goes into it. One project is ticked by default; All at once is a box you tick yourself. Open tasks untouched for 90+ days are Put off in the move and go to the project's ideas unless you take them. Where to start: done tasks keep their dates, so they sit in History on the day they were done; stated decisions and questions become History entries dated as in the source; notes become project notes. OnePuls writes a first summary, you put 1–3 tasks into Focus, and Undo the move deletes exactly what the move made.

Moving in from code. Picked GitHub and Claude Code: connect PulsOne to Claude Code once (one line in the terminal; Cursor and Codex take the same link) and say Move this project to PulsOne in the project folder. Claude Code reads the code, git, pull requests, issues and its own sessions on your computer — they never leave it — and sends a draft; the screen waits for it (Claude Code is reading…) and goes on by itself. What to take shows the project by stages (how it was built): each record with its kind (Result · Decision · Dead end · Tool · Question), its receipt (a PR, an issue, a commit, a session) and its date; a decision in your own words; replaced → yt-dlp where you changed your mind. Not sure comes unticked. The CLAUDE.md note can become the project's Instructions for AI by a tick. Foundation and ideas puts each idea in its pillar › branch; an idea off the foundation comes only when ticked; empty pillars are named. A line says how much was taken from how much («41 records out of 1 214 commits, 312 PRs and 180 sessions»). Where to start shows Ideas found their place in the foundation (the pillars with their ideas, the empty ones with Come up) and Keep recording: Claude Code shows three lines for CLAUDE.md and, after your yes, saves each session's decisions, dead ends and results. Moving again from the same repo brings only what is new. A claude.ai export (ZIP) brings its projects — instructions as a note for AI — and its chats as topics.

Team. A project can be shared with a small circle: Settings → Team → Make it a team. Invite copies a one-use link for 7 days (nothing is emailed); whoever opens it signs in and is in. Roles: Admin (everything, access included — the owner always is one), Manager (tasks, assignees, decisions), Member (own tasks, thoughts, answers). The project, its branches, sections, tasks, History and notes are shared; ideas, materials, Atlas and Inbox are not yet, and Focus stays personal. Tasks get an assignee — a person, or one of the owner's AIs set to Executor with the person who answers for it; a task for an AI needs What should come out. The Tasks tab filters Mine · All · Unassigned. Make it yours only takes everyone out at once; what they wrote stays. Others' changes arrive when you come back to the tab and every 90 seconds. Details: docs/team.md.

AI Agents. A project's own agents on the person's own server — Claude Code, Codex, Gemini CLI, Cursor or a script. The tab sits between Tasks and Ideas, in solo and Team projects alike, and lists the agents, their server, and whether it is online. + Agent connects a server once (npx -y https://pulsone.app/runner-<version>.tgz connect <code>, the code lives 10 minutes), then picks one of the agents that server's runner allows and the folder on the server it works in for this project. Branches share their project's agents. The agents, the model keys and the compute stay on the person's server; PulsOne can start only what the runner's config.json lists. Servers are renamed or disconnected in Settings → Account → AI agent servers. Giving a task to an agent is picking it in Who does it — in solo projects too; the task needs What should come out. It starts within seconds: the drawer shows the agent working, short lines of Progress and the full log, and Stop. When the agent hands it in, the drawer and the task row say handed in · check it: Accept closes the task, Return (with an optional note) sends it back for another go. The tab shows what each agent is doing now — working on a task, queued, busy in another project, online or offline — and Handed in · check. An agent that cannot go on without a decision asks: the task shows {agent} asks with the question, one-tap choices and a field for one's own answer; the same question waits at the top of the project's Inbox and on the phone. The agent goes on with the answer, and the question and the answer stay in History as a decision. Questions come only from agents — people talk in their own messenger (docs/ai-agents.md).

Elsewhere. A task's deadline puts it on that day in the Calendar; a calendar block gives it an hour. Projects can carry goals (see Goals), and a project can have its own AI in OnePuls. On a phone, /projects shows a phone layout of the same data. Focus (the task now and «Дальше», across projects) has its own address, /focus; on a phone it lands on «Сегодня», where the current task lives.