Entries are the basic unit of information in Distill. Each entry represents a single piece of thought– an idea, action, decision, or note. They are designed to be short and atomic, but can also be extended into longer text when more detail is required.
Entries exist to:
Capture information quickly, with minimal friction.
Keep individual thoughts small and easy to connect.
Provide consistent input for threads and agents to work with.
Creating entries
You can create an entry from the main editor in your vault, or from within threads when you are adding replies to entries. Entries can be used in several ways, including but not limited to:
Ideas: Capture hypotheses, questions, or sparks of inspiration.
Inspiration: Save links, images, or screenshots.
Actions: Record tasks or next steps.
Decisions: Note choices along with rationale.
Editing entries
You can edit, delete entries and access other entry properties by clicking the main "dot" on the left side of the entry.
Threads
Entries can exist independently, or they can be grouped into threads. Reply to an entry to form a thread. This creates continuity of thought over time.
Adding replies to an entry creates a thread.
Entries can be added directly into an existing thread.
Agents can connect entries across threads when relationships are detected.
Threads can be used in various ways:
Ongoing conversations: Develop ideas through back-and-forth discussion.
Project tracking: Follow the evolution of a project from initial idea to completion.
Problem solving: Work through complex issues step by step.
Documentation: Build comprehensive records of processes or decisions.
Attachments: Add images or links. Agents can process and summarize this content.
Agent mentions: Mention an agent by name (e.g. @Analyst) to request specific actions such as summarization or list-making.
Agent interaction
Agents work with entries to provide higher-level outputs:
Summarization of one or more entries.
Extraction of action items.
Organization of related entries into lists.
Identification of patterns across time and projects.
Best practices
Keep entries short whenever possible.
Record decisions at the time they are made, including rationale.
Use replies to grow threads rather than rewriting old entries.
Attach supporting material (links, images) directly to entries instead of storing separately.
Use agent mentions when specific help is required.