Zira logo
AI plugins
What's New
October 8, 2026
Version 2026.10.08
6 min read

Zira Plugin: Device Status, Reports and Duplicates (Beta), plus QA Annotation in Vision Hub

The Zira plugin for Claude and Codex now checks the battery, temperature, camera and connection of every camera, sets up weekly reports in a few questions, copies dashboards and data sources to another site, starts from what matters to you and finds more rare defects. In Vision Hub, you can fix a QA frame's boxes where it is and cut its marked nails straight into a nails dataset.

AI Assistance
Device Health
Reports
AI Vision
Dashboards
Datasets
Integrations

The Zira plugin for Claude and Codex learned a lot this week. It can now keep an eye on every camera, set up your weekly reports for you, copy dashboards and data sources between sites, and help you build better Vision models from your own production images. And in Vision Hub, reviewing pallet QA images and turning nails into training data takes fewer steps.

Beta. The Zira plugin is in beta; the Vision Hub changes are available to everyone. To try it with your team, request access at sales@zira.us.

Device status for every camera

"Are my cameras OK?" or "Which cameras have a low battery?"

Zira checks every camera at your sites and shows its status on one page:

  • Online or offline, with how long a camera has been quiet. Cameras that stopped recently come first.
  • Battery and charging, with a warning when a battery is low and not charging.
  • Temperature, power and device errors.
  • Camera on or off, and camera moved, so you know when a camera needs to be pointed again.
  • Wi-Fi, cellular and network cable.

You do not need to set up production counts or targets first. Ask "Check device status every weekday at 6:30" and Zira checks each morning, telling you only when a camera goes offline, comes back, or reports something new.

The Device Status panel in Claude

Type /zira:device-status-panel and a panel opens beside the chat with one row per camera: its status, when it was last seen, battery, temperature and network, with anything worth a look in the notes. After that, a short line above the chat box keeps the count in view while you work, and a notice appears when a camera goes offline or comes back. The panel uses the same checks as the device status page and refreshes when you click Refresh. Turn on automatic refresh in the plugin settings to have it check every 10 minutes.

Device status for a pallet plant: one camera that went quiet first, then cameras to check, such as a moved camera, a low battery and a camera that is off.

Weekly reports in a few questions

"Send me a weekly report for my saws."

Pick the machines, and Zira recognizes each one: trimsaws, bandsaws, Pallet QA cameras and forms each get a ready-made report with the numbers that matter for them. Choose a day, a week or a month, and every report compares it with the one before:

  • Output, yield, fail rate and running time, each marked better or worse.
  • Days worth a look, such as a high fail rate, or long stops with no reason entered.
  • Machines that went quiet, and since when.
  • Charts you can explore, with CSV and Open in Sheets.

Zira runs it on the schedule you choose. In Claude, it can also keep a private page updated with the latest report, so you open the same link every week.

Every report, dashboard and review page now ends with a link to its saved copy, which opens any time later, even after the chat is closed. Ask "Open last week's Trimsaw report" and Zira finds it instead of building it again. Health and status dashboards are titled with your company and site names.

A weekly report for four saws: each number compared with the week before, the status of each machine, and units per day.

Copy dashboards and data sources

"Copy the Band Saw 1 dashboard to South Charleston."

Setting up a second plant no longer means starting from scratch:

  • Dashboards. Zira copies a dashboard in the same site, or to another site. For another site, it finds that site's matching machines and numbers and shows you the plan before copying. You confirm or change it, and Zira tells you which charts may show no data. AI reports are not copied, so Zira offers to set one up for the new dashboard.
  • Data sources. "Copy Cam 1 Quality as Cam 2 Quality." Zira copies a machine, camera or form in the same site or to another one, and tells you first what is not copied, such as readings, or a camera's settings, models and datasets. A copied camera is then ready to set up.

Nothing is copied until you say yes, and you get a link to the copy.

A start that fits you

"Help me get started with Zira."

Getting started now begins with what you want help with, such as understanding production, improving quality or keeping cameras working. Zira suggests the most useful first step for that, runs it with you, and shows you how to ask again.

Zira can also remember your priorities and your usual company and site, in Claude and in Codex, so later suggestions fit your work. Say "Show my Zira preferences", "Change my priorities" or "Forget my Zira preferences" at any time.

Health checks that stay quiet

"Check my Ohio sites' devices every morning."

Set up a daily health check for one site or all of them in a few questions. Each run updates the health dashboard. When nothing changed, Zira tells you so in one line.

Find more rare defects

"Find more raised nails for Cam 1 Quality."

Rare defects are hard to train for because there are so few examples. Zira searches your camera's recent production images for likely examples and opens a review page. You accept or reject each one, and Zira turns the accepted images into a dataset, ready for you to add to the camera in Zira. You can also check an existing dataset for labels that look wrong. This works with Pallet Vision cameras.

Test models on fresh production images

"How does the newest model do on yesterday's production?"

Score a Vision model on recent images from a Pallet Vision camera's production line, images it has never trained on, cut up the same way Zira prepares its training datasets.

See an AI report before you schedule it
  • A sample first. Before a scheduled AI report is saved, Zira writes a sample in the chat, so you see what your team will receive.
  • Fine-tune it in Zira. Open the draft in Zira's agent editor, change it there or in the chat, and schedule it when it reads right.
  • End-of-day reports. Ask for "every day at 18:00 with today's data", and the report covers the day that is ending, not yesterday.
  • Focused on its own period. Each report compares within its period or against your targets, and says plainly when a comparison you asked for is not possible.
Vision Hub: annotate QA frames in place and cut nail crops

Teaching a nails model from your own production used to mean moving full QA frames into a dataset just to fix their boxes. Now it happens on Image Review:

  • Annotate where the frame is. Annotate opens the QA frame in the annotator, in one window you keep beside the review page. Your boxes are saved next to the camera's, never over them, and a Corrected chip switches between your boxes and the model's. The annotator lists the session's marked frames and outlines their marked crossings, so you can zoom to each one with a click.
  • Nail crops only. Move marked images can now cut just the marked crossings into a nails dataset, using your corrected boxes, while the full frames stay in the session.
  • The right crop size. Nail crops can be cut at 320, 512 or 640 px, in Generate datasets and when copying slices. Show intersections labels every crossing with its size in pixels, so you can see which size fits a camera.
  • Full-resolution snapshots. Copy and merge now offer 4000 and 4800 px, the size newer Pallet Vision cameras capture.
  • Snapshots arrive faster. The QA Snapshots widget shows each new pallet about a second after it is uploaded.
Getting started

Request beta access to the Zira plugin at sales@zira.us, then read Zira in Claude and Codex. For the Vision Hub changes, see Image Review.