ee12510ef1
- apps/cli/ is now the canonical CLI (was apps/cli-v2/). - apps/cli/ legacy v0 archived as branch 'legacy-cli-archive' and tag 'cli-v0-legacy-final' before deletion; git history preserves it too. - .github/workflows/release-cli.yml paths updated. - pnpm-lock.yaml regenerated. Broker-side peer-grant enforcement (spec: 2026-04-15-per-peer-capabilities): - 0020_peer-grants.sql adds peer_grants jsonb + GIN index on mesh.member. - handleSend in broker fetches recipient grant maps once per send, drops messages silently when sender lacks the required capability. - POST /cli/mesh/:slug/grants to update from CLI; broker_messages_dropped_by_grant_total metric. - CLI grant/revoke/block now mirror to broker via syncToBroker. Auto-migrate on broker startup: - apps/broker/src/migrate.ts runs drizzle migrate with pg_advisory_lock before the HTTP server binds. Exits non-zero on failure so Coolify healthcheck fails closed. - Dockerfile copies packages/db/migrations into /app/migrations. - postgres 3.4.5 added as direct broker dep. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
29 lines
2.2 KiB
Plaintext
29 lines
2.2 KiB
Plaintext
{\rtf1\ansi\ansicpg1252\cocoartf2867
|
|
\cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
|
|
{\colortbl;\red255\green255\blue255;}
|
|
{\*\expandedcolortbl;;}
|
|
\margl1440\margr1440\vieww11180\viewh8060\viewkind0
|
|
\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0
|
|
|
|
\f0\fs24 \cf0 Mesh templates for predefined roles, groups\'85\
|
|
Mesh blockchain, can it be a good addition? For what?\
|
|
Mesh webhooks, external web sockets, restful apis to be connected to the mesh (mcp)\
|
|
Mesh skills available for all ai? Like a mesh catalog of skills for sessions to get and use them?\
|
|
Inicial private mesh by default for every new user\
|
|
Mesh dashboard for situational awareness of mesh, to illustrate the peers connected, their activity, status, mesh structure\
|
|
Mesh of meshes? bridge?\
|
|
Mesh Connectors: slack, telegram, they can appear as peers? Or sth different?\
|
|
Connect humans to the mesh? Peer info to know about if human, type of channel (telegram or whatever) or llm model if ai?\
|
|
How to connect others than just claude code? The problem will be the push system I suppose\
|
|
\
|
|
Add path (pwd) where each session is being executed for them to understand how to reference files if same computer? Maybe only visible for peers on same computer?\
|
|
What if a peer on connection can make available all the project files, folders and subfolders? Direct access? So other ai can read files if needed from connected projects?\
|
|
Can we have peer stats for example about context consumption?\
|
|
Mesh notifications about new peers, new connectors, new resources? Broadcast?\
|
|
Allow group or role changes dynamically not only on mesh connection?\
|
|
Dynamic mcp that can be connected or disconnected on realtime without resetting the claude code sessions?\
|
|
Mesh templates on creation, with a predefined structure that it can be changed as well by mesh admin role? Or any? Or what idea?\
|
|
What if reminders can be just cron so ai knows exactly how to configure crons for the mesh? So broker can handle the cron creation? What about mesh heartbeats to keep ai alive?\
|
|
Sandbox for code execution, python, node, chromium, etc so any peer can connect to resources, and resources being scalable on real time if a new peer needs a sandbox?\
|
|
\
|
|
} |