alezmad/claudemesh
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: mark v0.4.0 phase 2 shipped + record web deploy trick
Some checks failed
CI / Lint (push) Has been cancelled
Details
CI / Typecheck (push) Has been cancelled
Details
CI / Broker tests (Postgres) (push) Has been cancelled
Details
CI / Docker build (linux/amd64) (push) Has been cancelled
Details

Browse Source 
roadmap entry for the me-topics + dashboard-topics ship.

claude.md gets the long-overdue note that apps/web is on coolify
on the ovh vps, not vercel — it does not auto-deploy on push to
gitea-vps the way the broker does, and that mismatch cost a
session of debugging. records the manual deploy command so the
next time we ship a web change we don't rediscover the issue.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Alejandro Gutiérrez
2026-05-03 01:36:05 +01:00
parent 354c47c3d6
commit 397ddb4c45
2 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CLAUDE.md
View File

@@ -24,7 +24,7 @@ Peer mesh for Claude Code sessions. Broker + CLI + MCP server.
- **CLI:** - **CLI:**
- npm: `cd apps/cli && npm publish --tag alpha --access public --no-git-checks --ignore-scripts` - npm: `cd apps/cli && npm publish --tag alpha --access public --no-git-checks --ignore-scripts`
- Binaries: `git tag cli-v<version> && git push github cli-v<version>` — workflow builds 5 platforms. - Binaries: `git tag cli-v<version> && git push github cli-v<version>` — workflow builds 5 platforms.
- **Web:** Vercel auto-deploy on push to GitHub - **Web:** Coolify on the OVH VPS (`claudemesh.com` resolves to `135.125.191.245`, NOT Vercel — the `apps/web/Dockerfile` is what Coolify builds). Push to `gitea-vps` does NOT auto-deploy the web app the way it does the broker. Trigger manually: `curl -s -X GET "http://100.122.34.28:8000/api/v1/deploy?uuid=p68x1e3k4xmrjmblca5ybe09" -H "Authorization: Bearer 3|K2vkSJzdUA69rj22CKZc5z0YB6pkY43GLEonti3UzcnqVJj6WhrqqYTAng6DzMUi"`
## Dev ## Dev

19
docs/roadmap.md
View File

@@ -247,12 +247,19 @@ level, or wire claudemesh to messaging surfaces beyond Claude Code.
over per-mesh apikeys — zero broker / protocol changes; per-mesh over per-mesh apikeys — zero broker / protocol changes; per-mesh
trust boundaries preserved. *Shipped 2026-05-02 in CLI v1.10.0.* trust boundaries preserved. *Shipped 2026-05-02 in CLI v1.10.0.*
Spec at `.artifacts/specs/2026-05-02-workspace-view.md`. Spec at `.artifacts/specs/2026-05-02-workspace-view.md`.
- **v0.4.0 phase 2+ — `me topics`, `me notifications`, `me - **v0.4.0 phase 2 — `claudemesh me topics` + dashboard parity**
activity`, `me search`** — additional aggregating verbs over — `GET /v1/me/topics` aggregates topics across every mesh the
`/v1/me/*` mirroring the existing per-mesh reads. Default caller belongs to with per-topic unread counts and last-message
aggregation rule for existing read verbs (`notification list`, timestamps, sorted by activity. CLI verb renders the feed with
`topic list`, `task list`, `state list`, `memory recall`) when no `--unread` filter and `--json` output. Web dashboard adds a
`--mesh` is passed. matching `/dashboard/topics` page (SSR, direct DB) with a Topics
entry in the sidebar between Meshes and Invites. *Shipped
2026-05-03 in CLI v1.11.0.*
- **v0.4.0 phase 3+ — `me notifications`, `me activity`, `me
search`** — additional aggregating verbs over `/v1/me/*`
mirroring the existing per-mesh reads. Default aggregation rule
for existing read verbs (`notification list`, `task list`, `state
list`, `memory recall`) when no `--mesh` is passed.
- **v0.3.2 — multi-session DM routing + broadcast self-loopback** — - **v0.3.2 — multi-session DM routing + broadcast self-loopback** —
fixes two production bugs: (1) replies via `claudemesh send fixes two production bugs: (1) replies via `claudemesh send
<from_id>` rejected with "no connected peer" when the sender's <from_id>` rejected with "no connected peer" when the sender's