Command-line tool for managing your AT Protocol bookmarks. Works with kipclip.com and any app that uses the same record format. kipclip.com
atproto rust kipclip bookmarks tags toread atprotocol
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Clarify CLI independence from website, explain PDS and record format

+15 -6
+15 -6
README.md
··· 1 1 # kip 2 2 3 - Command-line interface for [kipclip.com](https://kipclip.com) — an AT Protocol bookmark manager. 3 + Command-line tool for managing your AT Protocol bookmarks. Works with [kipclip.com](https://kipclip.com) and any app that uses the same record format. 4 4 5 5 Read, add, tag, and manage your bookmarks from the terminal. Bookmarks are stored on your personal PDS using AT Protocol, so they stay yours. 6 + 7 + kip talks directly to your PDS — it doesn't go through kipclip.com or any other server. The website and CLI read and write the same data, but neither depends on the other. You can use kip without ever visiting the website, and your bookmarks will still show up there if you do. 6 8 7 9 ## Install 8 10 ··· 57 59 58 60 ## How it works 59 61 60 - kip authenticates via AT Protocol OAuth (PKCE + DPoP) using the [jacquard](https://crates.io/crates/jacquard) Rust SDK. Bookmarks are read from and written to your PDS directly. URL metadata (title, description, favicon, image) is extracted client-side by fetching and parsing the bookmarked page. 62 + On [AT Protocol](https://atproto.com), your data lives in your Personal Data Server (PDS) — a repository of records that you own. Apps don't store your data in their own databases; they read and write records in your PDS. This means any app that understands the same record format can work with the same data. 63 + 64 + kip authenticates via AT Protocol OAuth (PKCE + DPoP) using the [jacquard](https://crates.io/crates/jacquard) Rust SDK, then talks to your PDS directly. URL metadata (title, description, favicon, image) is extracted client-side by fetching and parsing the bookmarked page — no server involved. 65 + 66 + ### Records 67 + 68 + Your bookmarks are stored as records in these AT Protocol collections: 69 + 70 + - **`community.lexicon.bookmarks.bookmark`** — the bookmark itself (URL, creation date, tags). This is a shared lexicon, so other AT Protocol apps can read your bookmarks too. 71 + - **`com.kipclip.annotation`** — enrichment sidecar (page title, description, favicon, image, notes). Shares the same rkey as its bookmark so they stay paired. 72 + - **`com.kipclip.tag`** — tag records for organizing bookmarks. 61 73 62 - AT Protocol collections used: 63 - - `community.lexicon.bookmarks.bookmark` — bookmark records 64 - - `com.kipclip.annotation` — enrichment + notes sidecar 65 - - `com.kipclip.tag` — tag records 74 + Because these are just records in your PDS, you can inspect them with any AT Protocol tool, export them, or build your own app on top of them. 66 75 67 76 ## License 68 77