ChatGPT DotsUndisclosed

Two days of Operator applying to apartments: about 20-30 listings contacted, a first viewing, and one page that blocked it

Vontaxis(Reddit 用户 u/Vontaxis,原帖作者本人,自述连着两天用 Operator 申请公寓)Reddit · 2025-02-06

Read original

Saved text / editorial summary

原帖正文(Reddit r/OpenAI,作者 u/Vontaxis;本轮经 Reddit 公开 Atom feed 取得,以下英文部分逐字未改写): “I used the last two days Operator for applying to apartments and it worked quite well. It wrote to around 20-30 listings and I had today my first visitation. There was one page that apparently blocked it. I fear that this is going to happen more in the future” 中文对照:作者写自己连着两天用 Operator 去申请公寓,效果「quite well」;它向约 20 到 30 条房源写了申请或联系信息,作者当天有了第一次看房。另有一个页面似乎把它挡住了,作者担心以后这种情况会更多。 注:原帖原文是 It wrote to around 20-30 listings,只说明「向约 20-30 条房源写了东西」,没有写是填表、发信还是别的动作;采集站条目页概括为「filling out web forms on their behalf」,本页不把该概括当作原帖事实。原帖也没有说明那封/那些内容是否发出、有多少回复、第一次看房的结果,以及那个页面为什么挡住它。

Business model

Reddit user u/Vontaxis posted 'I like Operator' in r/OpenAI. In two short sentences he says he used Operator for the last two days to apply to apartments and it worked quite well; it 'wrote to around 20-30 listings' and he had his first visitation that day. The original does not specify whether that means forms, messages or something else, so this page does not add that detail. He also notes one page that apparently blocked it and says he fears this will happen more in the future; the reason for the block is not given. There is no platform name, no form fields, no response rate, no outcome of the viewing, and no amounts, income or savings figures. A first visitation is a viewing opportunity, not an approved application, a signed lease or a completed move, and is not written as a result here. The collection site's summary says the agent filled out web forms on his behalf; the original text only says it wrote to listings, so that summary is not treated as an original-post fact. The workflow, prompt, synthetic sample and the 'human submits, stop when blocked, never bypass' rules are AgentFlow proposals, not the author's practice.

The useful part is not '20-30 listings' but keeping the unreliable outcomes visible. The author took the trouble to mention one page that blocked it. In bulk submissions the two real risks are a run that looks complete while a few rows failed silently, and handing identity documents to an automated flow. Making the status table the deliverable - and keeping submission and personal fields with the person - beats chasing a higher count. None of this is described in the original post; it is AgentFlow's proposed design.

Workflow

  1. List every listing link and its required fields first. (AgentFlow's prerequisite; the post gives only the 20-30 count.)
  2. Keep personal information and documents with the owner - the assistant only lists which fields are needed. (AgentFlow's boundary.)
  3. Prepare one draft and one status row per listing, so 'prepared' is never confused with 'submitted'.
  4. If a page blocks the run, mark that row 'blocked' and stop; never bypass login, CAPTCHA or anti-bot checks. (AgentFlow's compliance boundary; the post reports one blocked page.)
  5. Keep every submission, message and application fee with the owner. (AgentFlow's boundary; the post describes no confirmation step.)
  6. Record only what the post says: a first viewing, not an approved application or a signed lease.

Adaptation plan

The post does not name the listing platforms, describe the forms, say what 'wrote to' means, say whether anything was actually sent, give a response rate, describe the viewing outcome, explain the block, or state any cost. It gives no rent, application fee, subscription price, income or savings. '20-30' is a count of listings, not a success rate. No reproduction was attempted; the sample here is synthetic.

Prompt

AgentFlow draft · Untested.

You are my apartment-application preparation assistant. You may read the listing list I give you, work out which fields each listing needs, and prepare drafts. You do not fill in or hold personal information, submit applications, send messages or email, pay fees, or use stealth browsers, proxy rotation, CAPTCHA solving or any other bypass of site restrictions.

[INPUT]
- Listing list: [link / platform / note], one row each
- Field requirements per listing: [paste field names if visible, otherwise write 'owner to open and confirm']
- Types of information I will fill myself: [e.g. name, contact, income proof, move-in date]
- Forbidden actions: [e.g. no bypassing login or verification, no submitting on my behalf]
- Output format: [required table fields]

[STEPS]
1. Check the listing list and report how many rows there are, how many have visible field requirements, and which need me to open and confirm. If a link does not open, write 'owner to confirm' and do not guess the page.
2. For each listing output only the list of fields needed, marking which are personal information or documents that I fill myself. Include no real personal data.
3. Prepare one short draft per listing (greeting, ask about viewing times, note that documents can follow), labelled as a draft, not sent. Drafts contain no ID numbers, income figures or contact details.
4. Build a status table: listing / fields visible / draft ready / blocked / submitted (start as 'no' for all) / who does the next step.
5. If a login wall, CAPTCHA, anti-bot check or page block appears, mark that row 'blocked', state which step stopped, hand the link back to me and stop. Do not retry with a bypass, switch networks or solve the challenge.
6. List a 'needs my confirmation' item for every submission, message, document upload and application fee, and state what I need to do. End by stating that nothing was submitted, sent or paid.

[OUTPUT]
1) list check; 2) per-listing field lists; 3) unsent drafts; 4) status table; 5) blocked-row note; 6) confirmation list and no-send statement.

[NEEDS MY CONFIRMATION]
- All personal information and documents: I fill them myself; you do not handle them.
- Every submission, message and fee payment: I approve and do it myself.
- If page requirements differ from my list or extra documents are requested: ask me first, do not reroute.

[IF MATERIAL IS MISSING OR A STEP FAILS]
Link unreachable, fields not visible, page blocked, login or verification required, documents missing: state which listing and step is blocked and stop that row. Never guess page content, invent contact details or bypass restrictions. Prefer explicit 'blocked / to confirm' rows over a table that looks fully submitted. Record a first viewing only as an opportunity, never as an approved application or a signed lease.

Running costs and pitfalls

The post does not name the listing platforms, describe the forms, say what 'wrote to' means, say whether anything was actually sent, give a response rate, describe the viewing outcome, explain the block, or state any cost. It gives no rent, application fee, subscription price, income or savings. '20-30' is a count of listings, not a success rate. No reproduction was attempted; the sample here is synthetic. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

Original text and media remain attributed to their authors.