Zira logo
AI plugins
Support

ZIRA / AI PLUGINS

Your plant.
Your questions.
Your AI chat.

Bring Zira into Codex or Claude Code. Check cameras, understand production, build reports and take the next step, in your own words.

Install only what you use · Runs on your computer · Your Zira account

EARLY ACCESSZira + Zira Visionv0.3.51-preview.40
View release

Supplied directly by Zira. Separate from the official OpenAI and Claude directories.

01 / GET CONNECTED

One prompt.
Your assistant does the setup.

No terminal commands to type. Choose your app and your plugins, copy the prompt, and paste it into a local chat.

  1. 1
    Open the right chat

    Open Codex and start a Local task on this computer.

  2. 2
    Let your assistant prepare Zira

    It checks your computer, installs what’s missing and verifies the plugin. You handle any system approval or sign-in.

  3. 3
    Get your first useful answer

    Sign in to Zira in the browser when asked and say what you want help with. It all happens in the same chat.

Use Codex or Claude Code on your computer. This package does not run in ordinary ChatGPT or Claude web chats, Claude Chat/Cowork, or cloud tasks. Which app should I use?

Your app
Your plugins

Your assistant installs Zira and Node.js. No Python needed. You can add Zira Vision later with the update prompt.

Read the complete prompt
Install the public Zira plugin 0.3.51-preview.40 for Codex on this computer. I understand this is an early-access release supplied directly by Zira. I authorize installing Zira and the Node.js helper it needs. No Git installation. The release holds two plugins in one marketplace: zira and zira-vision. Install only zira; leave zira-vision uninstalled unless it is already installed, in which case keep and update it.

I am not technical. Do the setup for me and explain briefly what is happening. Preserve my existing Zira sign-in, preferences, reports and schedules, and avoid duplicate installations. Use the ZIP procedure below instead of the repository README's Git installation commands; consult its documentation for runtime setup and source switching.

Use the ZIP installation route; do not install or invoke Git. Download https://github.com/lightapp/zira-plugin/archive/refs/tags/v0.3.51-preview.40.zip over HTTPS. Extract safely to a staging directory, rejecting absolute paths, parent traversal and symlinks. Validate release.json and build.json: version 0.3.51-preview.40, public audience, preview channel, clean source, production-only profiles, no .pt support and no automatic refresh. Check every file hash listed in release.json before running packaged code.

Keep the extracted marketplace in a persistent, user-owned folder such as ~/.zira/plugins/public/preview/current (use the user's home directory on Windows too), outside Downloads, temporary folders and the host's plugin cache. Keep the whole public package intact, including hidden catalog directories. For an update, stage and verify the new ZIP first, preserve the previous source for rollback, then replace only this installer-managed source folder. Never delete credentials, reports, preferences, schedules or Python environments. Do not replace an installed newer version with this one; refresh the plugin page’s release information instead.

Inspect the selected host's marketplace/plugin list before registration. If zira already uses this local folder, reuse it. If it uses a different source, explain the source switch, preserve user data and use the native marketplace manager to switch to this folder; never edit host configuration files by hand. If that source is internal or managed by an organization, stop and ask before replacing it.

Register the extracted folder with codex plugin marketplace add "<persistent-source-folder>", then run codex plugin add zira@zira. Do not run codex plugin marketplace upgrade for this local source; that command requires Git.

Install a supported Node.js LTS (at least 20) if missing, from official sources or trusted system package managers. The local Node tools need no npm install. Zira itself does not need Python: do not install Python or analysis packages now. Only the optional trimsaw camera-view check uses Python, in its own separate environment; set it up later, and only if I ask for it (trimsaw-sizes.mjs scene-setup --confirm). Report any unsupported platform or failed dependency clearly; never call a partial setup complete.

Verify every installed Zira plugin is enabled and public, check its build identity against the selected public release, and check its tools can start. Keep operating-system and app protections, and stop for any approval the app or computer requires. Never ask for my password in chat. If I am in a web, cloud or unsupported chat, tell me exactly how to open a local session instead.

Finish onboarding in this same chat. Do not stop to ask me for a new chat or session, and do not hand me a prompt to paste later. A plugin's tools usually load only in a new session, so for this first run use the installed package directly: in the installed zira plugin folder read skills/getting-started/SKILL.md and references/local-mcp.md, and run the packaged helpers they name with Node from that folder (each tool in local-mcp.md maps to one script and the same options). Start the browser sign-in with the packaged sign-in helper and wait while I finish it, ask what I want to achieve, choose my site only if needed, and complete one useful read-only first task. If Node.js was just installed and is not found yet, call it by its full path instead of asking me to restart the app. Only if the computer itself must restart, say so once and tell me I can simply say "continue with Zira" afterwards. End with one line: Zira is ready in every new chat from now on.

Do not create tasks, change devices, publish reports or activate schedules as part of setup. After setup, remind me to return any temporary Full Access permission to my usual setting.

For smoother setup, use Full Access if available. It allows file and command access; switch back afterwards.

02 / THE PLUGINS

Start with a question.
See what you can do.

2 plugins from one marketplace, 29 skills in all. Install Zira, and add Zira Vision only if you work on models and datasets. Internal engineering and device-control tools are excluded.

Zira

For everyone

Ask about your sites, cameras and production. Build reports and dashboards, manage tasks and forms. 25 skills. Needs Node.js only.

05

Make Zira yours

Start with your priorities, learn what to ask and get help along the way.

2 skills included
“Help me get started with Zira.”

Zira Vision

For AI vision teams

Build and check the AI models behind your cameras: evaluate a model on your images, review rare defects and prepare training data. 4 skills. Adds Python for image and model analysis.

Actions depend on your Zira permissions and available data. Public model evaluation supports .tflite models. The Claude Code panels use manual refresh. Your assistant previews changes before applying them.

03 / KEEP IT READY

Update without
starting over.

In Claude Code, Zira updates itself. A new version installs in the background and is ready in your next session. In Codex, Zira tells you when a new version is available. Say “update Zira” and your assistant handles it. Your sign-in, preferences, reports and schedules stay in place.

What changed in this version
  • Company dashboards: build, change, copy, share and delete the dashboards on a company's Dashboards tab from chat, with charts across all of the company's sites.
  • Fast company totals: set up a Zira aggregator that rolls every machine up per site day, so a company dashboard loads in seconds.
  • Documentation clean-up: examples no longer name customers.

Use this prompt once if your Zira is older than 0.3.51-preview.34, or to update right now. No Git required; start a new local chat afterwards. To add Zira Vision to an existing Zira, tick it under “Your plugins” above and use this prompt.

A few things to know

Do I need a GitHub account or an API key?

No. The plugin downloads from Zira’s public repository. To access company data, sign in with your existing Zira account in the browser. Your Codex or Claude account is separate.

Where does my data go?

The tools run on your computer and contact Zira using your own account. Reports, downloaded datasets and analysis files can be saved locally. Information returned to the chat is handled by your chosen AI provider under its settings and terms. Reports are not published just by installing the plugin.

Will everything finish in one chat?

Yes. One prompt covers the install, your Zira sign-in and your first answer, all in the same chat. Along the way you may need to approve a download or a system prompt. After that, Zira is ready in every new chat.

What if I already have another Zira version?

Your assistant checks first. It should preserve your settings and ask before switching a pinned or internal installation. Keep one source of Zira enabled at a time. Read the version-switching guide.

Can my team install it on managed computers?

Yes, subject to your organization’s policies. Your IT team may need to approve the plugin source and helper programs. Start with the installation requirements. macOS has been tested; Windows end-to-end acceptance is still pending.