Feature request: CLI commands to move postings between boxes (Paper Trail, Feed, Set Aside, Reply Later) #138

Activity

1. josh256 commented on Jul 21, 2026

   

   josh256

   on Jul 21, 2026

   More actions

   It would be great to add this; it's needed and would be a great improvement.

   👍React with 👍1Reacted by Janita-S
2. martinlaws

   added 2 commits that reference this issue on Jul 30, 2026

   Add `hey move` command

   ...

   This issue will close once commit b7a8d4f is merged into the 'main' branch.

   b7a8d4f

   Add `hey move` command

   ...

   This issue will close once commit 9b2577c is merged into the 'main' branch.

   9b2577c
3. martinlaws commented on Aug 5, 2026

   

   martinlaws

   on Aug 5, 2026

   Contributor

   More actions

   Hit the same wall, and went digging for why.

   The SDK methods are there, but the routes behind them are gone. MoveToPaperTrail, MoveToFeed, MoveToSetAside, MoveToReplyLater and MoveToTrash all resolve to /postings/{id}/move/{box}.json and /postings/{id}/trash.json in hey-sdk v0.3.0, and every one of those returns 404 against a live account today. So does GET /postings/{id}.json. The whole per-posting namespace looks retired.

   It isn't an auth or an ID problem: the same posting ID succeeds on POST /postings/seen.json with the same token, seconds apart.

   What does work is the route the web app itself uses:

   POST /postings/moves?box_id={boxId}
   Authorization: Bearer <token>
   {"posting_ids": [...]}
   

   200, with a turbo-stream body carrying one <turbo-stream action="remove" target="posting_{id}"> per posting that actually moved. Box IDs are per-account, so it needs a GET /boxes.json first, and it's a batch endpoint rather than one posting at a time.

   Worth flagging that #152 is built on those same SDK methods. I checked the branch out and ran it against my own account: feed, paper-trail, set-aside and reply-later all 404 (exit 2). I didn't test trash or ignore. Nothing wrong with the shape of it, just the plumbing underneath.

   All of this is against a single account, so if these routes are working for anyone else I'd genuinely like to know — that would point at scope or a rollout rather than a removal.

   I have a working implementation on the bulk route and can open it if that's useful. Equally happy to hold if you'd rather settle the route question first.
4. robzolkos commented on Aug 25, 2026

   

   robzolkos

   on Aug 25, 2026

   Collaborator

   More actions

   Closing — hey move <box-item-id> --to <box> shipped and accepts Feed, Paper Trail, Set Aside, Reply Later, Trash (by name, kind, or ID), so agent-driven triage can sort, not just mark seen. The one deliberate exclusion is Bubble Up, since it needs a scheduled date — that's tracked in #74, which stays open. Thanks for laying out the agent use case so clearly.

   🎉React with 🎉2Reacted by jaguileram and Martin Laws
5. robzolkos

   closed this as completedon Aug 25, 2026