Agents In Use
What’s new todayLast update
1005 additions

Use Replit Agent to build a storage booking dashboard

Tobias Wupperfeld tested Replit Agent on an internal booking tool for a self-storage business.

OUR ADAPTATION

Suggested prompt

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

Build an internal tool for [storage units] and [bookings], with occupancy calendar and unit editing. Include authenticated access and role boundaries. Return a prototype and demonstrate booking operations for my review before customer use.

What happened

Wupperfeld reports a mostly working storage-booking prototype, with later review finding unprotected API endpoints and missing rate limiting.

Reported by Tobias Wupperfeld

How the agent did it

  1. Specify bookings, units and occupancy views.
  2. Build the database and API operations.
  3. Inspect layout and customer-data protection.

Where a person stepped in

Wupperfeld reviewed layout and ran a security review.

Tobias Wupperfeld tested Replit Agent on an internal booking tool for a self-storage business. The requested application had a dashboard, charts, a calendar showing occupancy and controls for adding, changing and deleting storage units. The agent's planning step identified that the tool needed a database and API endpoints.

Replit built the backend and connected the booking and unit operations. Wupperfeld reports a mostly functional dashboard after the initial run, with a misplaced chart legend and smaller layout problems. He selected the affected element and described the defect; he also used a drawing on the canvas to identify an area that needed changing.

The later review changed how the result should be interpreted. Wupperfeld cloned the project and asked Claude Code to inspect security. He reports missing authentication on API endpoints, exposed customer contact details and absent rate limiting. The account documents a working prototype and concrete repairs while showing that visible booking functionality did not establish protected customer access. He recommends treating this output as a draft requiring further review.

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

Source: www.madebyagents.com · Tobias Wupperfeld

Frequently asked questions

What did the calendar show?

Storage-unit occupancy data.

What UI defect appeared?

A chart legend was misplaced.

Why was the dashboard still a prototype?

A later Claude Code review found API endpoints without authentication, customer contact data without access control and no rate limiting.

More details

About this account

Replit planned and implemented the connected tool.

Firsthand account opened and read. Results are attributed to the author. Prompt is our suggested adaptation, not an original quotation.

Credit: Tobias Wupperfeld

Source published 15 Apr 2026

Source checked 14 Oct 2026

Tools and topics

Replit Agent · Database · API endpoints · Claude Code review

Storage bookings · Occupancy calendar · Access review

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