Assist With Moving
FeaturesYour AIAboutFAQ
Sign in
Release notes

What's New

See what Assist With Moving can do now, what was fixed, and what became easier or safer. Choose a quick scan or learn why each change matters.

Current application version: v0.7.0

Quick read shows one outcome sentence per change.

v0.7.0

Hand your chosen AI exactly what you choose, and take it back

August 17, 2026, 8:31 AM MST

You can now connect one AI to one private move with narrow authority you approve yourself, watch what it does, and end the connection so the very next thing it tries is refused.

+Created2

  • Approve exactly which moves an AI may reach and what it may do, see every use, and revoke it instantly.

    What: Settings → AI connections is a real grant manager. You choose the moves, then approve up to five separate permissions — read move context, read private evidence, save move work, work the Queue, and archive records — each with a published boundary saying what it does not imply. The connection shows its client, registration method, approval, expiry, last use and use count, plus an append-only trail of both uses and refusals. Revoking takes effect on the very next call, because the grant is re-read from the database on every discovery and every tool call rather than trusted from the access token. A connected AI can also work the Queue under that grant: list only actionable work, claim it, ask the smallest clarifying question, and finish it in one saved result. Signing in proves who you are; it never decides what the AI may do.

    Why: Signing in with OAuth proved identity and nothing else. Without a product-level grant, connecting an AI meant handing it whatever the sign-in could reach, with no screen that showed the connection, no narrow choice, and no way to end it yourself.

    Where: Settings → AI connections, after connecting an AI to https://movingmanifest.com/mcp.

  • A connected AI can see your move photos, and says plainly when a picture cannot be delivered.

    What: Private photos reach a connected AI as real image bytes, fetched server-side so no storage link ever leaves Assist With Moving. Each image and each batch has a size ceiling, and an oversized photo automatically steps down to a smaller version before it is ever dropped. Anything still left out comes back with a ranked, plain-language reason.

    Why: Moving's inventory is made of photographs, and asking for a batch of full-size ones could exceed the response limit and fail the whole call — so an AI asking for eight pictures got none instead of six. A photo that could not be delivered also vanished silently, so 'this belonging has no photo', 'the photo is still processing', and 'you asked for too much' were indistinguishable.

    Where: Ask a connected AI about belongings that have photos, with read-private-evidence approved.

✓Fixed3

  • Connecting an AI no longer fails because Assist With Moving asked for permissions the sign-in provider cannot issue.

    What: Discovery now advertises only the identity scopes the authorization server can actually grant, and carries the five Moving product permissions in a separate vendor block alongside the grant-manager address. Authority still comes from your approved grant, never from a token scope.

    Why: Advertising product permissions as OAuth scopes made well-behaved clients request something the provider could not issue, which failed the connection outright before a person ever reached the approval screen.

    Where: Point any compatible AI client at https://movingmanifest.com/mcp.

  • The approval screen now names Assist With Moving instead of a bare address.

    What: The protected-resource document publishes the product's real display name, so the consent screen a person sees while connecting their AI says Assist With Moving.

    Why: Being asked to approve access for an unnamed host is exactly the moment a person should be able to tell what they are approving.

  • Every page that offers help now points somewhere that works.

    What: One shared support path replaces the missing contact address referenced across the marketing, about, FAQ, privacy, and agent-facing pages.

    Why: Pages invited people to get in touch and then gave them nowhere to go.

    Where: The footer, About, FAQ, and Privacy pages.

↑Upgraded1

  • The local helper package is now named assistwithmoving-mcp, matching the product.

    What: The bundled local MCP command and its package were renamed from movingmanifest-mcp to assistwithmoving-mcp, along with the project's internal technical identity.

    Why: The old technical name predated the product name, so desktop AI configuration files referred to something a person could not recognize.

    Where: Local stdio setup, for people who run the helper package with an mmk_ key.

v0.6.0

A private move that starts with the person

August 14, 2026, 8:48 AM MST

A first visit now starts one private move directly, then keeps the path to Queue and AI-saved move work clear without requiring setup ceremony.

Backfilled: The product source after the completed v0.5.1 record through the verified private-first onboarding deployment is classified in the v0.6.0 completeness ledger.

