Keep your tools.
Bring context together.
Read selected sources from Obsidian, GitHub, Jira, and Confluence and keep them locally. Source references stay separate from agent-written summaries and tags.
Good decisions should carry into your next task.
Connect
scattered sources and your agent’s notes
so you spend less
time explaining from scratch.
Choose the vaults, repositories, tickets, and documents to connect.
Let users choose the scope.
Preserve sources and carry
context forward.
Found earlier decisions and their source evidence.
The agent linked product principles and evidence
and
completed the connection settings work.
Your agent writes and completes work.
You browse results,
evidence, and history.
Read selected sources from Obsidian, GitHub, Jira, and Confluence and keep them locally. Source references stay separate from agent-written summaries and tags.
Your agent saves summaries, tags, and sources with reusable notes. Browse the notes, revision history, and evidence in the app.
Find related records through note and memo search and the relationship graph. Follow note wikilinks, source evidence, and MOC reading paths to explore context.
Your agent links notes and sources to work and to-dos, then records completion directly. Browse status, results, and next actions on Home, and updates and brief agent memos in Activity.
Install an agent connection (bridge 3) in Settings and start a new
session.
Query saved notes and connected sources through CLI and MCP.
Enable automatic memory per project. It works with the app window closed. Context queries currently search all permitted connections.
Notes and collected source snapshots are stored locally. Reading fresh external sources uses the network.
Connected sources are read-only. Notes retain their evidence and revision history.
Choose your connections and source scope. Credentials are managed in macOS Keychain.
Aidebook for macOS · Apple Silicon.
Download for macOSv0.2.4 public release Homepage updated October 19, 2026
Apple Silicon · macOS 11 or later
Ad-hoc signed · Not
notarized by Apple. You may need to allow the app on first launch.
Your agent writes notes and saves work status and completion directly. The app lets you browse work, results, evidence, note history, search, and the relationship graph, and manage plugins, connections, and settings. It does not provide human approval, rejection, completion review, or ordinary record editing. External connections require their own access and authentication setup.
Keep your existing sources in their original tools. Aidebook reads selected sources and separately stores notes and evidence for your agent. It does not automatically overwrite connected Obsidian files or external issues.
The showreel is a motion demo built with fixed example data to explain the product flow. It is not an app recording and does not connect accounts or make AI calls.
After installing the automatic memory hooks, create .aidebook-auto-memory.json in a project and set enabled to true. Hooks run only in those projects. This setting controls where hooks run; queries currently retrieve results from all permitted Aidebook connections.
Install with Homebrew, or download the v0.2.4 DMG from GitHub Releases and copy the app to Applications. The current release is ad-hoc signed, without Apple Developer ID signing or notarization. On first launch, you may need to verify the source and allow the app in macOS System Settings under Privacy & Security.
Before upgrading or replacing the app, quit the old app and run
aidebook-cli service stop using the OLD installed CLI.
Then update Homebrew, upgrade the app and CLI together, and open
the new app in this order:
aidebook-cli service stop
brew update
brew upgrade --cask aidebook
open -a Aidebook
In the new app’s Settings, reinstall your Agent connection (bridge 3), then start new Agent sessions. Existing notes, revisions, evidence, MOC membership, and connection settings are preserved. v0.2.4 uses protocol 2 / API 1 and does not guess-stop a legacy Core that lacks a compatibility declaration. If you have already replaced the old binaries, follow the service error’s recovery guidance; do not force-stop the owner or delete your data.