Get AI summaries of any video or article — Sign up free
A quick tour of Capacities (2023) thumbnail

A quick tour of Capacities (2023)

Capacities·
5 min read

Based on Capacities's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Capacities treats every piece of information as an “object,” including built-in types (links, PDFs, tweets, audio) and custom types like recipes, quotes, and books.

Briefing

Capacities organizes personal knowledge around “objects” and then connects them through bottom-up linking—so content becomes a navigable network instead of a folder hierarchy. Every piece of information in Capacities is treated as an object: built-in types cover things like pages, web links, PDFs, tweets, files, and audio, while users can create custom object types such as recipes, quotes, and books. Objects can carry properties (for example, a book card can include a cover image, author, and reading status), and those properties can link to other objects—like an author field that jumps to a person object with its own backlinks to the book.

The app avoids folders entirely. New content is created quickly from anywhere by typing the object type and name, even inline while writing. That design supports a network mindset: instead of deciding where something “belongs” in advance, users relate it after the fact by adding links, tags, and collections. This is where Capacities shifts from simple categorization to relationship-driven organization. A recipe object can be attached to a collection (such as Mediterranean recipes), tagged with multi-select attributes like cuisine, and linked to other recipes it “goes well with.”

To make those relationships visible, Capacities includes a graph view that visualizes the local network around a chosen object. In the recipe example, the graph highlights related tags, linked media, and the collection membership, turning metadata into an explorable map of ideas.

A final layer ties the network to time: daily notes. Recipes can include a “cook” property that stores the date last cooked; clicking that date opens the corresponding daily node in a calendar layout. Daily nodes show reflections and notes written on that day, plus references to related content created or interacted with—such as the recipe cooked, other items collected, tags added, and screenshots saved. Daily notes also function as a lightweight planning and journaling space: users can jot to-dos, capture snippets encountered during the day, review what happened, and apply templates like a “daily routine.” Activity tracking (sport, reading, audiobooks, and more) can link back to the underlying objects, such as assigning a task to write a chapter in a specific book.

Capacities also integrates external input. Email, Telegram, and WhatsApp can send messages, voice recordings, files, and images directly into daily notes—turning everyday capture into structured memory. A WhatsApp quote and a photo, for instance, can land in the day’s node, while an email newsletter can be forwarded to create a reference for later listening.

Beyond this tour, the app points to features like fast full-text search, import/export in multiple formats, a powerful editor, and a mobile app in testing. The pitch centers on community feedback: Capacities is positioned as a tool built with user input, with a Discord community offered for collaboration.

Cornell Notes

Capacities treats all information as “objects,” including built-in types (links, PDFs, tweets, files, audio) and custom types like recipes, quotes, and books. Objects can store properties and link to other objects—for example, a book’s author field can open a person object with backlinks to the book. Instead of folders, users organize through bottom-up linking: tags, collections, and explicit links create a network of related ideas, visualized with a graph view. Daily notes add a chronological layer, letting users browse what happened on a specific day and see references to objects created or used then. Integrations (email, Telegram, WhatsApp) feed messages and media into daily notes to keep capture-to-structure friction low.

How does Capacities define and organize “objects,” and why does that matter for knowledge management?

An object is any meaningful “thing” in a user’s world, and all content lives as an object. Capacities includes built-in object types such as generic pages and media types like web links, PDFs, tweets, files, and audio. Users can also create custom object types—for example, recipes to store favorite dishes, quotes to remember lines found in reading or on Twitter, and books to track what’s being read. Because objects can have properties (cover image, author, reading status) and those properties can link to other objects (author linking to a person card), the system builds connections automatically through relationships and backlinks rather than relying on a single location like a folder.

What replaces folders in Capacities, and how does that change how people should structure information?

Folders are removed from the workflow. Instead, users create content first and then relate it through linking and tagging. The approach is bottom-up: start from the content being worked on, then add links in the form of tags, collections, or direct links to other objects. For instance, a Shawarma recipe can be added to a “Mediterranean recipes” collection, tagged with cuisine cultures/regions using a multi-select property, and linked to other recipes that pair well with it. This creates a network of ideas where relationships matter more than top-down placement.

How does graph view help users understand relationships between objects?

Graph view provides a local visualization of all related content around a selected object. In the recipe example, the graph highlights tags connected to the recipe, shows media links associated with it, and includes the collection membership. The result is a quick way to see how an item connects to other parts of a knowledge base—turning metadata into an explorable map rather than a static list.

What role do daily notes play, and how do they connect back to other objects?

Daily notes act as a chronological hub for planning, journaling, and reviewing. A recipe can include a “cook” property containing the date last cooked; clicking that date opens the corresponding daily node in a calendar layout. That daily node can show reflections and notes written that day, plus references to related objects—such as the recipe cooked, other items collected, tags added, and screenshots saved. Daily notes also support to-do lists and templates (like a “daily 60 Minute communication routine”), and activity tracking (sport, reading, audiobooks) can link back to objects such as a book for a writing task.

How do integrations like WhatsApp, Telegram, and email fit into the object-and-link workflow?

Integrations let users send content directly into daily notes. Email, Telegram, and WhatsApp can deliver messages, voice recordings, files, and images straight to the day’s node. For example, a WhatsApp quote can be captured into daily notes, and a photo sent from WhatsApp can appear there as well. Email newsletters can be forwarded into daily notes to create a reference for later use, keeping capture tied to the same object-based system.

Review Questions

  1. When a book’s author field links to a person object, what additional navigation benefit appears through backlinks?
  2. How does bottom-up linking (tags, collections, direct links) differ from organizing content with folders in Capacities?
  3. What mechanisms connect a recipe to a daily note, and what kinds of information can appear inside a daily node?

Key Points

  1. 1

    Capacities treats every piece of information as an “object,” including built-in types (links, PDFs, tweets, audio) and custom types like recipes, quotes, and books.

  2. 2

    Objects can store properties and link to other objects, enabling connected cards such as a book linking to an author/person object with backlinks.

  3. 3

    The app avoids folders; users create content quickly and then organize it through bottom-up linking using tags, collections, and explicit links.

  4. 4

    Graph view visualizes the local relationship network around an object, showing tags, media links, and collection membership in one place.

  5. 5

    Daily notes provide a chronological layer for reflections, to-dos, templates, and activity tracking, with references back to related objects.

  6. 6

    Email, Telegram, and WhatsApp integrations feed messages, media, and files directly into daily notes to reduce capture friction.

  7. 7

    The system is designed for community-driven iteration, with users encouraged to join a Discord community to shape the product.

Highlights

Every content item becomes an object, and properties can link to other objects—turning metadata into navigable relationships.
Instead of folders, organization happens through bottom-up linking (tags, collections, and direct links) that builds a network of ideas.
Daily notes act like a time machine: clicking a date property opens a calendar day with references to what was created or used then.
Graph view turns connections into a visual map, making relationships between recipes, tags, collections, and media easy to scan.
WhatsApp, Telegram, and email can push quotes, photos, and files straight into daily notes for structured capture.

Topics

Mentioned