> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beacon.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing lenses

> Edit a lens, upload new versions, change the current version, choose who can find it, and delete it

After you create a lens, you can change its details, upload new versions, roll back, decide whether
it is listed in the marketplace, and delete it. Only the lens's owner can change it.

## Your lenses

The **Lenses** page at [beacon.sh/dashboard/lenses](https://beacon.sh/dashboard/lenses), under
**Observe** in the dashboard sidebar, lists:

* **Your lenses:** every lens you created, public or private, with its current version and how
  many people added it. Select **Manage** to open a lens's settings.
* **Added from the marketplace:** lenses by other authors that run on your sessions. Select
  **Remove** to stop one reading your sessions.

You can also open a lens's settings with **Manage** on its page at `/lenses/<key>`, or with
**Manage lenses** at the bottom of a session's **+** menu.

## Edit details

On the lens's settings page, change the title, icon and description under **Details**, then select
**Save details**. They appear on the marketplace card, the lens page and the session lens menu.

The key is permanent. To use a different key, create a new lens.

## Upload a new version

Under **Versions**, choose the new HTML file. Beacon fills in the next patch version, such as
`1.0.3`; change it if you want `1.1.0` or `2.0.0`. Select **Upload version**.

Every version is immutable, and a version number can be used only once. Uploading does not change
what anyone sees unless you tick **Make it the current version now**.

## Change the current version

The current version is the one the lens page, the marketplace and everyone who added the lens see.
To publish a version, select **Make current** next to it. It takes effect immediately.

To roll back, make an earlier version current. Nothing is re-uploaded, and every version stays in
the list.

## Who can see a lens

| Visibility | Who can see and add it |
| - | - |
| **Just me** | Only you. New lenses are private unless you choose otherwise. |
| **Everyone** | Everyone. The lens is listed in the marketplace once it has a current version. |

Change it under **Who can find and add this lens?** and save.

Making a public lens private removes it from the marketplace straight away, and it disappears from
the sessions of everyone else who added it. You keep it.

## Delete a lens

At the bottom of the settings page, type the lens's key and select **Delete lens**. This deletes
every version and removes the lens from everyone who added it. It cannot be undone.

The key of a deleted lens is retired: no one, including you, can create a lens with it again. That
way an old link to the lens can never open a different lens published under the same key.

## Manage lenses with your agent

Everything on this page except deleting can also be done by your coding agent through
[Beacon Cloud MCP](/cloud/lenses/lenses-mcp). Ask it, for example:

```text theme={null}
Upload ./lens.html as version 1.1.0 of my failed-commands lens and make it current.
```

## Related

> **[Lenses with MCP](/cloud/lenses/lenses-mcp)**
>
> The tools and the publishing flow your agent uses.

> **[Creating lenses](/cloud/lenses/creating-lenses)**
>
> File rules and the session data a lens receives.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.