Sync collections and higlights from Linkwise to your vault.
The official Obsidian integration for Linkwise. Effortlessly sync your saved links, AI-generated summaries, key questions, live highlights, and curated collections directly into your vault as clean, native Markdown notes.
🗺️ <Collection>) that stands apart from the links it indexes — a 🗺️ map marker in its name, a summary callout with a live link count, and a #linkwise/moc tag.📝 Note: This plugin requires an active Linkwise Pro subscription.
main.js, manifest.json, and styles.css from the GitHub Releases page..obsidian/plugins/ and create a new folder named linkwise.Setting up the sync connection is quick and secure. Choose one of the two options below to pair your vault.
lw_pat_…).⚠️ Important: This token is only displayed once. Store it securely or regenerate a new one if lost.
You can trigger a manual synchronization at any time using three different methods:
Cmd/Ctrl + P) and running "Linkwise: Sync now".Upon completion, a native notification will display your sync summary (e.g., "Linkwise: sync complete — 24 new, 3 updated"). If you prefer a hands-off approach, you can configure an Auto-sync interval in the settings to pull updates in the background.
The plugin preserves your Linkwise organization by mapping your collections directly to vault folders. Unfiled links are neatly placed into an Unsorted directory.
Linkwise/
├── Research/
│ ├── 🗺️ Research.md # Map of Content — hub linking every link in the collection
│ ├── Agent Harness Engineering.md
│ └── Attention Is All You Need.md
└── Unsorted/ # For links not yet assigned to a collection
├── 🗺️ Unsorted.md # Map of Content for unfiled links
└── ...
ℹ️ Upgrading from an earlier version? Legacy index notes (a plain
MOC,<Collection> (MOC), the collection name itself, or the old_MOC) are renamed to🗺️ <Collection>automatically on the next sync — no duplicates, nothing lost.
Each collection folder contains a Map of Content — a fully managed 🗺️ <Collection> note that wikilinks every link in the collection. The 🗺️ marker in its name makes it pop in the graph and file explorer, and its title comes straight from the filename (no redundant heading):
---
linkwise_moc: true
collection: "Research"
tags: [linkwise/moc]
---
> [!info] Map of Content
> Index of the **Research** collection : 12 links.
- [[Agent Harness Engineering]]
- [[Attention Is All You Need]]
Run Linkwise: Set up graph colors (Command Palette, or the button in settings) to color these hubs distinctly in the graph view. See Graph Colors below.
Every synced note features rich properties (frontmatter) and a clean sections layout. When Linkwise has a cover image for the article, it's shown at the top (toggle: Show cover image, on by default). Notes start straight at the summary:
---
linkwise_id: "cf2cf531-..."
title: "Agent Harness Engineering"
url: "https://addyosmani.com/blog/agent-harness-engineering/"
source: "addyosmani.com"
collection: "Research"
tags: [ai, agents]
highlight_colors: [yellow, purple]
saved: 2026-06-16
cover: "https://..."
---
<img class="linkwise-cover" src="https://addyosmani.com/assets/images/agent-harness.jpg" alt="Cover image" referrerpolicy="no-referrer">
## Summary
The AI-generated summary text appears here...
## Key Questions
**A core question the article answers**
The AI-generated answer detailing the concepts...
## Highlights
<blockquote class="linkwise-highlight" data-color="yellow" style="border-left: 4px solid #FEF08A;">
A sample passage you highlighted while reading inside Linkwise.
</blockquote>
*Your personal annotation or thought attached to this specific highlight.*
## My Notes
Write anything you want here! Your thoughts, permanent links, and deeply structural outlines belong down here. This section completely survives all future syncs.
To keep your data intact while allowing for seamless updates, the plugin uses a strict boundary rule:
## My Notes is managed by Linkwise and will be refreshed during synchronization.## My Notes belongs entirely to you. The sync engine will never overwrite or alter anything in this section. Do not modify or delete the ## My Notes header itself.Collections form little hub-and-spoke clusters in Obsidian's graph: the 🗺️ <Collection> Map of Content hub in the center, its links around it. By default every node is the same color, so the hub blends in. The Set up graph colors command fixes that.
Run it from the Command Palette (Linkwise: Set up graph colors) or the Graph colors button in settings. It adds two color groups to your graph configuration:
tag:#linkwise/moc) — violet, so hubs pop out.path:"<your vault folder>") — muted slate.The command is non-destructive: it only adds groups whose query you don't already have, and never edits or removes color groups you set up yourself. After running it, close and reopen the graph view to see the new colors. Prefer different colors? Adjust them any time under Settings → Graph view → Groups.
| Setting | Description | Default |
|---|---|---|
| Personal Access Token | The unique lw_pat_… authentication token generated from your mobile app. |
None |
| Vault Folder | The target directory path where all Linkwise notes will be written. | Linkwise |
| Auto-Sync Interval | The frequency at which the plugin checks for updates in the background. | Manual only |
| On Deletion Strategy | How to handle notes when their corresponding link is removed from Linkwise. Options: Mark (appends linkwise_deleted: true), Trash (moves to _trash folder), or Ignore. |
Mark |
| Show cover image | Show the article's cover image at the top of each note (when one exists). Applies to newly synced notes; reset the sync state to re-apply to every note. | On |
| Graph colors | One-click button that adds graph color groups so collection maps stand out from notes. Non-destructive. | N/A |
| API Base URL (Advanced) | Custom endpoint configuration. Only modify if self-hosting or testing locally. | Production API |
| Reset Sync State (Advanced) | Clears the local sync cursor. The next sync will re-evaluate all items, gracefully merging changes without creating duplicates. | N/A |
| Issue | Root Cause & Resolution |
|---|---|
| "Invalid or revoked token" | Your access token has expired or been revoked. Generate a new token in the Linkwise app and update it in your plugin settings. |
| "Obsidian sync is a Pro feature" | The account paired with the token does not have an active Linkwise Pro subscription tier. |
| "Already up to date" / No notes sync | No new items have been saved, or existing notes haven't changed since the previous sync session. |
| Notes are missing | Double-check that the plugin is fully enabled and verify the absolute path configured in the Vault Folder setting. |
| Need a full fresh sync | Go to Settings → Reset sync state, and then run Sync now to forces a comprehensive rebuild. |
| Deleted highlights persist | Known limitation: A highlight removed in isolation will update in Obsidian the next time its parent article undergoes an edit or re-sync. |
.obsidian/plugins/linkwise/data.json file. If your vault is hosted on a shared sync network, treat it with the same caution as a password. You can revoke it instantly inside the mobile app.Get the local developer environment up and running with standard npm operations:
# Install package dependencies
npm install
# Run the project in development/watch mode
npm run dev
# Run type-checking and generate production-ready bundle
npm run build
# Run code linter
npm run lint
The codebase is structured modularly within the src/ directory:
main.ts: Handles the main lifecycle events and initialization hooks of the Obsidian plugin.settings.ts: Implements the UI configurations panel and settings parsing logic.api.ts: Manages network requests and data framing with the Linkwise data endpoints.sync.ts: Core processing engine responsible for handling differential pulls and local document writes.markdown.ts: Parser tasked with parsing boundaries to merge upstream changes into your custom files cleanly.This project is licensed under the terms of the MIT License. See LICENSE for details.