VediramPlugin is not available
Preview. Plugins are a preview feature.
What you see
- In the Levee app, Settings > Plugins lists a plugin, but its status is not ready.
- The status is downloading, needs setup, needs Levee update, unavailable or revoked.
- A plugin shows ready, but the agent in your project does not seem to have it.
- Saving a plugin's values fails.
Why it happens
A plugin gives the AI agent an extra tool, for example a connection to a business application. Your organization chooses the plugins in its cloud policy. Levee then downloads each one to your computer, checks it, and offers it to your projects only when everything it needs is in place: its files, the software it runs on, and its settings.
Some settings come from your organization. Others, such as your own account name or key for a service, only you can provide.
What you can try
Open the Levee app and go to Settings > Plugins. Find the plugin and read its status.
downloading
The plugin, or the software it runs on, is still downloading. The page says "Values can be set once the plugin has downloaded."
- Wait a few minutes, and keep the computer connected to your network.
- If it stays at downloading for more than an hour, tell your IT team.
needs setup
The plugin is missing a required setting.
- If the plugin shows fields to fill in, enter your values and click Save. Fields marked required must be filled. A field may expect a certain form, for example a web address: if you see a message such as "... must match ..." or "... must be a number", correct the value.
- If the page says "Your organization has not finished setting up this plugin.", the missing setting belongs to your organization. Tell your IT team.
Saved values are never shown again. A field already saved shows set. Use Replace to change it or Clear to remove it.
needs Levee update
The page says "Update Levee to use this plugin." The plugin needs a newer version of Levee. Ask your IT team to update Levee.
unavailable
The page says "This plugin is unavailable right now." Levee could not get the plugin ready, for example because your organization's settings for it are not answering, or the download did not check out. Levee keeps trying on its own. If it stays unavailable, tell your IT team.
revoked
The page says "This plugin was removed by your organization." It is no longer offered to your projects. Ask your IT team if you still need it.
The plugin is ready, but the agent doesn't have it
- Check which AI tool the project uses. Plugins work with Claude Code only: Codex CLI does not load them, so a Codex agent never gets plugin tools.
- Stop the project and start it again. The agent is given the list of plugins when the project starts.
- Ask the agent which tools it has.
- If the plugin is still missing, tell your IT team. Plugins only run in projects when your organization has turned them on.
"user values for this plugin belong to another user"
On one computer, a plugin's personal values belong to the first person who saved them. Another user cannot change them. Ask that person to clear all their values for the plugin, or ask your IT team to change them.
For your IT team
How plugins reach a machine
The cloud policy's spec.plugins list is synced to the machine. For each plugin, the Levee service downloads the bundle and its tenant secrets from Vediram Cloud with the machine's identity, verifies size and SHA-256, and reads the plugin's settings from the bundle's own manifest. If the plugin needs a runtime (node or python), Levee downloads it on first use from the Levee-Tools catalog (runtimeProvisioning.mcpRuntimeCatalogUrl, by default on downloads.vediram.com) and verifies it.
Sync runs at service start, after every new plugin list, every 1 to 30 minutes (backing off) while a plugin is downloading or unavailable, and every 30 minutes otherwise. During an upgrade, the previous ready version stays in use until the new one is ready. A removal or a yanked version applies at once.
Plugins run in a project only when proxies.mcp.enabled is the JSON literal true in policy. See Plugins policy. For the user's side, see Plugins.
Status reference
| Status | Cause | Fix |
|---|---|---|
| downloading | The bundle is downloading, or its node or python runtime is not installed yet. | Allow HTTPS to Vediram Cloud and to downloads.vediram.com from the machine (the service runs as Local System). |
| needs setup | A required setting with no default has no value. The service log names the missing keys. | User-scoped keys: the user fills them in. Tenant keys (tenantConfig): set them in the cloud policy; the next sync brings them to the host. |
| needs Levee update | The plugin's kind is unknown to this Levee, or it needs a newer Levee. | Update Levee. |
| unavailable | Tenant secrets answered 404 (the cloud no longer resolves the plugin for this tenant), the cached bundle does not match its SHA-256, the manifest is missing or invalid, or the version is yanked. | Check the plugin's entry and tenant settings in the cloud policy. A plugin whose tenant secrets answer 404 stays unavailable, across restarts, until they answer again. |
| revoked | The plugin is no longer in the cloud policy, or the policy's plugin list is empty. | Expected. Add it back to the policy if needed. |
Logs
levee log tail --component service --since 2h
levee log tail --component proxy.mcp --project <project-id> --since 1h
Service log lines name the plugin and the reason, for example "MCP plugin ... needs setup: ..." or "MCP plugin ... is unavailable". The service log never contains setting values.
If the Startup Doctor shows "Some Levee features are unavailable" with McpPlugins, the plugin list from cloud policy could not be written to disk. Levee retries at every sync. Revocations still apply in memory. See Startup Doctor checks.
If the service log says "Could not grant the MCP servers of project ... their files; none will run", the project started with no plugins at all. Stop and start the project. If it repeats, collect logs.
Personal values
User values are sealed per plugin on the machine and bound to the first user who stores them. Another standard user gets "user values for this plugin belong to another user". An administrator running the Levee app elevated can overwrite them. Clearing every value releases the ownership.
Plugins installed by an administrator
Plugins an administrator imports directly on the machine are not listed on the Plugins page. If one has the same ID as a cloud plugin, the locally imported one is used.
Before you open a request
Send the service and proxy.mcp logs and the plugin's status. See Collecting logs for support.