Agents In Use
What’s new todayLast update
3 use cases added today

Claude Code sessions build a Singapore haze map

A developer used parallel Claude Code sessions in separate Git worktrees to build a public haze map. Claude wrote the Python data pipeline, MapLibre map, particle model and CI. The developer defined the scope and checked screenshots as the agents worked through issues and pull requests.

OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Build a small map answering [environmental question] using [approved public dataset]. Begin with one layer and one date. Document units, missing data and known false positives. Work on a separate branch, capture before-and-after browser screenshots and ask me to inspect them. Keep predictions clearly labelled, explain retrospective versus live validation, and propose scheduled refreshes without deploying until approved.

Evidence at a glance

Sourced account
Source poster / publisher
u/teyou
Original account
Read the source ↗
Published
Source link checked
Reported result
A public haze-map page was accessible during source checking. The author reports twice-daily data refreshes and stale-data alerts. Their retrospective forecast check used realised winds, which they explicitly call a best case rather than proof of live forecasting performance.
Human involvement
The developer decided what to build and what claims the map could make, inspected screenshots and described data-cleaning rules. Forecast limitations and the map's geographic scope are explicit in their returned comments.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. The developer defined a small haze-map question and selected public fire, air-quality and wind datasets.
  2. Claude Code built the Python data pipeline, MapLibre interface, particle model and CI configuration.
  3. Parallel coding sessions used separate Git worktrees, branches and ports, with changes tracked through GitHub issues and pull requests.

Developer teyou used Claude Code to build a public map showing fires, smoke and wind relevant to Singapore's haze. Claude wrote the Python data pipeline, MapLibre interface, particle model and CI. The developer chose the scope and the claims the map was allowed to make.

Work ran across several Claude Code sessions, each with its own Git worktree, branch and ports. Changes began as GitHub issues and arrived as pull requests with before-and-after screenshots. A lead session reviewed and merged work. In returned comments, the developer explains that Playwright captured screenshots, only one browser ran at a time, and they personally inspected changes.

Data cleaning was a substantial part of the project. Satellite detections included factories, gas flares, volcanoes and reflections over water. The author reports removing 51,922 false detections. Their comments explain land checks and cross-satellite comparisons, rather than treating every hotspot as a fire.

The map's public page was accessible during source checking. The author reports twice-daily GitHub Actions refreshes, Cloudflare hosting and a Worker that warns about stale data. These scheduled jobs are not themselves AI reasoning.

Forecast claims need care. A retrospective check used realised winds, which the author calls a best case. It does not independently establish live forecast accuracy. The account is useful for developers combining parallel coding agents, screenshot review and messy public datasets without confusing an accessible visualisation with validated scientific predictions.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/teyou

Frequently asked questions

What did Claude Code actually build?

The author says Claude wrote the Python data pipeline, MapLibre map, particle model and CI. Multiple sessions worked in separate Git worktrees, with screenshots and a lead review session.

Does the source prove the map's live forecast accuracy?

No. The author describes a retrospective check using realised winds and explicitly calls it a best case. Prospective forecasts had only recently begun to be logged and scored.

Does the map cover every Southeast Asian burning season?

No. The author says the focus is haze reaching Singapore from Indonesia, Malaysia and Brunei. Their returned comment specifically excludes northern Thailand's burning season.

More details

Remaining steps

  1. Sessions produced before-and-after Playwright screenshots; the developer inspected changes and a lead session reviewed and merged work.
  2. The team added filters for false satellite fire detections and scheduled data updates with stale-data alerts.

About this account

Claude Code sessions implemented code and browser checks in separate worktrees. A lead session reviewed and merged changes. Scheduled refreshes and alerts are ordinary automation built by the agents, not evidence of AI making ongoing air-quality decisions.

Firsthand account by u/teyou: https://www.reddit.com/r/ClaudeAI/comments/1xbgkdf/singapores_air_hit_psi_230_this_week_i_built_a/. Public RSS post and returned comments captured on 23 October 2026; RSS coverage is partial. Body eligibility passed at 0.8. Outcomes and execution metrics are author-reported, not independently reproduced. Linked artifact checked over HTTP. Suggested prompt by Agents In Use, not the author's original prompt.

Credit: u/teyou on Reddit

Source published

Added to Agents In Use

Source checked

Tools and topics

Claude Code · Git worktrees · Python · MapLibre · Playwright · GitHub Actions · Cloudflare

parallel agents · data visualisation · environmental data · browser testing · data cleaning

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.