@todoforai/cli 0.1.72 → 0.1.73

package/dist/todoforai-cli.js

@@ -43281,6 +43281,10 @@ class ApiClient {
     const { projectId, ...body } = input;
     return this.request("POST", `/api/v1/projects/${projectId}/recommendations`, body);
   }
+  async feedIgnore(input) {
+    const { projectId, ...body } = input;
+    return this.request("POST", `/api/v1/projects/${projectId}/feed/ignored`, body);
+  }
   async getRegistrySpec(specId) {
     const base = this.apiUrl.replace(/\/api\/v1\/?$/, "").replace(/\/$/, "");
     const res = await fetch(`${base}/cookie/v1/registry/templates/${specId}`);
@@ -44637,32 +44641,15 @@ To materialize growth recommendations, propose todos on the project board. A pro
 
 Exactly ONE \`api_recommend_template\` call per proposal: it carries both what the todo is and where it lands on the board.
 
-1. WHAT IT IS. Pass \`name\` + \`body\`, written for THIS business, and optionally \`description\`, \`short\` and \`categories\`.
+1. WHAT IT IS. Pass \`name\`, \`description\` and \`body\`, written for THIS business.
    - Reuse an existing registry template instead ONLY when it already fits this business closely with no meaningful edits: pass its id as \`templateId\` and omit \`name\`/\`body\`. If it needs tailoring, write yours inline. Do not recommend a generic playbook that ignores this company's specifics.
 
-   Language: match the business. Write user-facing text such as names, bodies and notes in the language the company itself communicates in. When the company is international or unclear, use English. Only the frame stays in English. The heading lines \`Your task:\`, \`Steps:\` and \`Data needed:\` are parsed, so keep them exactly as-is. Everything else follows the business's language.
-
-   The body is read by a PERSON deciding whether to run it, so it must be understandable at a glance. The executing agent is capable and has the business context at run time, so it will elaborate and figure out the details itself. Write a minimal brief, not a playbook. Include ONLY what the agent could not figure out on its own: the business-specific direction such as company, competitor, segment, channel and the metric to move, plus any hard constraint. Cut everything else, including background, caveats, generic how-to and restated context.
-
-   Hard limits: body ≤80 words total. One sentence of persona. One-sentence task. 2-4 steps, each a short fragment of at most 8 words naming WHAT, not how. Data needed is a comma-separated list. If a sentence wouldn't change what the agent does, delete it.
-
-   \`name\`: 3-6 words, action-first like "Win Reddit comparison threads", with no company name prefix. Give \`description\` and \`short\` one tight sentence each.
+   A person reads it at a glance and decides whether to run it, so use as few words as possible. The executing agent is capable, reads the business context at run time and asks for anything it is missing, so give no steps, no list of inputs and no background.
+   - \`name\`: 3-6 words, action-first like "Win Reddit comparison threads", with no company name prefix.
+   - \`description\`: one plain sentence of at most 15 words saying what the user gets, such as "Three vs-Gmail pages, drafted and ready to publish." Never repeat the name.
+   - \`body\`: one sentence naming the expert to act as, such as "You are an SEO writer for email products." Nothing else: no headings, no task, no steps.
 
-   Example body at the right density (adapt specifics, keep the brevity):
-   "You are a B2B outbound specialist for dev-tool companies.
-   Your task:
-   Land Acme in 10 agency partner conversations this month.
-   Steps:
-   - Shortlist 30 EU automation agencies
-   - Draft one-line personalized openers
-   - Send, track replies in a sheet
-   Data needed:
-   Acme pricing page, current partner list, founder's LinkedIn"
-
-   Body structure (REQUIRED). The body is split into the agent's system prompt and the first user turn by section headings, so follow this exactly:
-   - Start with the persona, expertise and any Rules as plain prose at the top with no heading. This becomes the agent's system prompt.
-   - Then write the request using these exact standalone heading lines, letters only, each on its own line and ending with a colon: \`Your task:\`, \`Steps:\`, \`Data needed:\`. Everything under these headings becomes the first user turn.
-   - Headings must match exactly or the split breaks. Write \`Your task:\`, not \`Your task (SEO):\`. Put the business-specific detail in the body text under each heading, never in the heading itself.
+   Language: write the name, description, body and note in the language the company itself communicates in. When the company is international or unclear, use English.
 
 2. WHERE IT LANDS, in that same call. It becomes a PROPOSED todo on the project and never a running todo:
    Give it a one-line \`note\` of roughly 15 words at most giving the WHY for THIS business, which becomes the proposal's tooltip, a \`priority\` of high, medium or low. Leave \`group\` empty: proposals land on the board without a group, and you never create, rename or archive groups. Project and business context default to the current session, so pass them only when targeting a different one. The proposal appears as a ✧ row on the board for the user to review before any credits are spent. Re-proposing the same \`templateId\` refreshes that open proposal instead of duplicating it. An inline proposal is always a new one, so check the board you just read before repeating a move that is already there. Dismissed proposals since your last run are fed back to you. Don't re-propose those, steer elsewhere.
@@ -50445,7 +50432,7 @@ var package_default = {
     type: "git",
     url: "git+https://github.com/todoforai/cli.git"
   },
-  version: "0.1.72",
+  version: "0.1.73",
   type: "module",
   bin: {
     "todoforai-cli": "bin/todoforai-cli.js",
@@ -50515,6 +50502,7 @@ Examples:
   tfa-cli open <url> [todo-id]        # Live url preview in the chat
   tfa-cli connect <key>… [--reason "why"]  # Sign-in card for connectors on this machine (several keys = one choice)
   tfa-cli recommend --template <id> | --title "…" [--info] [--source "label|ref|url"]  # ✧ proposal card, or an ⓘ info row
+  tfa-cli ignore --title "…" [--source "label|ref|url|from"] [--note "why"]  # Log an inbound item as noise (folded under the Feed card)
   tfa-cli inbox [needs-you|messages|activity] [--unread]  # Read the notification feed (the bell)
   tfa-cli inbox seen [tab]              # Mark notifications read
   tfa-cli notify [--to <email>] "Title" "message" [--href /t/<id>] [--url <link>]  # Note to your own user, or --to a project member (Messages tab + phone push)
@@ -80418,6 +80406,28 @@ async function main() {
       console.log(res.ref);
     return;
   }
+  if (positionals[0] === "ignore") {
+    const title = args.title?.trim();
+    if (!title) {
+      process.stderr.write(`${RED3}Usage: tfa-cli ignore --title "..." [--source "label|ref|url|from"] [--note "why"] [--project <id>]${RESET2}
+`);
+      process.exit(2);
+    }
+    const source = args.source ? (() => {
+      const [label, ref, url2, from] = String(args.source).split("|");
+      return label && ref ? { label, ref, ...url2 ? { url: url2 } : {}, ...from ? { from } : {} } : undefined;
+    })() : undefined;
+    const projectId2 = args.project || getEnv("PROJECT_ID") || cfgScope.data.default_project_id;
+    if (!projectId2) {
+      process.stderr.write(`${RED3}No project found \u2014 pass --project <id>${RESET2}
+`);
+      process.exit(2);
+    }
+    await api2.feedIgnore({ projectId: projectId2, title, ...source ? { source } : {}, ...args.note ? { why: args.note } : {} });
+    process.stderr.write(`${DIM2}ignored: ${title}${RESET2}
+`);
+    return;
+  }
   if (positionals[0] === "recommend") {
     const templateId = args.template || positionals[1];
     const inlineTitle = !templateId && args.title?.trim();
@@ -80457,7 +80467,15 @@ async function main() {
     }
     const rec = await api2.recommend({
       projectId: projectId2,
-      ...templateId ? { specId: templateId } : { template: { name: inlineTitle, body: args.note || inlineTitle } },
+      ...templateId ? { specId: templateId } : { template: {
+        name: inlineTitle,
+        description: args.note || (source ? `From ${source.label}` : inlineTitle),
+        body: `Handle this item: ${inlineTitle}${args.note ? `
+
+${args.note}` : ""}${source?.url ? `
+
+Original: ${source.url}` : ""}`
+      } },
       ...args.info ? { todoKind: "info" } : {},
       ...source ? { source } : {},
       ...args.title ? { title: args.title } : {},

package/package.json

@@ -7,7 +7,7 @@
     "type": "git",
     "url": "git+https://github.com/todoforai/cli.git"
   },
-  "version": "0.1.72",
+  "version": "0.1.73",
   "type": "module",
   "bin": {
     "todoforai-cli": "bin/todoforai-cli.js",