+Created0

    ✓Fixed0

      ↑Upgraded1

      • New people can create a private move in one short form and follow its Queue-to-saved-work loop.

        What: The empty workspace now creates its private boundary and first move together, optional route context stays optional, the Move overview explains the durable Queue and saved-work path, failure recovery stays inside the product, and AI guidance distinguishes hosted OAuth, helper-key tools, and the Partial Queue boundary.

        Why: The previous first visit exposed an internal household step and advanced setup language before a person had a useful move to return to, while AI setup could imply every connection door had the same tools.

        Where: Sign in, create the first private move from Your moves, then use the First useful loop on the Move overview.

      v0.5.0

      A working Assist With Moving first run

      August 13, 2026, 2:56 PM MST

      Assist With Moving now opens as one coherent product: the public entry reaches a usable sign-in, the empty workspace explains the move clearly, and chosen-AI setup starts with secure hosted OAuth.

      Backfilled: Every first-parent source after the v0.4.1 product cutoff through the verified Assist With Moving first-run deployment was classified in the v0.5.0 completeness ledger.

      +Created0

        ✓Fixed1

        • The Assist With Moving entry now reaches a usable sign-in and carries one current identity through the workspace, Queue, and chosen-AI setup.

          What: The public Assist domain now preserves the requested path while entering through the production Clerk-approved host. Public pages, auth framing, the signed-in shell, Queue guidance, packets, metadata, API/MCP copy, and agent guides use Assist With Moving; AI Connections recommends hosted OAuth before fallback API keys.

          Why: An ordinary visit to the Assist-domain sign-in previously showed only a legacy title and no usable control because the production identity rejected that origin. Mixed identity and key-first setup also made the first visit harder to understand.

          Where: Begin at assistwithmoving.com, continue into the empty workspace or Queue, and open AI Connections to copy the hosted movingmanifest.com/mcp endpoint.

        ↑Upgraded0

          v0.4.1

          Reliable sign-in for chosen AI connections

          August 12, 2026, 7:29 PM MST

          Chosen AI connections can now complete real Moving sign-in and keep useful, source-backed work in the move workspace through the recommended OAuth MCP connection.

          Backfilled: Every first-parent source after the v0.4.0 product release marker through the verified OAuth repair deployment was classified in the v0.4.1 completeness ledger.

          +Created0

            ✓Fixed1

            • Chosen AI connections can now finish browser sign-in and save durable move work through the recommended MCP endpoint.

              What: Moving now accepts the signed production OAuth access-token shape issued during browser consent while retaining issuer, signature, expiry, token-type, subject, client, and supplied-audience checks.

              Why: The first live connection exposed a mismatch between the released verifier and the token actually issued after consent, so a valid chosen AI could sign in but could not reach any move tool.

              Where: Connect a chosen AI with movingmanifest.com/mcp, then review its returned decisions, estimates, plans, and source checks in the move Overview under Saved work.

            ↑Upgraded0

              v0.4.0

              AI work that stays with the move

              August 12, 2026, 4:46 PM MST

              Assist With Moving now gives each person a clearer handoff desk and a durable chosen-AI workflow: Queue work stays attributable, and finished plans, estimates, decisions, inventory, locations, evidence, and source checks return to the move workspace instead of disappearing in chat.

              Backfilled: Every first-parent source after the v0.3.0 release-record marker through the verified August 12 production deployment was classified in the v0.4.0 completeness ledger.

              +Created2

              • A chosen AI can now do bounded move-planning work and save a complete, readable result back into the move workspace.

                What: The canonical OAuth MCP provides eight focused tools to brief and search a move, read selected records and private evidence, save move context and inventory, correct planning records, and preserve one complete result with decisions, estimates, plan sections, and honest source checks.

                Why: Useful AI work should become part of the durable move record, with provenance, replay protection, tenant boundaries, and human-visible results rather than remaining an unauditable chat answer.

                Where: Connect from AI Connections or the AI setup guide, then inspect returned work in a moves Overview under Saved work.

              • The Queue now shows Needs you, Working, Waiting for your AI, and Done as one clear, attributable handoff flow.

                What: Moving gained durable Queue records, bounded AI claims, exact ownership and delegation rules, readable activity and results, and responsive global and move-specific Queue workspaces while retaining compatible capture history.

                Why: A person needs to know what requires their answer, what an AI is doing, what is waiting to be picked up, and what finished without confusing operational retries or leases for extra product states.

                Where: Open Queue globally or inside a move; capture and specialized review paths remain available beside the canonical handoff flow.

              ✓Fixed0

                ↑Upgraded0

                  v0.3.0

                  A complete moving workspace for people and their agents

                  July 27, 2026, 10:08 AM MST

                  Assist With Moving grew from a basic inventory into a coordinated moving workspace: people and their AI assistants can capture evidence, organize belongings, plan spaces and transport, collaborate safely, and keep large moves understandable on any screen.

                  Backfilled: Every shipped source since the previous release marker was classified against the verified July 27 production deployment.

                  +Created8

                  • AI assistants can connect directly and complete real capture, inventory, box, image, transport, and queue workflows.

                    What: The hosted OAuth connection now provides purpose-built tools for reviewing captures, editing items and boxes, working with images, configuring moves, and planning transport. The local API-key connection remains a separate supported door.

                    Why: A connected assistant can now help finish a move workflow instead of stopping after discovery or requiring a person to translate every step into manual edits.

                    Where: Connect an assistant from AI Connections, then use the Queue, Inventory, Movable Units, Spaces, and Transport workflows.

                  • Moves now open into a focused workspace with clear paths to inventory, movable units, operations, planning, and results.

                    What: The product navigation was rebuilt around Moves, Movable Units, and Items, with move-specific work grouped inside the selected move and a useful overview replacing empty setup forms.

                    Why: The structure follows how people think about a move: choose the move, understand its current state, then act on the belongings or operation that needs attention.

                    Where: The change spans the signed-in home, move directory, move overview, workspace navigation, and movable-unit detail.

                  • Move owners can invite participants and deliberately share queue work with the right people and assistants.

                    What: Assist With Moving now understands move participants, durable invitation claims, per-person queues, agent provenance, and explicit delegation consent.

                    Why: A household move is rarely a one-person job. These boundaries let several people contribute without making every capture or assistant connection visible to everyone by default.

                    Where: Manage collaboration from the move Participants experience and each participant's Queue.

                  • Spaces and Transport turn room capacity, vehicle capacity, placement, and trip planning into one visual planning workflow.

                    What: People can define present and destination spaces, describe transport resources, calculate usable cargo volume, review capacity, and place belongings into the plan.

                    Why: Inventory becomes operational when it answers where belongings are now, where they are going, and whether the available rooms and vehicles can hold them.

                    Where: Open Spaces & Transport inside a move; connected assistants can work with the same planning concepts.

                  • Photo and document captures now move through a clear, reviewable queue and stay attached to the inventory they create.

                    What: Capture supports move switching, background uploads, structured item details, reusable photos, entry detail views, and automatic evidence attachment after processing.

                    Why: Evidence is useful only when people can see what is waiting, understand what an assistant produced, and trace the result back to its original photos or document.

                    Where: Use Add to Queue, the move Queue, item detail, and the Photos workflow.

                  • Items, boxes, totes, and other movable units gained practical controls for naming, classification, placement, sale, conversion, and removal.

                    What: Inventory records now have stable codes, thumbnails, editable names and descriptions, clearer measurements, item-to-box conversion, disposition actions, manual creation, and focused detail views.

                    Why: Real inventories change while packing. These controls let people correct what something is and what should happen to it without rebuilding the record.

                    Where: The controls appear across Items, Movable Units, item detail, box or tote detail, Sell, and admin cleanup.

                  • Assist With Moving can be installed on a phone for faster access during packing and move-day work.

                    What: The public app metadata and install experience now support adding Assist With Moving to a mobile home screen.

                    Why: Packing work happens away from a desk, so quick app-like access reduces friction when capturing or checking belongings in place.

                    Where: Use the browser's install or Add to Home Screen path on a supported mobile device.

                  • Public guidance now explains the real product and the direct remote-assistant connection path without fabricated examples.

                    What: The public site gained honest product panels, About and FAQ pages, and corrected AI connection guidance that distinguishes the supported remote path from local tools.

                    Why: People should understand what the product actually does and choose a connection method that works before they create an account or configure an assistant.

                    Where: Review the public home, About, FAQ, AI, and MCP guide pages.

                  ✓Fixed5

                  • Private move data, assistant credentials, media inputs, and administrative controls now stay behind stricter access boundaries.

                    What: Authorization checks were tightened across API keys, agent connections, media retrieval, route guards, administrative setup, and permanent data operations.

                    Why: A moving inventory can contain addresses, valuables, documents, and household relationships. The product must reject ambiguous or outdated access instead of assuming it is safe.

                    Where: The protections cover signed-in routes, REST and MCP access, media tools, API-key lifecycle, and production configuration.

                  • Photo uploads, previews, and assistant image delivery recover cleanly instead of failing silently or leaving captures stuck.

                    What: The media path now handles gateway responses, authenticated display URLs, image dimensions, retries, aborts, storage signing, and failed-upload state more reliably.

                    Why: Photos are the evidence layer for inventory and claims. A failed upload must be visible and recoverable, and a successful upload must remain connected to the right record.

                    Where: The fixes protect Add to Queue, Photos, item and box evidence, and image tools used by connected assistants.

                  • People and assistants now receive useful, safe errors when a tool, record, or backend dependency cannot complete the request.

                    What: Tool failures and mutation errors are translated into actionable product messages, missing records degrade safely, and the app shell remains honest when its backend is unavailable.

                    Why: A generic failure invites repeated actions and accidental damage. A clear boundary tells a person or assistant what can be corrected and what must wait.

                    Where: This applies to agent tools, inventory saves, missing box records, signed-in error states, and provider-safe loading fallbacks.

                  • Inventory measurements, conversions, deletion cascades, sale values, and cleared move notes now remain internally consistent.

                    What: Derived volume fills missing measurements, item-to-box conversion handles assigned heavy units, hard deletion cleans dependent records, and nullable updates preserve intentional clearing.

                    Why: Plans and packets are trustworthy only when related records agree after an edit or removal, including less-visible dependent data.

                    Where: The fixes protect movable-unit conversion, inventory deletion, sale details, measurements, and assistant-driven move updates.

                  • A move manager's assistant can work an explicitly shared participant queue without being blocked by the manager relationship.

                    What: Queue authorization now follows the move's delegated access rules instead of treating a manager's connected assistant as unrelated.

                    Why: Explicit sharing should work consistently for both the manager and the assistant acting on the manager's behalf, while unshared queues remain private.

                    Where: The fix applies when a move manager delegates work from the Participants and Queue workflows.

                  ↑Upgraded4

                  • Core move, inventory, load-planning, sign-in, and navigation surfaces now adapt cleanly from phones to wide desktops.

                    What: Navigation shifts by screen size, dense tables become focused mobile cards, hidden desktop trees no longer mount on small screens, and headers and sign-in cards stay inside the viewport.

                    Why: Moving work happens on phones in rooms and trucks as well as on desktop planning screens. Each device should get one usable interface, not overlapping layouts.

                    Where: The upgrades span the app shell, Inventory, Load Planner, workspace header, AI setup, and authentication pages.

                  • Search, sorting, pagination, density context, and stable return positions make large moves faster to scan and manage.

                    What: Move and inventory lists gained search and richer sorting, the load planner pages through large result sets, and returning from detail keeps a person's place.

                    Why: A workflow that feels fine with ten belongings can become unusable with hundreds. Discovery and position memory keep the interface predictable as a move grows.

                    Where: Use the move directory, move switcher, Inventory, Movable Units, Spaces & Transport, and Load Planner.

                  • Loading, saving, navigation, empty states, undo, and status language now give clearer feedback without losing a person's context.

                    What: The interface added consistent skeletons and empty states, save confirmation, double-submit guards, section-preserving navigation, truthful counts and labels, Escape behavior, and hardened undo.

                    Why: Good feedback answers three questions during a busy workflow: did the action happen, what can I do next, and can I safely recover from a mistake?

                    Where: These refinements appear throughout move setup, inventory detail, queues, load planning, launchpad, and product error boundaries.

                  • A required production check now catches lint, type, build, and critical contract failures before main can ship.

                    What: The repository gained a focused required CI gate aligned with the fact that every merge to main deploys production.

                    Why: Automated release checks make routine improvements safer by stopping known classes of broken builds before they reach customers.

                    Where: This protects every production deployment even though the checks themselves run behind the scenes.

                  v0.2.0

                  Item detail Other Photos gallery

                  June 20, 2026, 8:54 AM MST

                  The item detail Evidence tab shows extra uploaded photos alongside the main item image.

                  Backfilled: Added after the gallery shipped. This release-note-only addition did not create or silently renumber a second v0.2.0 release.

                  +Created1

                  • Item evidence includes an Other Photos gallery with a clear empty state and upload guidance.

                    What: Additional item photos appear together below the primary image, while an empty state explains how to add the first extra photo.

                    Why: A person reviewing condition or ownership evidence can find the full visual record without guessing whether more photos exist.

                    Where: Open an item's Evidence tab.

                  ✓Fixed1

                  • The main item image no longer repeats inside the Other Photos list.

                    What: The evidence strip filters out the image already used as the primary thumbnail.

                    Why: Each visible image now represents distinct evidence instead of inflating the apparent photo count.

                    Where: Open an item's Evidence tab.

                  ↑Upgraded1

                  • Item evidence review keeps the primary image and supporting photos in one understandable view.

                    What: The evidence layout distinguishes the representative image from its supporting gallery.

                    Why: That hierarchy makes quick review easier while preserving all uploaded evidence.

                    Where: Open an item's Evidence tab.

                  v0.2.0

                  MCP OAuth discovery preservation

                  June 19, 2026, 2:02 PM MST

                  The production AI connection contract remains discoverable while private MCP requests still require authorization.

                  +Created1

                  • Public OAuth discovery metadata tells compatible AI assistants how to begin a protected connection.

                    What: Assist With Moving publishes the standards-based protected-resource document needed to identify its authorization boundary.

                    Why: Discovery lets an assistant find the correct sign-in flow without making private move data public.

                    Where: This powers compatible remote MCP connection setup.

                  ✓Fixed1

                  • Unauthenticated MCP requests receive an authorization challenge instead of access to move data.

                    What: The public discovery document and the protected tool endpoint retain separate access behavior.

                    Why: An assistant needs enough public information to connect, but inventory, photos, credentials, and household records must remain private.

                    Where: This protects the production MCP endpoint.

                  ↑Upgraded1

                  • The visible version and release trail now preserve the expected assistant-connection contract.

                    What: The release record ties the public discovery behavior and protected endpoint to a visible application version.

                    Why: A durable record makes future connection changes easier to compare and verify.

                    Where: Review the What's New page and AI connection documentation.

                  v0.1.0

                  Initial release-log baseline

                  June 19, 2026, 6:05 AM MST

                  Assist With Moving established a public, privacy-safe record of product-visible changes.

                  +Created1

                  • The /updates page became the canonical place to understand product changes.

                    What: The first release record established coverage for the move workspace, inventory, photos, planning, packets, API, and assistant surfaces.

                    Why: A single findable history helps customers and collaborators understand how the product is evolving.

                    Where: Use the public footer or visit /updates.

                  ✓Fixed1

                  • Release notes describe product outcomes without exposing private moves, credentials, or internal handoff details.

                    What: The public record stays at the capability and user-outcome level.

                    Why: Transparency about product changes should not disclose the personal data the product is designed to protect.

                    Where: This boundary applies to every public release entry.

                  ↑Upgraded1

                  • Release entries use the application package version as their visible version source.

                    What: The page, typed release data, sitemap, and package version were connected into one release-note foundation.

                    Why: One version source reduces drift between what the code reports and what customers see.

                    Where: The current application version appears at the top of /updates.

                  Assist With Moving organizes move records, evidence, and documentation packets.

                  Need help? Everything goes through the Assist With Life support desk. There is no support email address — Assist With Moving does not run a mailbox.

                  FeaturesYour AIAboutFAQAPIMCPPCS movingClaims inventoryPrivacyUpdatesTermsSupport