Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Point printed dashboard links at a page that exists

shukieshah40a091848bfa
diff --git a/cli/beacon/cmd/endpoint_connect.go b/cli/beacon/cmd/endpoint_connect.go
index c212fe6f..f5e0b87c 100644
--- a/cli/beacon/cmd/endpoint_connect.go
+++ b/cli/beacon/cmd/endpoint_connect.go
@@ -164,7 +164,7 @@ func connectEndpoint(cmd *cobra.Command, userMode bool, logPath string) error {
// connection point, so the dashboard stays empty until an agent actually runs.
fmt.Fprintln(out)
fmt.Fprintln(out, "Next: run any supported agent as you normally would.")
- fmt.Fprintf(out, "Its sessions appear at %s within a minute of the activity.\n", result.Enrollment.DashboardURL)
+ fmt.Fprintf(out, "Its sessions appear at %s within a minute of the activity.\n", dashboardHomeURL(result.Enrollment.DashboardURL))
return nil
}
@@ -222,7 +222,7 @@ func runEndpointDisconnect(cmd *cobra.Command, args []string) error {
fmt.Fprintf(out, "Local enrollment record and device key removed from %s.\n", asymptote.Dir(userMode))
}
if loadErr == nil && enrollment != nil {
- fmt.Fprintf(out, "The device %s is still registered server-side; revoke it from %s/dashboard/endpoints.\n", enrollment.DeviceID, enrollment.DashboardURL)
+ fmt.Fprintf(out, "The device %s is still registered server-side; revoke it from %s.\n", enrollment.DeviceID, dashboardHomeURL(enrollment.DashboardURL))
} else {
fmt.Fprintln(out, "Revoke the device from the dashboard's Beacon Endpoints page if it is still registered.")
}
@@ -265,6 +265,24 @@ func connectBrowserOpener(userMode bool) func(string) error {
}
// managedIngestStatusLine renders the human status line for `beacon endpoint status`.
+// dashboardHomeURL turns the recorded service URL into the page a person can
+// actually open.
+//
+// The recorded value is the service root, which serves the marketing site, and the
+// dashboard is a single page at /dashboard with its views as tabs. Deep links like
+// /dashboard/telemetry have no route behind them, so anything printed here has to
+// stop at the dashboard itself.
+func dashboardHomeURL(base string) string {
+ base = strings.TrimRight(strings.TrimSpace(base), "/")
+ if base == "" {
+ return auth.DefaultDashboardURL + "/dashboard"
+ }
+ if strings.HasSuffix(base, "/dashboard") {
+ return base
+ }
+ return base + "/dashboard"
+}
+
func managedIngestStatusLine(status asymptote.ManagedIngestStatus) string {
if !status.Enabled {
if status.Message != "" {
diff --git a/cli/beacon/cmd/endpoint_connect_test.go b/cli/beacon/cmd/endpoint_connect_test.go
index 10bab013..64ccb4c7 100644
--- a/cli/beacon/cmd/endpoint_connect_test.go
+++ b/cli/beacon/cmd/endpoint_connect_test.go
@@ -132,7 +132,8 @@ func TestConnectUsesSignedInAccountAndSelectedPrivacy(t *testing.T) {
text := out.String()
for _, want := range []string{
"Next: run any supported agent",
- "sessions appear at https://beacon.sh",
+ // The recorded service URL is the marketing root; the app is at /dashboard.
+ "sessions appear at https://beacon.sh/dashboard",
"within a minute",
} {
if !strings.Contains(text, want) {
@@ -147,6 +148,24 @@ func TestConnectUsesSignedInAccountAndSelectedPrivacy(t *testing.T) {
}
}
+// Every URL Beacon prints has to be one a browser can actually open. The dashboard
+// is a single page at /dashboard whose views are tabs, so the service root is the
+// marketing site and deep links like /dashboard/telemetry have no route at all.
+func TestDashboardHomeURL(t *testing.T) {
+ for base, want := range map[string]string{
+ "https://beacon.sh": "https://beacon.sh/dashboard",
+ "https://beacon.sh/": "https://beacon.sh/dashboard",
+ " https://beacon.sh ": "https://beacon.sh/dashboard",
+ "https://beacon.sh/dashboard": "https://beacon.sh/dashboard",
+ "http://127.0.0.1:8971": "http://127.0.0.1:8971/dashboard",
+ "": "https://beacon.sh/dashboard",
+ } {
+ if got := dashboardHomeURL(base); got != want {
+ t.Fatalf("dashboardHomeURL(%q) = %q, want %q", base, got, want)
+ }
+ }
+}
+
func TestConnectRequiresSignedInAccountInUserMode(t *testing.T) {
originalLoad, originalConnect := connectAccountLoad, connectManagedEndpoint
t.Cleanup(func() {
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdx
index bbb53161..dfcc91e0 100644
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@ -13,6 +13,12 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
### Unreleased
+- **Printed dashboard links point somewhere that exists** · The dashboard is a
+ single page at `/dashboard` whose views are tabs, so the service root serves the
+ marketing site and deep links such as `/dashboard/telemetry` and
+ `/dashboard/endpoints` have no route behind them. Connect and disconnect printed
+ those paths, and the cloud-agents guide named them in prose; all of them now point
+ at the dashboard itself.
- **Setup ends on what to do next** · A managed install used to close on a wall of
paths and a sentence pairing the dashboard with a revocation link. It now ends by
saying to run an agent as usual and that its sessions appear on the dashboard
diff --git a/docs/runtimes/claude-code-cloud-agents.mdx b/docs/runtimes/claude-code-cloud-agents.mdx
index 7b32e2e4..8fb4d76c 100644
--- a/docs/runtimes/claude-code-cloud-agents.mdx
+++ b/docs/runtimes/claude-code-cloud-agents.mdx
@@ -102,8 +102,8 @@ Choose Beacon Managed, GCS, or S3 for the cloud-agent session logs.
A cloud sandbox has no browser and no Vector, so it cannot run
[`beacon endpoint connect`](/cli/endpoint-connect). Instead it authenticates with
a device key that a Beacon operator mints for the environment itself: one
-key per cloud environment, bound to your organization, listed on
-`/dashboard/endpoints` like any laptop and revocable from there. Ask your
+key per cloud environment, bound to your organization, listed under **Devices**
+on the dashboard like any laptop and revocable from there. Ask your
Beacon contact for a key, naming the environment (for example
"Claude Code web, acme/frontend"). You receive three values to put in the
environment in step 2: `BEACON_CLOUD_UPLOAD=asymptote`, the ingest URL, and the
@@ -295,9 +295,9 @@ Read the README, run pwd && ls, create a tiny temporary markdown note under /tmp
## 5. Verify upload
-For Beacon Managed, open `/dashboard/endpoints`: the cloud environment's
-device shows a fresh **last seen** time as soon as the first batch is accepted,
-and the session appears on `/dashboard/telemetry` within a couple of minutes,
+For Beacon Managed, open the dashboard: under **Devices** the cloud
+environment shows a fresh **last seen** time as soon as the first batch is
+accepted, and the session appears under **Sessions** within a couple of minutes,
with `run.provider=claude_code_web` and the Claude session id as the run id.
To check the key itself from your workstation:
@@ -357,8 +357,8 @@ run.run_id=cse_...
The Beacon Managed flow puts a per-device key in the Claude Code environment.
It can only append telemetry to your organization's ingest stream; it reads
-nothing and grants no dashboard access, and revoking the device on
-`/dashboard/endpoints` stops it within a minute. This is the one place a Beacon
+nothing and grants no dashboard access, and revoking the device under
+**Devices** stops it within a minute. This is the one place a Beacon
device key lives in an environment variable: a sandbox has no keychain and no
secrets file to hold it, unlike a laptop, where the key stays in a `0600` file.