ticlawk 0.1.16-dev.8 → 0.1.16-dev.9

package/bin/ticlawk.mjs

@@ -30,7 +30,6 @@ import { getInstallDaemonHelp, runInstallDaemon } from '../src/core/daemon-insta
 import { runSetupReadiness } from '../src/core/setup-readiness.mjs';
 import {
   AGENT_COMMAND_HELP,
-  runAttachmentUploadCommand,
   runAttachmentViewCommand,
   runGroupCreateCommand,
   runGroupMembersAddCommand,
@@ -416,10 +415,6 @@ async function main() {
       console.log(AGENT_COMMAND_HELP.attachment);
       return;
     }
-    if (sub === 'upload') {
-      process.exitCode = await runAttachmentUploadCommand(args);
-      return;
-    }
     if (sub === 'view') {
       process.exitCode = await runAttachmentViewCommand(args);
       return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.16-dev.8",
+  "version": "0.1.16-dev.9",
   "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
   "type": "module",
   "main": "ticlawk.mjs",

package/src/cli/agent-commands.mjs

@@ -662,18 +662,6 @@ function inferContentType(filePath) {
   }
 }
 
-export async function runAttachmentUploadCommand(args) {
-  const env = requireAgentEnv();
-  const file = args._?.[2];
-  if (!file) {
-    console.error('usage: ticlawk attachment upload <file>');
-    return 2;
-  }
-  const upload = await uploadFileViaDaemon(env, file);
-  printJson(upload);
-  return upload.ok ? 0 : 1;
-}
-
 export async function runAttachmentViewCommand(args) {
   const env = requireAgentEnv();
   const assetId = args._?.[2];
@@ -848,12 +836,9 @@ export const AGENT_COMMAND_HELP = {
   ticlawk profile show [@handle | --id <agent-id>]
   ticlawk profile update [--display-name X] [--description Y] [--avatar-file path]
 `,
-  attachment: `ticlawk attachment <upload|view>
-  ticlawk attachment upload <file>
-    Upload-only — the user is NOT notified. Almost always you want
-    \`ticlawk message send --attach <file>\` instead, which uploads AND
-    surfaces the file to the user inside a chat message.
-  ticlawk attachment view <asset-id> [--out <path>]
+  attachment: `ticlawk attachment view <asset-id> [--out <path>]
+    Fetch metadata + signed URL for an existing asset. To send a file
+    to a user, use \`ticlawk message send --attach <file>\` instead.
 `,
   reminder: `ticlawk reminder <schedule|list|snooze|update|cancel|log>
   ticlawk reminder schedule --title <t> (--fire-at <iso> | --in-seconds N | --in-minutes N) (--target "<target>" | --anchor-conversation-id <id>) [--anchor-message-id <id>]

package/src/runtimes/_shared/standing-prompt.mjs

@@ -79,10 +79,13 @@ EOF
 - \`--attach <path>\` may be repeated; up to 10 files per message.
 - Each file uploads to the secure file layer and surfaces to the user
   inside the chat UI alongside your text.
-- \`ticlawk attachment upload <file>\` exists as a separate command but
-  **only uploads** — the user is not notified and cannot see the file.
-  Almost never the right command. Only use it if you have a specific
-  reason to stash a file for later use without telling the user.
+
+**The number of attachments must match what your text says.** If your
+message body says "two charts attached", the command must contain
+exactly two \`--attach\` flags. If your files are not ready yet (still
+downloading, still generating), **wait** before sending; do not send a
+"here it is" message claiming files you have not actually attached.
+The user only sees what you attached, not what you promised.
 
 ### Threads