Private dashboard
A local view of selected task state and outputs.
When this is worth adding
You repeatedly open several files to find your next action.
First complete a useful task and a fresh restart in your existing folder. Keep the same team and add only the capability this problem needs.
Plan it with your team
Open your existing team project and paste this prompt. It produces a proposal for review.
Help me plan a private dashboard for this team. Ask which saved information I need to see and what I want to do from it. Start with a read-only local view using synthetic data. Explain storage, bind address and access before building. Keep the task files authoritative. Propose manual refresh first; add automatic updates only after we verify a real source and refresh path. Do not publish or add a scheduler during planning.If copying is blocked, select the text and copy it manually.
What you should have
A bounded proposal with selected inputs, an output, ownership, permitted tools and acceptance checks. Planning only. No dashboard server or refresh job is installed by this guide.
Checks before relying on it
- Prove the page reads the intended source and shows its freshness.
- Verify the actual listening address and reachable audience; a local folder alone does not make a server private.
- Test restart, stale data and how to stop the server.
Record actual results, limitations and anything not run. Add execution instructions only after the intended tool and access are verified.
Return to your work
Continue in your existing team or choose another topic. There is no need to rebuild the team.