@ziggs-ai/ziggs-mcp 0.11.0 → 0.12.0

package/dist/inboxToolResult.js

@@ -65,7 +65,7 @@ export function buildReadPlan(inbox, grantsByScope, self = { agentId: '' }) {
     // every time — the plan says to carry it to the human instead.
     const mayAnswer = (facts) => resolvePendingApprovalPartyId({
         pendingPartyIds: facts.pendingApprovalPartyIds ?? [],
-        proposedTo: facts.proposedTo,
+        proposedToIds: facts.proposedTo ? [facts.proposedTo] : [],
     }, [self.agentId]) === self.agentId && self.agentId !== '';
     for (const p of proposals) {
         add(`respond:${p.agreementId}`, mayAnswer(p)

package/dist/pendingDecisions.d.ts

@@ -97,8 +97,8 @@ export declare function buildPaymentApprovalItems(approvals: Array<Record<string
  * A task is "for me" when:
  * - it is explicitly assigned (`assigneeId`) to one of my ids, or
  * - it has no explicit assignee and one of my ids sits on the executing side
- *   of the task/agreement (executor, agent, provider, providerAgent,
- *   proposedTo).
+ *   of the task/agreement (executor, agent, or either column of the provider /
+ *   proposedTo party sides).
  * Tasks with no assignee and no readable agreement parties are excluded —
  * "can't tell" must not render as "yours".
  */

package/dist/pendingDecisions.js

@@ -1,4 +1,4 @@
-import { resolvePendingApprovalPartyId, } from '@ziggs-ai/api-client';
+import { partySideIds, resolvePendingApprovalPartyId, } from '@ziggs-ai/api-client';
 /** Chat/tool cues when {@link PendingDecisionItem.respondableBy} is `agent`. */
 export function decisionRespondCues(item) {
     if (item.respondableBy !== 'agent')
@@ -77,7 +77,7 @@ function respondableByFor(facts, self) {
     // Agent id first: when both owe a decision, ours is the one we can act on.
     const slot = resolvePendingApprovalPartyId({
         pendingPartyIds: facts.pendingApprovalPartyIds ?? [],
-        proposedTo: facts.proposedTo,
+        proposedToIds: facts.proposedTo ? [facts.proposedTo] : [],
     }, [self.agentId, self.ownerUserId]);
     return slot != null && slot === self.agentId ? 'agent' : 'human';
 }
@@ -171,8 +171,8 @@ export function buildPaymentApprovalItems(approvals, webOrigin) {
  * A task is "for me" when:
  * - it is explicitly assigned (`assigneeId`) to one of my ids, or
  * - it has no explicit assignee and one of my ids sits on the executing side
- *   of the task/agreement (executor, agent, provider, providerAgent,
- *   proposedTo).
+ *   of the task/agreement (executor, agent, or either column of the provider /
+ *   proposedTo party sides).
  * Tasks with no assignee and no readable agreement parties are excluded —
  * "can't tell" must not render as "yours".
  */
@@ -186,7 +186,7 @@ export function filterTasksForDelegate(tasks, selfIds) {
         const p = t.agreement?.parties;
         if (!p)
             return false;
-        return mine(p.provider) || mine(p.providerAgent) || mine(p.proposedTo);
+        return [...partySideIds(p.provider), ...partySideIds(p.proposedTo)].some(mine);
     });
 }
 export function buildActiveWorkItems(tasks, webOrigin) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ziggs-ai/ziggs-mcp",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "MCP server for Claude Code, Cursor, and other MCP hosts — act as your Ziggs delegate agent",
   "type": "module",
   "bin": {
@@ -39,7 +39,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@ziggs-ai/api-client": "0.11.0",
+    "@ziggs-ai/api-client": "0.12.0",
     "dotenv": "^16.6.1",
     "zod": "^3.24.2",
     "zod-to-json-schema": "^3.25.1"

package/skills/ziggs/references/grants-and-approvals.md

@@ -45,16 +45,20 @@ connection) **is just an agreement** (`engagementKind: "link"`). Create it, the
 counterparty owner approves it, and unpublished delegates can then reach each other.
 
 1. Human describes goal and counterparty.
-2. Propose the link with **`ziggs_agreement_buy`** (`engagementKind: "link"`, `proposedTo` =
-   the target delegate agent id; use `ziggs_agent_search` to find agents — do not guess ids).
-   No agent id? Mint a shareable invite with **`ziggs_link_create_invite`** instead; the
-   recipient claims it with **`ziggs_agreement_claim`**.
+2. Connect with **`ziggs_link_propose`**: pass `to` = their email address, or the id of an
+   agent that answers to them (use `ziggs_agent_search` to find agents — do not guess ids).
+   The link is with the PERSON either way; an agent answering to an organisation is refused,
+   because a link connects two people. Leave `to` out and you get `shareUrl` to hand your
+   human; the recipient claims it with **`ziggs_agreement_claim`**. The reply is identical
+   every time, so it never reveals whether an address has an account.
 3. Target human approves via **`ziggs_agreement_respond`** (action `approve`) when the
    pending link agreement shows in their inbox / `ziggs_link_list`. This is the same generic
    approval tool used for hire and service proposals — there is no separate link-response tool.
-4. **A link ≠ a grant.** The link only allows unpublished delegates to *reach* each other. To
-   chat or read context, continue with **`ziggs_chat_open`** (participantId = peer agent
-   id) and/or **`ziggs_context_issue_grant`** — still approval-gated when exposing existing scope.
+4. **A link ≠ a grant.** The link only makes the two people reachable to each other. To
+   chat or read context, continue with **`ziggs_chat_open`** (participantId = the peer
+   PRINCIPAL, a person: delivery lands in their mailbox and whoever runs that side picks it
+   up) and/or **`ziggs_context_issue_grant`** — still approval-gated when exposing existing
+   scope.
 5. `ziggs_context_read` only after grant is active.
 6. `ziggs_context_revoke_grant` when context access should end; **`ziggs_agreement_revoke`** when
    the agreement should end — any kind: hire, service, request, offer, or link.