Skip to content

Clarify ~/.kombai app data ≠ repo .kombai/ message board - #32

Merged
cursor[bot] merged 1 commit into
developfrom
cursor/kombai-path-clarification-fbda
Oct 4, 2026
Merged

cursor[bot] merged 1 commit into
developfrom
cursor/kombai-path-clarification-fbda

Conversation

@billbrietstout

Copy link
Copy Markdown
Owner

Summary

Bill found that pwd of /Users/billstout/.kombai is Kombai application data (mcp, binaries, workspaces), not the Cursor↔Kombai message board.

This PR updates the tracked .kombai docs so the distinction is unmistakable:

  • ~/.kombai / /Users/<you>/.kombai = Kombai app data (not the board)
  • <git-checkout>/.kombai/MESSAGE-BOARD.md = the only board (local, gitignored)

Also documents: create with cp .kombai/MESSAGE-BOARD.example.md .kombai/MESSAGE-BOARD.md from the repo root; Finder ⌘⇧. for the checkout’s .kombai dotfolder; never commit MESSAGE-BOARD.md.

Files

  • .kombai/README.md
  • .kombai/MESSAGE-BOARD.example.md

Project store docs updated in parallel (not in this PR): docs/kombai-message-board.md, docs/kombai-board-howto-message.md, docs/kombai-board-paste-snapshot.md, docs/kombai-path-clarification-message.md, workflows/kombai-cursor-visual-handoff.md, preferences.md.

Test plan

  • Confirm README warning table and example/wrong paths read clearly
  • Confirm example template carries the same ~/.kombai ≠ checkout warning
  • After merge, pull develop and create live board with the documented cp from repo root
Open in Web Open in Cursor 

Document that the Cursor↔Kombai board lives only under the git checkout
(.kombai/MESSAGE-BOARD.md), how to create it from the example, and that
the live file must never be committed.

Co-authored-by: billbrietstout <billbrietstout@users.noreply.github.com>
@billbrietstout
billbrietstout marked this pull request as ready for review October 4, 2026 21:18
@cursor
cursor Bot merged commit d347d55 into develop Oct 4, 2026
1 check passed
@cursor
cursor Bot deleted the cursor/kombai-path-clarification-fbda branch October 4, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants