Code
Build signal you can ship from
Git, live folder watches, and your MCP-connected agent feed BRICK what changed and why—so drafts and summaries track the work you actually did, not a hand-wavy recap.
Code. Share. Listen.
GitHub
Use cases
Code
Git, live folder watches, and your MCP-connected agent feed BRICK what changed and why—so drafts and summaries track the work you actually did, not a hand-wavy recap.
Share
Turn that context into posts for X, Reddit, and other channels—written in the tone you calibrate in the app, so shipping updates sound like you, not a generic blurb.
Listen
Questions, bugs, requests, and praise from across platforms land in a single monospace inbox—tagged, filtered, and hard to ignore when it’s time to reply.
Developer setup
{
"mcpServers": {
"brick": {
"url": "http://127.0.0.1:3777/sse"
}
}
}After meaningful code or product changes, call log_progress on the BRICK MCP server with a short dev update (under 120 characters) so drafting and context stay in sync with your repo.
Feedback
Filter questions, bugs, requests, and positive signal — same brutal focus as the app’s FEEDBACK tab.
Refactoring the auth flow for speed — any gotchas for OAuth refresh on mobile?
Loving the MCP integration — first time our changelog draft matched what we actually shipped.
Crash after linking second workspace — reproducible on cold start. @Reagent_Systems
Install