-
Notifications
You must be signed in to change notification settings - Fork 143
demo: replace social feed with spreadsheet app, update overlay and docs #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,9 @@ | ||
| { | ||
| "mcpServers": { | ||
| "expect": { | ||
| "command": "npx", | ||
| "command": "node", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. P1: The MCP server command uses a hardcoded absolute local path, which makes this config non-portable and likely broken for every other environment. Prompt for AI agents |
||
| "args": [ | ||
| "-y", | ||
| "expect-cli@latest", | ||
| "/Users/aidenybai/Developer/expect/apps/cli/dist/index.js", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hardcoded local filesystem path in MCP configHigh Severity The Reviewed by Cursor Bugbot for commit f8b5480. Configure here. |
||
| "mcp" | ||
| ] | ||
| } | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,22 @@ | ||
| import { useState } from "react"; | ||
| import { BrowserRouter, Routes, Route } from "react-router-dom"; | ||
| import { ErrorBoundary } from "./error-boundary"; | ||
| import { LoginPage } from "./pages/login"; | ||
| import { Layout } from "./components/layout"; | ||
| import { DashboardPage } from "./pages/dashboard"; | ||
|
|
||
| export const App = () => { | ||
| const [, setTick] = useState(0); | ||
| const forceUpdate = () => setTick((previous) => previous + 1); | ||
|
|
||
| return ( | ||
| <ErrorBoundary> | ||
| <LoginPage /> | ||
| <BrowserRouter> | ||
| <Routes> | ||
| <Route element={<Layout />}> | ||
| <Route path="/" element={<DashboardPage onUpdate={forceUpdate} />} /> | ||
| </Route> | ||
| </Routes> | ||
| </BrowserRouter> | ||
| </ErrorBoundary> | ||
| ); | ||
| }; |
This file was deleted.
This file was deleted.


Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: The new session-persistence guidance conflicts with the existing "unlock when done" rule by telling users not to unlock across turns. Keep tabs open across turns, but release
browser_lockat turn end and reacquire next turn.Prompt for AI agents