The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
Document managing and deleting lenses from the dashboard Lenses page
Claudeb68989bfd392
diff --git a/docs/cloud/lenses/adding-lenses.mdx b/docs/cloud/lenses/adding-lenses.mdxindex e24e44c0..096e093b 100644--- a/docs/cloud/lenses/adding-lenses.mdx+++ b/docs/cloud/lenses/adding-lenses.mdx@@ -44,7 +44,7 @@ Select **Add lens** on the lens's page. You need to be signed in.</Warning>Added lenses belong to your account, not to a session. To remove one, select **Remove lens** on the-same page.+same page, or **Remove** on the [Lenses](https://beacon.sh/dashboard/lenses) page in the dashboard.## Lenses on the session pagediff --git a/docs/cloud/lenses/lenses-mcp.mdx b/docs/cloud/lenses/lenses-mcp.mdxindex cab7786e..fe61b992 100644--- a/docs/cloud/lenses/lenses-mcp.mdx+++ b/docs/cloud/lenses/lenses-mcp.mdx@@ -3,8 +3,9 @@ title: "Lenses with MCP"description: "Let your coding agent create, upload, release and publish lenses"----[Beacon Cloud MCP](/deployment/managed-mcp) lets your coding agent do everything with a lens that-you can: create it, upload versions, release one, and choose who can find it.+[Beacon Cloud MCP](/deployment/managed-mcp) lets your coding agent create a lens, upload versions,+release one, and choose who can find it. Deleting a lens is only possible in the+[dashboard](/cloud/lenses/managing-lenses#delete-a-lens).## Before you startdiff --git a/docs/cloud/lenses/managing-lenses.mdx b/docs/cloud/lenses/managing-lenses.mdxindex 72382b1f..85a35650 100644--- a/docs/cloud/lenses/managing-lenses.mdx+++ b/docs/cloud/lenses/managing-lenses.mdx@@ -1,57 +1,75 @@---title: "Managing lenses"-description: "Upload new versions, change the current version, and choose who can find a lens"+description: "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, and decide-whether it is listed in the marketplace. You manage lenses through-[Beacon Cloud MCP](/cloud/lenses/lenses-mcp): ask your agent, and it calls the tools for you.+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.-Only the lens's owner can change it.+## Your lenses-## Change details+The **Lenses** page at [beacon.sh/dashboard/lenses](https://beacon.sh/dashboard/lenses), under+**Observe** in the dashboard sidebar, lists:-The title, description and icon can change at any time. Ask your agent, for example:+- **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.-```text-Rename my files-changed-plus lens to "Files Changed+" and update its description.-```+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-Every upload is a new, immutable version with its own semantic version number, such as `1.0.1`-or `1.1.0`. A version number can be used only once, so to change the HTML, upload another 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**.-Uploading a version does not change what anyone sees. It stays a draft until you release it.+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**.-## Release or roll back+## Change the current version-Releasing a version makes it the **current version**: the one the lens page, the marketplace and-everyone who added the lens see. Releasing takes effect immediately.+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, release an earlier version. Nothing is re-uploaded, and every version stays-available to release again.+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 || --- | --- |-| **Private** | Only you. New lenses are private unless you choose otherwise. |-| **Public** | Everyone. The lens is listed in the marketplace once it has a released version. |+| **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 visibility by asking your agent, for example "Make my token-heatmap lens public."+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 fromthe sessions of everyone else who added it. You keep it.-## Your lenses+## Delete a lens-Ask your agent to list your lenses. It shows every lens you own, public or private, with its-current version. You can also list the lenses you added, or browse the marketplace, the same way.+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.-Lenses cannot be deleted yet. To retire one, make it private.+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+Upload ./lens.html as version 1.1.0 of my failed-commands lens and make it current.+```## Relateddiff --git a/docs/deployment/managed.mdx b/docs/deployment/managed.mdxindex b5d1ce7a..b2353a30 100644--- a/docs/deployment/managed.mdx+++ b/docs/deployment/managed.mdx@@ -16,7 +16,7 @@ so there is no database, bucket or pipeline to run.repository and risk. Open a session to read its prompts, commands, tool calls and file edits.- **Lenses.** Focused views of a session, such as files changed, token spend or securityfindings. Use the built-in lenses, add more from the [marketplace](/cloud/lenses/adding-lenses),- or [build your own](/cloud/lenses/creating-lenses).+ [build your own](/cloud/lenses/creating-lenses), and manage them on the dashboard's **Lenses** page.- **MCP.** Let the agent you are working in search and read your past sessions, and publish lensesfor you. See [Beacon Cloud MCP](/deployment/managed-mcp).- **Analytics.** Token usage and cost by model, agent activity over time, and the harnesses,