v0.1.3

Opening this build

This build is ad-hoc signed but not notarized — notarization requires a paid Apple Developer
account. macOS will say "Apple could not verify Vibepaws is free of malware." That is expected,
and here is how to open it:

1. Drag Vibepaws into your Applications folder, then double-click it.
2. macOS blocks it. Open System Settings → Privacy & Security.
3. Scroll down to Security. You'll see "Vibepaws was blocked to protect your Mac."
   Click Open Anyway.
4. Confirm once more. macOS remembers the choice — first launch only.

On macOS Sequoia and later, Control-clicking the app no longer works as a shortcut for this.
System Settings is the only route.

Or install with Homebrew

brew tap junrong1/vibepaws https://github.com/junrong1/Vibepaws
brew trust junrong1/vibepaws        # Homebrew 6 requires this for third-party taps
brew install --cask vibepaws

This gives you brew upgrade for future versions. It does not skip the approval above —
Homebrew 6 removed --no-quarantine, so cask downloads are always quarantined. To skip the
System Settings trip, clear the flag yourself:

xattr -dr com.apple.quarantine /Applications/Vibepaws.app

What "not notarized" does and doesn't mean

It means Apple hasn't scanned this build — not that the app is unsigned or modified. The signature
is complete and verifiable (codesign --verify --deep --strict passes), which is why you get an
approval prompt rather than "Vibepaws is damaged." Every release is built in CI from a public
tag, and the build is reproducible from source with npm run dist:mac.

What's Changed

• feat(habit): 习惯画像层 —— 进化门控 / 行为 / 语气（含评审修复） by @horyzz in #30
• chore(docs): 移除 habit 层设计文档 by @horyzz in #32

Full Changelog: v0.1.2...v0.1.3

v0.1.2

Opening this build

This build is ad-hoc signed but not notarized — notarization requires a paid Apple Developer
account. macOS will say "Apple could not verify Vibepaws is free of malware." That is expected,
and here is how to open it:

1. Drag Vibepaws into your Applications folder, then double-click it.
2. macOS blocks it. Open System Settings → Privacy & Security.
3. Scroll down to Security. You'll see "Vibepaws was blocked to protect your Mac."
   Click Open Anyway.
4. Confirm once more. macOS remembers the choice — first launch only.

On macOS Sequoia and later, Control-clicking the app no longer works as a shortcut for this.
System Settings is the only route.

Or install with Homebrew

brew tap junrong1/vibepaws https://github.com/junrong1/Vibepaws
brew trust junrong1/vibepaws        # Homebrew 6 requires this for third-party taps
brew install --cask vibepaws

This gives you brew upgrade for future versions. It does not skip the approval above —
Homebrew 6 removed --no-quarantine, so cask downloads are always quarantined. To skip the
System Settings trip, clear the flag yourself:

xattr -dr com.apple.quarantine /Applications/Vibepaws.app

What "not notarized" does and doesn't mean

It means Apple hasn't scanned this build — not that the app is unsigned or modified. The signature
is complete and verifiable (codesign --verify --deep --strict passes), which is why you get an
approval prompt rather than "Vibepaws is damaged." Every release is built in CI from a public
tag, and the build is reproducible from source with npm run dist:mac.

What's Changed

• Feat/embercub evolution family by @junrong1 in #28
• docs(landscape): 划掉 9/29 交付的六项 —— 健康分、复盘卡、教练气泡、日志、成长可读性、减少动效 by @junrong1 in #29

Full Changelog: v0.1.1...v0.1.2

v0.1.1

Opening this build

This build is ad-hoc signed but not notarized — notarization requires a paid Apple Developer
account. macOS will say "Apple could not verify Vibepaws is free of malware." That is expected,
and here is how to open it:

1. Drag Vibepaws into your Applications folder, then double-click it.
2. macOS blocks it. Open System Settings → Privacy & Security.
3. Scroll down to Security. You'll see "Vibepaws was blocked to protect your Mac."
   Click Open Anyway.
