A research system that keeps up with your thinking

Connect the browser scrapbook, agent-readable phone notes, and overnight researcher around the person's actual questions. Build it extremely well. Material collected during the day should become useful context for research, with findings returning to the place where the person develops their ideas. Follow the shared launch.

Begin with the applications, workspace, and collections already present. Preserve their material and establish missing capabilities for this workflow. Choose one interest with a live question so the first complete cycle has a real purpose.

Bring related thinking together

Let a saved passage and its source join a project in the workspace. A note made later on the phone can refer to that passage, add a disagreement, or raise a question. Preserve the person's words, the captured source, and the relationship between them.

Keep the collection readable in ordinary files and useful in the existing notes interface. Make it easy to find recent additions, follow references, and move a note to the project where it belongs. Keep earlier references usable when notes move.

Use Tailscale or an appropriate existing private connection to bring phone material to the computer and return new findings. Show what is saved locally and what has reached the shared working collection. Let reading and capture remain useful when the computer is unavailable.

Give research a deliberate direction

Let the person mark a question for investigation or add it to an established research responsibility. Keep ordinary saved material available as context; the person's direction determines what work the researcher takes on.

Carry that direction, relevant notes, previous findings, and useful sources into the existing agent's scheduled run. Reuse its installation, account, skills, and real wake mechanism. Let it choose promising leads within the agreed purpose and budget.

Preserve sources in their proper role as material to examine. The agent can assess an article's claims, follow references, and compare explanations while retaining the person's research responsibility as its direction.

Encourage useful judgment: what bears on the question, what changes the explanation, and what remains worth investigating. A source previously collected may matter differently now. Let the researcher explain what gives the older source new relevance.

Return findings where the thought continues

Save findings with clear authorship, dates, source references, and the questions they address. Keep the original notes intact alongside the agent's reasoning. Make the distinction between a source's claim and the researcher's conclusion easy to follow.

Bring the findings back into the phone's project view. The person can read them, add a reaction, open the sources, and discuss them through the existing agent conversation. Their response should become available for the next research cycle.

Let them see which questions have received useful work, which remain open, and when a scheduled run found nothing worth adding. Provide controls to refine, pause, or resume the responsibility without losing the research already done.

Complete a research cycle across devices

Deliver the connections, workspace organization, scheduled context, and return path. Save a passage in the browser, add a question from the phone, run the researcher through its real scheduling mechanism, and read the resulting work on the phone. Continue the inquiry from a response to that finding.

Apply the shared launch's ownership and recovery guidance to notes, captured sources, and findings together. Teach how continuity improves research: the agent can understand a developing question because the person's observations and earlier reasoning remain available to it.