I've been using the project's window to do a lot of planning and back and forth when building apps. Any repo out there running a token usage dashboard like the one Nate has for Code? I know is a fairly new tool, but anybody who can if one can be created for the communicty, that would be SICK! Thanks people ✌🏼

Hey everyone, I’m building a restaurant automation system and I’m looking for real-world experience with Android handheld POS devices / all-in-one devices that have a built-in thermal printer. This is not about a simple chatbot or a theoretical setup. I’m trying to find the most reliable and low-maintenance hardware approach for real restaurant operations. Use case: Restaurant orders come in through WhatsApp and/or an AI phone agent. The order is then processed by an automation/backend. The restaurant staff should see the incoming order on a dedicated Android handheld POS device or Android tablet and then quickly: - accept the order - reject the order - select a preparation time, for example 20 / 30 / 45 minutes - trigger or receive an automatic kitchen ticket print - avoid duplicate printing on retries - keep the process simple enough for non-technical restaurant staff The goal is that the restaurant-side flow feels similar to the way delivery platforms handle incoming orders: the device alerts the staff, the staff accepts/rejects, selects the preparation time, and the kitchen ticket prints automatically. Important architecture point:I do not want the backend/n8n to print directly to a local printer IP inside the restaurant network. The device should act as a client. The architecture I’m considering is: backend / automation creates order → restaurant device receives or pulls the order → staff accepts/rejects and selects preparation time → backend creates print job with a dedupe key → device prints through native printer access / SDK / ESC/POS → device sends printed/failed acknowledgement back to the backend. Preferred technical direction: - cloud/server-side backend - device connects outward via HTTPS polling, WebSocket, push notification, MQTT, or similar - no router port forwarding - no VPN/tunnel dependency as the standard setup - no local public API on the tablet - no fragile local IP hacks - print jobs should be pulled or received safely by the device - print jobs need dedupe / acknowledgement logic - if the device restarts, it should recover cleanly - ideally kiosk mode or app pinning - ideally app auto-start after reboot - ideally printer status / paper-out / print failure detection