4. Confirm once more. macOS remembers the choice — first launch only.

On macOS Sequoia and later, Control-clicking the app no longer works as a shortcut for this.
System Settings is the only route.

Or install with Homebrew

brew tap junrong1/vibepaws https://github.com/junrong1/Vibepaws
brew trust junrong1/vibepaws        # Homebrew 6 requires this for third-party taps
brew install --cask vibepaws

This gives you brew upgrade for future versions. It does not skip the approval above —
Homebrew 6 removed --no-quarantine, so cask downloads are always quarantined. To skip the
System Settings trip, clear the flag yourself:

xattr -dr com.apple.quarantine /Applications/Vibepaws.app

What "not notarized" does and doesn't mean

It means Apple hasn't scanned this build — not that the app is unsigned or modified. The signature
is complete and verifiable (codesign --verify --deep --strict passes), which is why you get an
approval prompt rather than "Vibepaws is damaged." Every release is built in CI from a public
tag, and the build is reproducible from source with npm run dist:mac.

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Opening this build

This build is ad-hoc signed but not notarized — notarization requires a paid Apple Developer
account. macOS will say "Apple could not verify Vibepaws is free of malware." That is expected,
and here is how to open it:

1. Drag Vibepaws into your Applications folder, then double-click it.
2. macOS blocks it. Open System Settings → Privacy & Security.
3. Scroll down to Security. You'll see "Vibepaws was blocked to protect your Mac."
   Click Open Anyway.
4. Confirm once more. macOS remembers the choice — first launch only.

On macOS Sequoia and later, Control-clicking the app no longer works as a shortcut for this.
System Settings is the only route.

One command instead

brew tap junrong1/vibepaws https://github.com/junrong1/Vibepaws
brew install --cask --no-quarantine vibepaws

--no-quarantine skips the Gatekeeper prompt entirely, so there is nothing to approve.

What "not notarized" does and doesn't mean

It means Apple hasn't scanned this build — not that the app is unsigned or modified. The signature
is complete and verifiable (codesign --verify --deep --strict passes), which is why you get an
approval prompt rather than "Vibepaws is damaged." Every release is built in CI from a public
tag, and the build is reproducible from source with npm run dist:mac.

What's Changed

• Feature/code review by @junrong1 in #10
• Feature/code review by @junrong1 in #11
• fix(adapter): Claude Code 从来不发 Stop —— 最该响的那条提醒，对所有用户都是死的 by @junrong1 in #13
• feat(pets): 七个状态各有一张立绘 —— 表情这条通道，抖动和角标替代不了 by @junrong1 in #16
• fix/always-0-token by @horyzz in #17
• Feat/adapt pi by @horyzz in #18
• fix(adapter): statusline 补齐 context_pct 与状态栏输出 —— token 通道通了，另外两半还是空的 by @junrong1 in #19
• feat(settings): 设置窗口 —— 预算和会话目标一直有引擎，只是没有入口 by @junrong1 in #20
• feat(settings): 应用内重置 / 删除 / 卸载 —— 删数据的唯一出口一直是一句 rm -rf by @junrong1 in #21
• delete zani pet code by @horyzz in #22
• feat(adapter): 适配 DeepSeek Harness (dsh) —— 第四个 agent 也是机器级事件钩子，不靠模型自觉 by @horyzz in #24
• feat(status): 新增 ready 待命状态，decision_required 按 kind 分流 by @horyzz in #25
• feat(ui): session 状态文字标签，浮层与设置窗口共用一份文案 by @horyzz in #26
• fix(status): 启动未干活的会话判为 idle 而非 working by @horyzz in #27

New Contributors

• @junrong1 made their first contribution in #10
• @horyzz made their first contribution in #17

Full Changelog: https://github.com/junrong1/Vibepaws/commits/v0.1.0