Obsidian Copilot: Bring Your Own API Key
Obsidian + Copilot is where your work actually lives. The review unit sat on a desk, then in a backpack, for three weeks before any of the numbers below made it into writing. During that time it handled the same routine as everything else: calls in the morning, documents through the day, and the usual admin that fills the gaps. What follows is daily use, not the launch material.
What it gets right
The headline figure is Storage: Local Markdown files. It matters, but not in isolation. Plugin (Copilot (community)) is the number you feel after a long session, and Models (Bring your own key (any OpenAI/Anthropic)) decides whether this stays in the bag after a year of travel. The three trade off against each other, so the one you actually notice depends on how you work.
What the numbers miss
| Specification | Value |
|---|---|
| Storage | Local Markdown files |
| Plugin | Copilot (community) |
| Models | Bring your own key (any OpenAI/Anthropic) |
| Privacy | Local-first, vault on disk |
| Pricing | Obsidian free; model API cost only |
Weight is the obvious start. Obsidian + Copilot is of note, and that stops being abstract after a week of commutes. A few hundred grams is the difference between a bag you forget and one you notice on every staircase. Pick it up next to what you use now; the one you would rather carry up four flights is usually the right answer.
Comfort and build
The spec sheet is honest about Storage, but quieter on sustained use. In a realistic work session, Plugin settles toward the middle of the claimed range rather than the headline. That is normal, and still a step up from most alternatives. The gap between peak and sustained is where comparisons fall apart: two devices can post the same maximum and feel different after six hours.
Setup and daily use
Comfort and build separate the category. The materials and hinges on Obsidian + Copilot hold up to daily packing, and surfaces that touch skin stay neutral after hours. These details never make a launch event, yet they decide whether gear lasts three years or disappears after one trip. Hinges in particular fail first, so solid on day one means little if they loosen by month three.
Value and pricing
Setup decides whether you actually use the extra capacity. Obsidian + Copilot works best when the configuration stays out of the way: pair it and let it switch between devices. Anything that needs fiddling every morning will get left on the desk, however impressive it looks in a review. Firmware support matters too; steady updates age better than a perfect launch with no long-term maintenance.
How it compares
Value is the lens most often skipped. Listed at , Obsidian + Copilot sits among alternatives with the same premise. Paying more only makes sense if it buys something you use every week; paying less only works if the compromise stays outside your routine. Most buyers overspend on a number they never reach and underspend on the build that determines lifespan.
The trade-off
Against the rest of the category, Obsidian + Copilot is not trying to win every test. It targets a specific routine, starting with Pricing, and that focus is why it works for the people it works for. A jack of all trades makes too many small compromises and gets replaced first; Obsidian + Copilot trades breadth for depth, which is visible the moment you use it for its intended purpose rather than a generic checklist.
- Storage (Local Markdown files) is the number to memorise.
- Plugin (Copilot (community)) is what you will notice every day.
- Build quality shows up first at the joints and hinges.
- Compatibility with the rest of the kit is worth checking before buying.
Who it is for
Bottom line: Obsidian + Copilot does what it claims, and the claims sit close enough to the measured values to be trusted. Buy it if the numbers match how you actually work, and you will use the extra capacity every week. Skip it if you need the extremes of the spec sheet every single day, because that headroom costs money and weight without changing your routine.