When should you use it?
- You rent in New York City and repairs are being ignored
- You want complaints that cite the right code class
- You need to track complaint numbers and inspection dates
Not for: Filing duplicate or exaggerated complaints; Legal advice about rent, leases or eviction; contact a tenant group or lawyer
What do you need, and what do you get?
You need
- Your building's address or BIN
- Photos and dates for each problem
- Public HPD violation and DOB complaint data
- NYC's Housing Maintenance Code
You get
- A table of each issue, code section and hazard class
- Draft complaint text you submit through 311
- A tracker of complaint numbers and inspection appointments
How does it work, step by step?
- Look up the building's recordSearch HPD's open violations and DOB complaints for your building to see what's already known.
- Document each problemPhotograph and date every defect in your unit, one issue at a time.
- Map issues to the codeMatch each problem to the housing maintenance code section and note its class; immediately hazardous conditions such as no heat or hot water get faster inspections.
- Draft accurate complaintsWrite one complaint per real issue citing the section, and file it yourself through 311.
- Track and follow upLog complaint numbers, inspection dates and outcomes, and respond to inspector requests with your photos.
The prompt
Our own prompt, inspired by Argona0x (@Argona0x) and written to work in Claude, ChatGPT and Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
I rent at {address} (BIN {bin}) in New York City. Problems in my unit with dates and photo notes: {issues}. Public records for the building: {hpd_violations} {dob_complaints}. For each problem: identify NYC's Housing Maintenance Code section it likely violates and its hazard class, note whether a matching violation is already open, and draft a short, factual 311 complaint. Don't exaggerate or combine issues. Finish with a tracker table: issue, section, class, complaint draft ready, evidence I still need. Mark anything that needs a tenant advocate's advice.
Inspired by Argona0x (@Argona0x): my landlord raised my rent by $400. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The original story describes staggering filings so the complaints didn't appear to come from a single tenant; file honestly and accurately instead, since false or inflated complaints can backfire.
- Rent and lease rights are separate legal questions; talk to a tenant organization before acting on them.
Our take
Strip out the viral framing and there is a useful, legitimate pattern here: tenants who cite the exact code section and hazard class get faster, more serious responses than those who describe problems vaguely. New York makes the building's violation and complaint history public, and an assistant is good at matching a photo-documented problem to the relevant section of a long code. Where we part ways with the original is automation of the filing itself. Submitting complaints on a timed schedule to avoid looking like one tenant is the kind of tactic that undermines credibility, and every complaint should describe a real, current condition. Keep the human in charge of submitting, and keep a clean evidence trail with dates and photos. The outcome he reports, fines and a rent freeze, depends on city rules and on inspectors confirming the conditions, so don't expect the same result. A local tenant association can tell you what applies to your building and what your rights are.
Where the time goes back: Reading a long housing code and a building's violation history is done for you, so your complaints are specific the first time.
FAQ
Did the AI file complaints automatically?
Is this only for NYC?
Source and credit
Inspired by Argona0x (@Argona0x). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- my landlord raised my rent by $400
- Creator
- Argona0x (@Argona0x)
- Published on
- X
- Original date
- Apr 30, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.