← Back to setup
Let your agent set it up.
Preview only. This fictional project cannot connect to TaskUp.
Your setup prompt is ready.
It includes a sample key, your app’s URL, and only the extras you chose.
Copies all SDK features. Products remain optional; your agent will use existing authentication and controls where available.
Preview the prompt
TaskUp setup prompt
Set up TaskUp in my existing web app. Inspect the framework, browser entry point, routing, authentication and existing controls first. Preserve its working behavior.
Project: Sample Store
Production URL: https://your-app.example
Public TaskUp project key: YOUR_PUBLIC_PROJECT_KEY
TaskUp endpoint: https://task-up.org
Suggested framework/router: Next.js App Router. Confirm against the repository and adapt to its installed version.
Install the published npm package @taskup/web@0.2.8. Add one browser integration that reports the SDK connection and uncaught browser errors. Read https://task-up.org/agent-setup for API and privacy guidance. These are my selected extras:
- Enable usage: true. Track the initial page view and completed pathname changes once. This provides visits, page views and estimated daily active browsers. The SDK records URL paths; query and hash changes are not distinct pages. Do not claim separate page counts for hash-only routes.
- Use taskup.fetch(input, init) at the app request call sites selected for monitoring. This preserves fetch behavior and reports HTTP/network failures without reading request or response bodies. If the app uses another HTTP client, call reportNetworkFailure(path, status) on its failures, including status 0 when no response arrives. Use only a safe path; omit queries, bodies, credentials and tokens. Do not patch global fetch, wrap TaskUp's own requests or report one failure twice.
Starting browser integration (adapt it to this app; replace the user ID placeholder only if selected):
```
"use client";
import { useEffect, useRef } from "react";
import { usePathname } from "next/navigation";
import { useTaskUp } from "@taskup/web/react";
export function TaskUpClient() {
const pathname = usePathname();
const previousPath = useRef<string | null>(null);
const taskup = useTaskUp({
projectKey: "YOUR_PUBLIC_PROJECT_KEY",
endpoint: "https://task-up.org",
usage: true,
version: process.env.NEXT_PUBLIC_VERCEL_GIT_COMMIT_SHA,
});
useEffect(() => {
if (!pathname) return;
if (previousPath.current !== null && previousPath.current !== pathname) taskup.trackPageView();
previousPath.current = pathname;
}, [pathname, taskup]);
// Use taskup in the components that handle the selected actions below.
return null;
}
```
Respect the app's visitor notice and any required analytics/storage permission. Only activate usage once the app's permission requirement is met. Do not invent permission or silently bypass an existing consent preference.
Verify the deployed SDK connection, one temporary intentional error, and each selected real signal in TaskUp Setup/Monitor/Overview. Remove temporary test triggers. Public HTTP/SSL monitoring is separate and roughly every 15 minutes within capacity; a browser error alone does not prove an outage. Report the changed files, tests, verified signals and anything that still needs an owner action. Never invent metrics or include private credentials in browser code.When your agent finishes, deploy your app and return to Setup to check the connection.