Urgent.News

What's breaking now, across thousands of outlets.

More in Tech

Six hosted sandboxes say "isolated." None tells you which wall your agent ran behind

A Show HN went up yesterday for plimsoll , a Go daemon you run yourself that executes code an agent wrote. The sandbox part is ordinary.

  • Six hosted sandbox services unable to identify specific isolation wall for execution runs
  • Plimsoll Go daemon reveals isolation tier but not specific wall reached
  • Unique request ID enables tracking and verification of executed runs

Thinking about the conditions for closing a customer inquiry in code: Sending and completion are different

고객 문의를 시스템에서 ‘완료’로 옮기는 시점은 단순히 답장을 보냈을 때가 아닙니다. 요청을 실제로 처리했더라도 고객에게 확인 대상과 재문의 경로를 알리지 않았다면, 상태는 닫혔지만 대화는 닫히지 않은 셈입니다. 이 글은 작은 팀에서 문의 상태를 설계할 때 쓸 수 있는 종료 조건 을 정리합니다. 특정 제품 구현이 아니라 운영 규칙의 예시입니다.

  • Closing a customer inquiry requires more than just sending an email.
  • Completion state occurs when agreed standards are satisfied and recorded.
  • Customer confirmation is necessary before marking an inquiry as completed.

The Red Pencil Workshop

The workshop opens on a staged failure, because a visible row count teaches faster than a definition. On the projector, a fake ledger shows three captures for one invoice after a short reply suggested…

  • Red Pencil Workshop uses staged failure to teach concepts
  • Workshop employs red pencil as script exit line
  • Focus on stopping at one process to deepen understanding

robots.txt Is a Contract: Parsing It Without Lying to Yourself

You fetched /robots.txt , got a 200, grepped for Disallow , found nothing scary, and started crawling. That is not reading the contract — that is skimming the cover page.

  • Robots.txt is a contract requiring careful parsing to avoid self-deception.
  • Crawl-delay, user-agent scoping, and contract focus on front door are often overlooked.

More from Tuesday 13 October →