01
Start with your home
Sign in to Homes. Manage the home records you already keep, or ask your AI to help set up your home and rooms. If you are looking for a home, start a private search. Nothing runs automatically.
Your home records · your chosen AI
Give your AI the field notes—not the house keys.
Assist With Homes keeps your homes, devices, projects, routines, documents, and decisions. A compatible AI can research and reason, then save useful results back into the same private home record you already use.
Five steps · no protocol knowledge needed
A handoff does not send itself.
Queue remembers what you want done. Connecting only puts your chosen AI at the door; you decide in Homes what it may touch, and you still have to ask it to open the handoff and begin.
02
Add Homes to your AI
In your AI's connections or remote tools settings, add the Homes address shown above. The client must support remote MCP with OAuth.
03
Sign in and allow
Use the same Assist With Homes account that owns your home records, then click Allow. These two steps are the ones nobody can do for you—and clicking Allow is the approval. The connection is live at that moment.
04
Adjust it if you want to
The client appears in Your AI inside Homes already able to do everything Homes offers a connection—look, save its research, keep the append-only record of the home you own, attach private photos, change what you have said you are looking for, and archive reversibly. Nothing is waiting for you to switch on. Each of those has a switch you can turn off whenever you like, and you can narrow which searches it reaches or take the whole thing back.
05
Ask your AI to begin
Ask your AI to open your home records and waiting requests. It can save related changes in batches, read stored manuals and bills, and finish the Manage requests it answered.
First message to your AI
“Open my home records and waiting requests. Help me maintain my home, save related changes in batches, and finish the requests you answer. Tell me when information is missing rather than guessing.”
Using another AI?
Add the same address only if that client supports remote MCP and OAuth. Exact client-by-client steps stay unpublished until that path has completed sign-in, read, save, reconnect, and cleanup.
If tools look stale
After Homes adds a tool, or you change what an AI may do, start a new conversation: most AI apps load the tool list once per conversation. If it is still out of date, use your app's refresh or reconnect control for Homes, then ask your AI to open your home records or your home search. Homes refuses a stale call either way, and your records stay in Homes. If something fails, your AI is given a reference number (req_…); the same number appears beside that call in your AI settings.
Disconnect clearly
Take access back from Your AI inside Homes; it stops on that AI's next call, whatever the client still thinks it holds. Then use your AI client's clear-authentication or disconnect control and remove the saved Homes server if you want the address forgotten there too.
You decide, in Homes
You decide what it may do.
Signing in and clicking Allow is the approval, and it gives an AI everything below — including your stored photos, what you have said you are looking for, and reversible archiving. There is no box to tick and nothing waiting on a settings page. Inside Homes you take any of it back at any time with a per-AI switch, and it takes effect on that AI's next call.
Included when you allow
Look
See the home searches it may use: the homes on the list, your saved places and priorities, the evidence and comparisons on file, and the decisions you have already recorded.
Included when you allow
Save its findings
Add and fix its own work: candidate homes it found, sourced research notes, and decisions with the reasoning written out. This is the lane it can clean up after itself — if it gets a number or a note wrong, it can go back to the same record and correct it. It does not include changing what you said you want, and it does not include archiving a home.
Included when you allow
Keep your records
Write dated entries into your home's record as you dictate them, add cost and progress notes to your projects, and file what it researched. Every line is added rather than replacing anything, and every line carries the name of the exact model that wrote it. It can also mark a project done, or move its status and readiness as the work happens — even on a project whose status you set yourself, because that is a fact about the job rather than something you wrote, and the record shows it was your AI that moved it. It cannot rewrite a sentence you wrote — the most it can do to your words is add a line underneath — and it can never say whether a buyer would have to be told about something. That judgment is only ever yours.
Included when you allow
Attach photos
Attach private photos and PDF documents to home records this AI may reach, in batches of up to eight files. Photos are decoded and location metadata is removed. Stored PDFs can return derived text and clean page images while originals remain unchanged. Files use your storage and are never shared or published. Turn off “Look at and attach private photos and documents” on the connection to take this away.
Included when you allow
Change your criteria
Start home searches and add or reorder what matters in them: must-haves, nice-to-haves, things to avoid and deal breakers, with how much each one counts. What you wrote yourself stays yours — an AI can add a criterion beside it but never change or remove it. Turn off “Change what you are looking for” on the connection to take it away.
Included when you allow
Archive
Archive a home so it leaves the active list, or bring one back. Archiving is always reversible, is always recorded as this AI's doing, and is never a delete. It changes what you see on your own list rather than only what the AI wrote, so it has its own switch: turn off “Move things out of your active lists” to take it away.
Not offered at all
Exporting your search and permanently deleting a home are deliberately not offered over an AI connection. They are not switches waiting to be turned on later—they stay human actions inside Homes, with their own confirmation and their own record. Homes also keeps the exact sentence you agreed to, so consent stays readable afterwards.
Your AI
See your connected clients, every read, save, archive, and refused attempt, and take access back.
You-chosen access
The AI cannot pick an owner, a home search, or its own authority. Homes re-reads the permission you chose before every single call.
Bounded context
Search scans at most 200 candidates; detail reads are deliberately small and explicit.
Visible results
A complete result lands in the canonical home record, can finish its exact Queue handoff, and links from Queue and Results to the saved records.
Photo upload · exact boundary
Homes permission and AI-app permission are different things.
Homes controls identity, its grants, record reach, and final save. Your AI app or organization controls whether its code can read a local file and send bytes to assistwithhomes.com. An error should name which side stopped the work; reconnecting Homes cannot fix a client network rule, and widening a client network rule cannot create a missing Homes grant.
- Identity and OAuth consent
- Homes
Your Assist With Homes sign-in proves the person and creates the connection. - Grant and record authority
- Homes
Homes decides which actions and records the connection may reach and derives the person and home server-side. - Per-action confirmation
- Homes
Destructive, public, sharing, invitation, payment, permission, and outside-world actions stay separately confirmed or unavailable. - Local-file access
- Your AI client
The AI app or organization decides whether its code can read the file selected on your device. - Code and network access
- Your AI client
The AI app or organization decides whether its code can PUT bytes to assistwithhomes.com; Homes cannot change that policy.
One photo, one replay-safe lane
Measure and SHA-256 one JPEG, PNG or WebP up to 2250000 bytes (2.25 MB), call homes_begin_media_upload with one stable operationId, PUT the exact bytes to the returned no-redirect assistwithhomes.com URL, then call homes_finish_media_upload with the same operationId and sessionRef. The public route shape is https://assistwithhomes.com/api/mcp-media-upload/{sessionRef}/{token}, and the exact ceiling is 2250000 bytes (2.25 MB). Backblaze and object keys stay private behind Homes.
For a photo set, measure and hash the whole set first. Use a small bounded number of independent lanes, one operationId/session/PUT/finish per photo. Retry only failed lanes with their original ids; never make the set one giant transaction.
Claude-specific · checked 2026-09-02
If Claude blocks the PUT
Claude-specific note, checked 2026-09-02: if Claude's code-execution PUT is blocked, the least-privilege setting is to allow exactly assistwithhomes.com in Settings → Capabilities. All domains also permits it but is broader and optional. Start a new Cowork conversation after changing that setting. Backblaze is never a domain to allowlist; Homes keeps that private provider hop behind its own server.
Sources: Claude file and network access and Cowork network settings. Other clients stay client-neutral until their exact path is dated and sourced.
39 tools · 6 movements
From messy search to a decision record — and on into the home you keep.
Orient
brief · search · read · saved photos
Find the right home project, see its waiting AI handoffs, shortlist the relevant candidates, and retrieve the evidence already on file—including the photos you captured yourself.
Compare
context · tradeoffs · priorities
Line up homes against the buyer's actual priorities without flattening uncertainty into one mysterious score.
Preserve
candidate · place · observation · batches
Add or correct the durable record, including source checks, map context, and research sections that can be revised later. One pass covering several homes is one approval, not one per home.
Decide
complete result · decision
Return a complete research pass in one approval, finish its exact Queue handoff, or make a small later correction without duplicating the work.
Keep
home overview · record context · record search · entries · projects · research · photos
The home you already own. Your AI reads the shape of the whole home record, opens one item with the gaps it honestly has, and writes dated entries in your words, project cost and progress notes, and the research it did. It can inspect private record photos and add a privacy-clean photo of its own — both arrive when you connect it, and the photo switch at /settings/ai is how you take either one back. Every addition is signed with the exact model that made it.
Suggest
suggestions · this connection
What your AI thinks you should do next goes beside your queue, never on it: lettered options, the consequence of each, and the lines it is quoting. You accept one — which is what creates the work — or decline it in your own words. It can also tell you exactly what it is allowed to do, hand some of that back, or ask you for more.
Exact live tool catalogue (39)
- 01
homes_list_ai_activity— this connection's own recent Homes activity, so a working pass can resume rather than restart. - 02
homes_save_complete_result— PREFERRED HAPPY PATH for a home search; candidate facts, evaluated priorities, sources, up to 8 research sections, one decision, and optional exact-version Queue handoff completion in a single durable call. - 03
homes_get_workspace_overview— FIRST CALL for the home you own; the homes on file, how much of each record family exists, and every queue item waiting for an AI across all context kinds. - 04
homes_get_record_context— one record's bounded context by family and ref: facts, recent entries, connections, captures, and for devices their sourced extracts and FAQ answers, plus an honest account of what is missing. - 05
homes_list_records— every record of one family, a page at a time: filtered by home, room, thing or status through an owner-first index — and for the Library by kind, which returns a year of bills in the order they are dated — with an opaque cursor and an honest isDone, so a caller can prove it has seen the whole set. - 06
homes_search_records— bounded title and reading search across the record families, saying exactly which families it covered and where it stopped. - 07
homes_get_record_media— bounded retrieval of 1-8 active private Manage photographs as real image bytes, using tiny cleaned copies first and a strict total response budget. For stored PDF text and clean page images use homes_get_record_documents; this photo tool never returns PDF originals. - 08
homes_save_record_entries— up to 25 dated entries in one approved pass, stored verbatim and signed with the exact client and model, optionally moving the status of a project an entry is about. An entry with no known day is stored as reported today rather than as if it happened today. Never sets disclosure: that judgment is the person's alone. - 09
homes_save_project_update— mark one project done or change its status, readiness, priority and where it is filed, and append a cost or time recap line or a line under its reading — each only where the authorship seam allows it. - 10
homes_save_projects— create or amend up to 25 projects on a home the person owns in one approved pass, each attributed, with a per-item result. Work the person asked for; an assistant's own idea still goes through homes_suggest_directives. - 11
homes_save_devices— create or amend up to 25 of the durable things in a home — systems, appliances, fixtures, furniture, vehicles — in one approved pass, each attributed, with a per-item result: what it is, which home and room it is in, what it hangs off, and what paperwork is on file. Measurements and states go on with homes_save_facts, which appends rather than replaces. - 12
homes_save_routine_update— bring one recurring thing up to date: move the next due date on when it has passed, propose or amend an unconfirmed cadence, offer candidate anchor dates, say where it is attached, and log what actually happened. Confirming a cadence is the person's alone and there is no argument here that could. - 13
homes_save_research— create or amend research topics and library documents including dated utility bills, and file source-required findings — specs, parts, intervals, and usage or cost readings with a billing period — plus FAQ answers, all attributed so the answer outlives the chat. - 14
homes_save_facts— append up to 25 durable facts — pool volume, filter size, price paid, warranty date — to a home, area or device. Append-only, and every one is stored unconfirmed: confirming is the person's click and no argument here can set it. - 15
homes_begin_media_upload— authorize one exact private JPEG, PNG, WebP or PDF for a byte-capable client; returns a short-lived no-redirect PUT on assistwithhomes.com in structuredContent.upload.url. A document keeps the storage ceiling rather than the reply budget, and is stored byte-for-byte as it arrived. - 16
homes_finish_media_upload— finish one first-party-relayed upload after rechecking the current grant, target, expiry, provider-observed length, type, SHA-256, exact stored version, and a full image decode where the file is a photograph. A PDF is byte-sniffed and stored unchanged; nothing renders it. - 17
homes_attach_media— attach one private photo or PDF by tiny inline base64 or guarded public-https fetch, or reserve a pending slot that only the person can fill from their device. Any record family is a valid target, including a Library item, so a bill or a manual hangs off its own document. - 18
homes_suggest_directives— draft up to 10 suggestions beside the Queue — never in it — each with lettered options, their consequences, and quoted evidence. Only the person accepts or declines one. - 19
homes_queue_for_later— write down 1-10 requests the PERSON just asked for ("add that to the list") as their own Queue items in Waiting on AI, marked as left by their AI at their request. Starts nothing. The AI's own ideas go through homes_suggest_directives instead. - 20
homes_suggest_preference— propose up to 5 standing preferences ("check the warranty first") for the person to accept or decline on /preferences. Guidance, never permission; nothing is in force until they accept the exact sentence. - 21
homes_get_records— Batch checkout of up to 10 home records with selected sections and explicit per-item results. - 22
homes_get_record_documents— Read up to 8 stored PDF attachments as derived text or clean page images, with per-document continuations; original bytes and metadata stay private. - 23
homes_save_home_setup— Create or amend up to 100 homes and rooms with stable item keys; rooms can refer to a home created in the same batch. - 24
homes_save_routines— Create or amend up to 100 routines with per-item receipts. New routines remain unconfirmed; confirming cadence stays person-only. - 25
homes_save_calendar_events— Create or amend up to 100 home calendar events with stable item keys and per-item results; no external calendar or notifications. - 26
homes_save_services— Save up to 100 home-linked service records in the Library: provider, utility type, contact, website, safe account reference and linked bills. - 27
homes_save_people— Save up to 100 people and companies in the one directory shared by finding, buying, managing and selling a home — agents, inspectors, lenders, contractors, utilities, insurers, neighbours — with role, contact details, the company a person works for, and the home they are about. Homes never contacts anyone. - 28
homes_save_coverage— Save up to 100 warranties, home warranties, insurance policies and service plans on a home or one device: provider, policy number, what is covered, start and end dates, and the expiry reminder (on by default). Homes never files a claim. - 29
homes_save_searches— Save up to 100 home searches: name, buy or rent, where, timing, the ordered weighted criteria (−10…+10, five tiers, an unknown scores nothing), the people involved, and which homes are in each search and where each stands. A model adds and tunes its own criteria and never changes one the person set. - 30
homes_save_listings— Save up to 100 dated listings, each filed under its home — an existing home, or a new home marked potential — with offer, status, dates, price, source link, listing agent and facts that each carry who reported them; optionally adds the home to a search. Homes never scrapes or follows a listing feed. - 31
homes_save_visits— Plan or record up to 100 visits to homes, each on a date and optional time, with the listing shown, the search it serves and who shows it. A tour day is a date's visits. A model never rates a visit. - 32
homes_get_search_results— One search's homes scored against its criteria: points, what holds, what fails, what is unknown (an unknown scores nothing), musts missed and deal-breakers, each with the fact it read and who reported it. A check, not a filter: every home in the search is returned. - 33
homes_set_archived— Archive or restore up to 100 records of any kind — a home, a listing, a home in a search, a device, a project. Never a delete: an archived record keeps every word and comes back exactly as it was. - 34
homes_get_lists— the person's Lists, or up to 10 Lists with every entry in order — linked records by ref and current name, plain lines, reasons and checklist ticks. - 35
homes_save_lists— Create Lists and put up to 50 records or plain lines on each per item, with reasons; tick or annotate checklist entries. Keyed items, per-item results; never removes an entry or archives a List. - 36
homes_save_manage_result— PREFERRED Manage working pass: up to 100 records across related batches, with stable operation keys and result-ref aliases; completes up to 10 exact-version Manage handoffs only if all submitted writes succeed. - 37
homes_begin_media_uploads— Begin up to 8 private photo/PDF uploads together, with per-file operation IDs and results. Each original still has its own byte transfer. - 38
homes_finish_media_uploads— Finish up to 8 private photo/PDF uploads together, with per-file operation IDs and results. Each original still has its own byte transfer. - 39
homes_manage_connection— the connection describing its own authority — scopes, switches, reach, expiry — and filing one exact owner-approval request. It can hand authority back; only the person's click widens it.
10 switches · yours to turn down at any time
What it may do, per assistant.
Permissions decide the broad shape. These decide the detail, per AI, and they are checked on every single call alongside the permission — never instead of it. A switch can only ever take something away: turning one on never grants anything the permission did not already carry.
- Read your homes and their records
- Look at your homes, rooms, devices, projects, routines, entries, research and library items, and the home searches this connection may reach. Turn it off and this AI can still see what it is allowed to do, and nothing else.
- Look at and attach private photos and documents
- Read the pictures saved with your homes and derived text or clean pages from stored PDFs, and attach private photos and documents. These abilities arrive with signing in. Turning it off withholds this content and prevents new attachments. Original files and metadata are never returned to the AI.
- Save the research it does
- Save and correct the research it does itself: homes and listings it found or you handed it, each fact credited to who reported it, and finished research results. This is its own lane — it can go back and fix what it wrote.
- Keep the record of the home you own
- Write in your home's record as you dictate it: dated entries in your words, project cost and progress notes, research topics and documents. Every line is added rather than replacing anything, every line carries the exact model that wrote it, and nothing it writes can overwrite a sentence you wrote.
- Change what you are looking for
- Change your home searches: what matters in each, how much, and which homes are in it. It adds criteria and tunes its own, and never changes one you set. Its own switch, separate from keeping your records, because an assistant cannot put back a deal breaker it wrote over — it never knew what was there. It arrives on, and this is where you take it away.
- Read and answer the queue, and write requests down when you ask
- Read the work you marked Waiting for your AI, across home searches and the homes you own, and return a result to the exact item. It also lets it write a request down for you mid-conversation — say “add that to the list” and it lands in Waiting on AI as your own request, marked as left by your AI at your request. Nothing it writes down starts on its own, and its own ideas still come to you as suggestions. Turning it off hides the queue from this AI and stops it writing requests down; it never changes what is already in your queue.
- Propose suggestions
- File suggestions beside your queue — options with their consequences and the evidence behind them — for you to accept or decline. A suggestion never runs; accepting one is what creates work.
- See where your homes are
- Be told where a home actually is: its address line and locality. Turn it off and records still come back, with the location withheld and the response saying it was withheld.
- Read entries you marked private
- Read entries you marked private. Turn it off and those entries are left out of every read, and the count of what was left out is reported so their absence is never a silent gap.
- Move things out of your active lists
- Move a home, a listing or any other record out of your active lists, and bring it back. Always reversible, always attributed, and never a delete. It arrives on, and this is where you take it away.
Only you, always
These three are not switches and never will be. No permission on this page turns them on, and no AI connection Homes can issue reaches them.
- — Delete anything, permanently or otherwise.
- — Share or publish any part of your home records.
- — Widen its own access, or approve a request it made for more.
First useful conversation · finding a home
- 1. Your AI opens your home records and sees any AI handoff waiting for it.
- 2. Use
homes_get_search_resultsto see how each home in a search measures up against what you said matters. It checks; it never hides a home. - 3. Research outside Homes, then file each dated listing under its home with
homes_save_listings. Every fact says who reported it, and your AI's stay unconfirmed until you confirm them. - 4. Tune your search with
homes_save_searches: your AI can add criteria and adjust its own, never change one you set.
Deliberately absent
No listing-feed scraping, full export, deletion, member changes, seller or real-estate-agent outreach, appointment booking, offers, payments, signatures, purchases, or hidden outside action. A Queue item never grants more authority. It is coordination context only; the permission you chose in Homes controls every read and write, and is re-checked on every single call.
Live connection
Assist With Homes publishes one production address, one Clerk sign-in boundary, and one place inside Homes to inspect or revoke an AI's access. Exact client compatibility remains a separate proof for each named client.
Built and checked
A permission you set, deciding which home searches an AI may use and whether it may also attach private photos, change your priorities, or archive; a connected-client list with first and last use; a readable history including refused attempts; immediate revoke and disconnect; and the joined result path across all 39 tools.
Partial
Named clients, reconnect behavior, and mobile setup require separate exact proof. Each AI app registers itself with the sign-in service when it first connects, so the name you see is the name the app gave, not one Homes has verified. Recognise it before you click Allow.
Later
Participant-private views, professional portfolio governance, and outside-action handoffs. Export and permanent deletion are not on this list: they are deliberately not offered over an AI connection.
If a connection will not work
Assist With Homes is part of the Assist With family. Support runs through Assist With Life Support. There is no direct email contact for Assist With Homes—no support mailbox exists, and none is planned. Bring the client name, the step that stopped, and the exact message you saw.
Named client instructions appear only after that exact client completes a safe sign-in, read, write, web-visibility, cleanup, and reconnect journey.
AI-readable guide