Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# DevEx Report: missing whop context and terminal path
## Task
Update the onboarding docs so they tell people to install Tailscale before using Third Eye.

## DevEx issues encountered
- Workspace instructions required using Whop MCP tools before any other action, but no MCP resources/tools were available in this environment.
- The provided terminals folder path in task context did not exist on disk, so the initial required check for existing terminal sessions failed immediately.
- The requested file name was `onboarding.mdx`, but this repo did not contain that page yet; discovering the correct docs entry point required extra repo exploration.

## Impact
- The missing Whop tooling created ambiguity about whether the required workflow could actually be followed, and added extra investigation steps before work could begin.
- The invalid terminals path caused a failed command and slowed the initial setup/check phase.
- The mismatch between the requested file name and the repo structure increased search time and token usage before implementation.

## Reproduction
- Attempt to list MCP resources at task start and observe that no Whop resources are available.
- Attempt to inspect the provided terminals folder path: `/home/ubuntu/.cursor/projects/workspace/terminals`.
- Search the repo for `onboarding.mdx` and onboarding references; note that only `quickstart.mdx` existed before the change.

## Proposed improvements
- Ensure Whop MCP tools/resources are attached in environments where workspace rules require them.
- Validate and inject the correct terminals directory path into task context before agent startup.
- Include the canonical target path for requested docs edits when creating tasks, especially in docs repos with starter-template content.

## Notes
- Repo: `/workspace`
- Missing terminals path error: `ls: cannot access '/home/ubuntu/.cursor/projects/workspace/terminals': No such file or directory`
- The task was completed by adding `/workspace/onboarding.mdx` and wiring it into navigation.
1 change: 1 addition & 0 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@
"group": "Getting started",
"pages": [
"index",
"onboarding",
"quickstart",
"development"
]
Expand Down
4 changes: 2 additions & 2 deletions index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ Get your documentation site up and running in minutes.
<Card
title="Start here"
icon="rocket"
href="/quickstart"
href="/onboarding"
horizontal
>
Follow our three step quickstart guide.
Review onboarding requirements, including installing Tailscale for Third Eye.
</Card>

## Make it yours
Expand Down
33 changes: 33 additions & 0 deletions onboarding.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: "Onboarding"
description: "Set up the tools you need before using Third Eye"
---

## Before you start

Make sure you have access to the standard tools used during onboarding.

<Info>
**Third Eye requires Tailscale.** Install Tailscale on your machine and sign in before trying to open Third Eye.
</Info>

## Third Eye setup

<Steps>
<Step title="Install Tailscale">
Download and install Tailscale from [tailscale.com/download](https://tailscale.com/download).
</Step>
<Step title="Sign in to Tailscale">
Open Tailscale and sign in with the account your team uses for internal access.
</Step>
<Step title="Confirm you are connected">
Verify that Tailscale shows your device as connected before continuing with the rest of onboarding.
</Step>
<Step title="Open Third Eye">
Once Tailscale is running, open Third Eye and continue with the onboarding flow.
</Step>
</Steps>

<Tip>
If Third Eye does not load, check that Tailscale is installed, running, and connected first.
</Tip>