feat(cli): default-aggregation for topic list + notification list
Some checks failed
CI / Lint (push) Has been cancelled
CI / Typecheck (push) Has been cancelled
CI / Broker tests (Postgres) (push) Has been cancelled
CI / Docker build (linux/amd64) (push) Has been cancelled

ships v0.5.0 phase 1.

omitting --mesh on these read verbs now routes through
/v1/me/topics and /v1/me/notifications instead of prompting
the user to pick a mesh. behavior preserved for explicit
--mesh foo.

implementation: resolveMeshForMint helper in commands/me.ts
silently picks the first joined mesh for apikey-mint when
flags.mesh is null. /v1/me/* endpoints resolve the user from
the apikey issuer regardless of which mesh issued the key, so
mint location is irrelevant — only the user identity matters.

help text updated to reflect the new default.

phase 2 (task list, state list, memory recall) needs /v1/me/*
aggregator endpoints first; deferred.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Alejandro Gutiérrez
2026-05-03 04:56:33 +01:00
parent e60980cfd7
commit 5ceb311d74
4 changed files with 57 additions and 16 deletions

View File

@@ -16,10 +16,23 @@
import { withRestKey } from "~/services/api/with-rest-key.js";
import { request } from "~/services/api/client.js";
import { readConfig } from "~/services/config/facade.js";
import { render } from "~/ui/render.js";
import { bold, clay, cyan, dim, green, yellow } from "~/ui/styles.js";
import { EXIT } from "~/constants/exit-codes.js";
/**
* /v1/me/* endpoints resolve the caller's user from the apikey issuer
* regardless of which mesh issued the key — every mesh works. When the
* user didn't pass --mesh, silently pick the first joined mesh for
* apikey-mint instead of prompting; the endpoint sees the same user.
*/
function resolveMeshForMint(explicit: string | null | undefined): string | null {
if (explicit) return explicit;
const cfg = readConfig();
return cfg.meshes[0]?.slug ?? null;
}
interface WorkspaceMesh {
meshId: string;
slug: string;
@@ -53,7 +66,7 @@ export interface MeFlags {
export async function runMe(flags: MeFlags): Promise<number> {
return withRestKey(
{
meshSlug: flags.mesh ?? null,
meshSlug: resolveMeshForMint(flags.mesh),
purpose: "workspace-overview",
capabilities: ["read"],
},
@@ -136,7 +149,7 @@ export interface MeTopicsFlags extends MeFlags {
export async function runMeTopics(flags: MeTopicsFlags): Promise<number> {
return withRestKey(
{
meshSlug: flags.mesh ?? null,
meshSlug: resolveMeshForMint(flags.mesh),
purpose: "workspace-topics",
capabilities: ["read"],
},
@@ -232,7 +245,7 @@ export async function runMeNotifications(
): Promise<number> {
return withRestKey(
{
meshSlug: flags.mesh ?? null,
meshSlug: resolveMeshForMint(flags.mesh),
purpose: "workspace-notifications",
capabilities: ["read"],
},
@@ -321,7 +334,7 @@ export interface MeActivityFlags extends MeFlags {
export async function runMeActivity(flags: MeActivityFlags): Promise<number> {
return withRestKey(
{
meshSlug: flags.mesh ?? null,
meshSlug: resolveMeshForMint(flags.mesh),
purpose: "workspace-activity",
capabilities: ["read"],
},
@@ -416,7 +429,7 @@ export async function runMeSearch(flags: MeSearchFlags): Promise<number> {
return withRestKey(
{
meshSlug: flags.mesh ?? null,
meshSlug: resolveMeshForMint(flags.mesh),
purpose: "workspace-search",
capabilities: ["read"],
},