A local-first Strands agent for everyday documents

Your home has a paper trail. Make it useful.

FolderHome finds the current document, connects the right contact, drafts the next step and waits for your exact confirmation before anything changes.

Local-first Exact confirmation Reversible file actions

Try the guided case Install and run locally pip install · your own folders · your own model

CASE / 08·22

SYNTHETIC DOSSIERHyundai i10

LOCAL

Current policy: SYN-I10-2026
Claims contact: Jordan Current
Older version: Keep as evidence
Next review: 26 Aug · 10:00

documents→plan→confirm

Cloud mode

Try it here in cloud mode

The real FolderHome master agent runs on a synthetic household of 104 example documents. External actions stay disabled; every turn is budget-metered.

Interactive case file

One request. Four bounded workflows.

Scripted synthetic walkthroughThis public page runs no backend and changes no files. The repository command runs the real local adapters.

Free chat

Your own words, a synthetic household

Ask about insurance, health, contracts, taxes or the calendar. Nothing here is real data.

Guided case

Try the test case: Hyundai i10 insurance claim

Guided walkthrough with four bounded steps: search policies → resolve contact → draft claim → exact /confirm → four synthetic files created.

Free exploration

Try it in your own words

Real FolderHome master agent on a synthetic household (104 example documents: insurance, health, taxes, contracts, calendar…). Nothing is real data, external actions disabled, every turn budget-metered.

FOLDERHOME

Tell me what happened. I will search first and propose a bounded plan; nothing is executed yet.

PROOF, NOT PROMISES

The safety boundary is part of the product.

Demo architecture: one Strands master, exact confirmation, typed local adapters — Synthetic accident-demo view: four demo adapters in the guided case; the free chat uses the full read-only tool set on a synthetic household. The hosted runtime was verified live with Amazon Bedrock on 2026-09-13. Household execution stays local behind exact confirmation.

Agent flow: request → search → bounded plan → confirmation → local adapters — Synthetic accident-demo view: four demo adapters in the guided case; the free chat uses the full read-only tool set on a synthetic household. The hosted runtime was verified live with Amazon Bedrock on 2026-09-13. Household execution stays local behind exact confirmation.

Open the current diagram full-size · Read the full architecture map and limits

STRANDS

One master agent

Natural conversation routes into typed, bounded tools and specialists.

LOCAL

Paths stay out of plans

Logical resource IDs keep household locations outside model-visible payloads.

GATED

Hash-bound confirmation

Search is not permission. Execution needs the exact displayed plan ID.

AWS · VERIFIED LIVE

AgentCore runtime on Bedrock

Direct-code ZIP runtime, verified live on 2026-09-13 with Amazon Bedrock Nova Micro; every hosted turn is budget-metered and synthetic-only. The ARM64 container is a separate packaging path.