Skip to content
Agentmart
Submit a tool

bearcli

Read and write notes in the Bear app (macOS) from the command line using bearcli.

Skill by rcedwards

IndexedMIT
Write a review

Chalk Labs

Need help deploying bearcli?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/rcedwards-bearcli

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Read and write notes in the Bear app (macOS) from the command line using bearcli. Use when the user asks to find, read, create, edit, tag, pin, archive, trash, or restore a Bear note, search Bear notes, manage attachments on a note, or otherwise wants "Bear" (the notes app) content looked up or changed. Also use when the user says "bearcli", "my Bear notes", "search Bear", or references a note by title that sounds like a personal note rather than a code file.

Use cases: writing, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/bearcli

What's inside

Skill name
bearcli
Description
Read and write notes in the Bear app (macOS) from the command line using bearcli. Use when the user asks to find, read, create, edit, tag, pin, archive, trash, or restore a Bear note, search Bear notes, manage attachments on a note, or otherwise wants "Bear" (the notes app) content looked up or changed. Also use when the user says "bearcli", "my Bear notes", "search Bear", or references a note by title that sounds like a personal note rather than a code file.
License
MIT
Instructions
152 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# bearcli

## Overview

`bearcli` reads and writes notes in the Bear app's local database. It runs on the binary bundled
inside the app: `/Applications/Bear.app/Contents/MacOS/bearcli`, and is also on `PATH` as `bearcli`
after Bear has been installed. There's a separate `mcp-server` subcommand for MCP clients (Claude
Desktop) — ignore it here; this skill is for direct CLI invocation.

Every note is identified by `<note-id>` or `-t/--title <title>` (case-insensitive), mutually
exclusive. Most commands accept `--format tsv|csv|json` (default tsv) and `--fields f1,f2` or
`--fields all`. Read commands never mutate state; write commands (`create`, `append`, `edit`,
`overwrite`, `tags add/remove`, `pin add/remove`, `trash`, `archive`, `restore`, `attachments
add/delete`) print nothing on success — the exit code is the signal (0 success, 1 business error,
64 usage error). Use `--format json` on a read first if you need to confirm what a write will
touch.

Get the full reference any time with `bearcli help all` or `bearcli help <subcommand>`.

## Quick workflow

1. Find the note: `bearcli search "<query>"` or `bearcli list --tag <tag>` to get its id/title.
2. Read before writing: `bearcli cat` (raw content) or `bearcli show` (structured fields) to see
   current state, and `bearcli outline` if you'll target a specific section.
3. Write with the narrowest tool that does the job — `tags add`/`pin add` for metadata, `append`
   for adding, `edit` for a targeted find/replace, `overwrite` only when replacing a whole note or
   section.
4. Confirm with a follow-up `cat`/`show` if the result matters.

## Finding notes

```bash
bearcli list                                    # all notes, sorted pinned,modified
bearcli list --tag work --sort modified:desc
bearcli list --count                            # just the match count

bearcli search "meeting notes"                  # free text
bearcli search "@today @todo"                   # Bear search syntax (dates, tasks, tags...)
bearcli search "@todo" --format json --fields id,title,matches
```

Search syntax highlights: `#tag`, `!#tag` (exact, no children), `#*/tag` (subtags only),
`@today`/`@last7days`/`@date(2026-01-01)`, `@todo`/`@done`/`@task`, `@tagged`/`@untagged`,
`@pinned`, `@images`/`@files`/`@code`, `-` to negate any term. Full syntax:
https://bear.app/faq/how-to-search-notes-in-bear/

## Reading notes

```bash
bearcli cat <id>                                # raw content, no escaping
bearcli cat --title "Mars"
bearcli show <id> --format json --fields all    # structured metadata (not content by default)
bearcli outline <id>                            # every section's address + byte range
bearcli search-in <id> --string "TODO"          # exact-match occurrences within one note
```

`show`'s default fields are `id, title, tags`; pass `--fields all,content` to include the body.
`cat --format json` returns `{"content":"...", "hash":"..."}` — that hash is what `overwrite`'s
`--base` checks against, so read before an `overwrite` if the note might have changed elsewhere.

## Section addressing

Many commands take `--section <address>` to scope to one part of a note instead of the whole
thing. An address is one or more heading lines (with `#` markers, written as they appear), joined
by `\n` when a heading name repeats and needs an ancestor to disambiguate, optionally ending with
a 1-based index. A trailing `preamble` line addresses a section's lead text above its first
subheading.

```
"## Install"               a uniquely-named section
"# Setup\n## Install"      the ## Install under # Setup, when it repeats elsewhere
"# Build\n## Install\n2"   the 2nd ## Install under # Build
"## Install\npreamble"     the lead text of ## Install, above its first subheading
```

Run `bearcli outline <id>` to get exact, copyable addresses instead of guessing — a missing or
ambiguous address comes back with a helpful error suggesting what to retry with.

## Creating and writing

```bash
bearcli create "My Note" --content "Body text" --tags "work,draft"
printf "line1\nline2" | bearcli create "My Note"        # --content reads stdin when omitted

bearcli append <id> --content "New paragraph"            # default: end of note
bearcli append <id> --section "## Tasks" --content "- [ ] New task"

bearcli edit <id> --find "TODO" --replace "DONE"
bearcli edit <id> --find "## Notes" --insert-after "\nNew line"
bearcli edit <id> --find "obsolete paragraph\n" --delete
bearcli edit <id> --find "cat" --replace "dog" --all --word --ignore-case

bearcli overwrite <id> --content "# Title\nBody"          # whole note; unconditional without --base
bearcli overwrite <id> --section "## Tasks" --base <hash> --content "## Tasks\nRewritten body"
```

`edit` finds an exact string and replaces/inserts-around/deletes it; repeat `--find` with a
following action for atomic batch edits (all apply or none do). `--section` confines every `--find`
so a string that recurs elsewhere in the note still resolves uniquely. `overwrite` replaces the
whole note or one section (heading included) — pass `--base <hash>` from a prior `cat --format
json` if another edit landing concurrently should abort the write; CLI callers may omit it.
Both `edit` and `overwrite` reject a change that would silently drop an attachment unless you pass
`--force` (the rejection message names the files).

Text arguments (`--content`, `--find`, `--replace`, etc.) interpret `\n \t \r \\`; **stdin does
not** — pipe pre-formatted text in as-is.

## Tags, pins, attachments, lifecycle

```bash
bearcli tags list                               # every tag in use
bearcli tags list <id>                          # tags on one note
bearcli tags add <id> work "work/meetings"
bearcli tags remove <id> draft
bearcli tags rename work job
bearcli tags delete draft                       # removes from all notes, incl. nested children

bearcli pin list                                # every pin context in use
bearcli pin add <id> global work                # "global" = All Notes pin, else tag names

From rcedwards/blaude-bode, MIT.

More from rcedwards/blaude-bode

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from rcedwards

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get bearcli running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying bearcli?

CallGet help
Cite this page

bearcli skill. Agent Mart. https://agentmart.dev/skills/rcedwards-bearcli (last updated 2026-10-24)