Instructions for a coding agent
Give your agent this page and the project-specific public key from TaskUp Setup. The key identifies your project and is safe to include in browser code.
Get a prompt for your app
Open Setup in your TaskUp project and choose Set up with my agent. Use Set up everything with my agent, or select the signals and controls you want and copy the tailored prompt. Products and cost setup is optional. You can also preview onboarding or use the manual path.
1. Inspect the app
Find its framework, root browser entry point, routing, authentication and existing feature flags. Keep the app's working behaviour. Ask the owner before replacing an existing flag system or enabling usage tracking without an appropriate visitor notice.
2. Install and connect
Run npm install @taskup/web. In TaskUp Setup, choose the app's framework and copy its component and mounting instructions. Choices include both Next.js routers, React with or without React Router, Vue with or without Vue Router, Nuxt, SvelteKit, Svelte and other JavaScript apps. Mount the integration once in the browser. It has the project key and endpoint already filled in. Do not put private credentials in browser code.
3. Verify real signals
Deploy the app, load a page, then use Check connection in TaskUp Setup. The integration reports uncaught browser errors. When usage is selected, it also reports the initial page view and completed pathname changes; query and fragment changes are not separate page views. Hash-only routing needs separate consideration and is not covered by the ready-made snippets. The production URL is checked separately by TaskUp's HTTP monitor. Temporarily trigger one intentional browser error to confirm it appears in Monitor, then remove the test trigger. Do not leave fake events in production.
4. Add safe controls only when requested
Register a control in TaskUp Control, then read its key using taskup.boolean, taskup.string or taskup.number in the app. Keep a local fallback. TaskUp cannot edit arbitrary code or change a flag that the app does not read from TaskUp. Existing feature flags can remain; route a particular flag through TaskUp only if the owner wants TaskUp to control or schedule it.
5. Know the data limits
usage: true counts visits, page views and estimated daily active browsers without a user ID. If the app already authenticates users, it may supply its own stable signed-in user ID for account-based daily activity counts. TaskUp cannot discover a site's login state or total registrations from the SDK alone. Calls such as trackClick(), trackConversion() and reportNetworkFailure() belong at the real action or failure in the host app. Server errors need explicit reporting. Never send passwords, cookies, tokens, form contents or payment data.
6. Optional costs and estimated profit
Revenue comes from the connected Stripe account, after refunds known at sync. Stripe does not know the app's product, hosting or other business costs. Help the owner prepare costs for the same completed UTC day and currency in TaskUp Settings. Product unit costs and units sold can be entered in the optional calculator. The owner reviews and saves the totals; TaskUp calculates estimated profit automatically. Do not ask for manual revenue or profit, change live Stripe prices, invent expenses, or claim a save without completing it. Payment fees are currently cost inputs; this connector does not import them automatically.
Finish with evidence
Run the host app's lint, typecheck, tests and production build. Confirm the TaskUp connection, a real page view, an intentional test error and any registered control on the deployed app. Report which signals work and which integrations still need credentials.