Home · Community report
Run a personal task dashboard app
Run a personal task dashboard app. Hand your existing task tracker to Instinct so it keeps running without a web login.
What you can get
Reaches your accounts Creates or changes things in accounts you connect, with your approval.
-
It does
- Reads and updates the tracker through the token you provide
- Does not take on new permissions without your say
-
It stops and asks
- Before handing over a token: scope it to only the actions the tracker needs.
- Before trusting the display: watch it for a few real days, not just the first setup.
- Before leaving it unattended: know what happens if the token or sensor stops working.
-
You approve
- You decide the scope of the token before handing it over
Derived from this task's own brief and steps, not from the source.
- Pick the tracker
Name the existing app and what you want kept current.
- Create a scoped tokenStops for your approval
Limit access to only what the task needs.
- Choose a display method
Browser, tablet, or a dedicated screen.
- Watch it over real daysStops for your approval
Confirm it stays current before relying on it.
Editorial, not from the source
Works when
- You already have a working personal tracker and just want it running without a browser.
- You're comfortable creating and scoping an API token yourself.
- You want a passive display rather than another app to check.
Does not work when
- You don't yet have a tracker built, since this keeps one running rather than building it from scratch.
- You'd rather not hand out a standing token to any tool.
- You need guaranteed real-time updates rather than a periodically refreshed view.
Run a personal task dashboard app: setup template
| Item | What it's based on | Status |
|---|---|---|
| [Token scope] | [Tracker's own API settings] | [Confirmed by you] |
| [Sync targets] | [Calendar or other linked tools] | [Matches source data] |
| [Display method] | [Device or sensor used] | [Tested over real use] |
The source case
On X, @karolina_dubiel describes building a personal tracker called Table that combines features from Notion and Google Calendar, synced with Canvas for assignments and Google Calendar for tasks. Rather than keep opening it in a browser, the author made a token so Instinct could run Table instead, and paired an old monitor with a presence sensor and a Raspberry Pi so the dashboard turns on automatically when they sit at their desk. The post describes the author's own build and does not say how the display is kept current minute to minute, or what happens if the token or sensor stops working. Checked on 2026-10-09 as a single report.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
So, I made a token for Instinct to run Table for me instead, plus finally put the 2002 Samsung monitor in my room to use with a 24 GHz mmWave radar presence sensor and a Raspberry Pi.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring A tracker or app you already use, A token or API key for it. Acts Reads and updates the tracker through the token you provide. Does not take on new permissions without your say. Source community report, checked 2026-10-09.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- A tracker or app you already use
- A token or API key for it
Connected
- The tracker's own API or integration
- Optionally a calendar it should stay synced with
How to try it
Editorial, not from the source
- Point Instinct at the tracker you already use, with a token or API key scoped to what it needs to read and update.
- Tell it which other tools the tracker should stay synced with, such as a calendar, so due dates don't drift out of step.
- Decide how you want to see it: a kept-open browser view, a screen on a timer, or a presence sensor that wakes a display when you sit down.
- Check a few days of real use before calling the setup done, and confirm what happens if the token expires or the sensor misfires.
Start from a tracker you already trust
The report behind this page starts with a tracker the author had already built and used all summer, combining a calendar view with task due dates and assignment deadlines. That ordering matters: this is about keeping an existing tool running, not designing one from scratch. Before involving an agent, be clear about what the tracker already does well and where the friction actually is. In the reported case, the friction was specific: having to open a browser to check it. If your own friction is different, such as the tracker missing a feature, that is a separate problem from handing it a token to run unattended. Name the tracker, its API or integration point, and the exact fields you want kept current before asking an agent to take it over.
Scope the token before the display
A standing token is a different kind of access than a one-off question, because it keeps working after you've stopped watching. Before anything else, decide what the token can read and what, if anything, it can write back, and create it with only those permissions where the tracker's settings allow it. The reported setup synced two systems, a calendar and a task table, which means two sets of permissions to think through rather than one. If the tracker does not support a narrowly scoped token, treat that as a real limit rather than working around it with a full-access key. The display is the visible part of this setup, but the token is the part that keeps running when no one is looking at the screen.
Treat the hardware as optional, not required
The physical side of the reported build, a spare monitor, a radar presence sensor and a small computer, is the most distinctive part of the story but the least necessary part of the task. The underlying idea, an agent keeping a tracker current without your having to open it, works with a browser left open, a tablet on a stand, or a scheduled screenshot emailed to you, with no sensor required. If you do want a dedicated display, test it running for a stretch of ordinary days before relying on it, since a demo that works once on a new setup can still fail quietly a week later. Decide in advance what you'll do if the automatic view goes dark: usually, just checking the tracker directly.
Open Instinct to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
- This is one report of a highly custom build: an existing tracker, a spare monitor, a presence sensor and a Raspberry Pi. Most of the hardware work is the author's own, not something Instinct did for them.
- The post does not say how often the display refreshes or what happens when the token lapses.
- Giving an agent a standing token to run a tool is a broader access grant than a one-off request; scope it to only what the tracker needs.
- No sensor hardware or display wiring is included here. Unknown: reliability over weeks rather than the single setup described.
Editorial, not from the source
- Before handing over a token: scope it to only the actions the tracker needs.
- Before trusting the display: watch it for a few real days, not just the first setup.
- Before leaving it unattended: know what happens if the token or sensor stops working.
Editorial, not from the source
- The display shows stale data
- Check the sync interval and whether the token is still valid; an expired token will freeze the last successful read.
- The dashboard doesn't turn on when you sit down
- Check the presence sensor's range and placement before assuming the agent side has failed.
- Calendar and tracker drift out of sync
- Confirm which tool is the source of truth for due dates and have Instinct read from that one only.
Common questions
Can Instinct run my existing task tracker for me?
One user reports making a token so Instinct could run a personal tracker they had built, instead of opening it in a browser. This directory has not reproduced the setup.
Do I need special hardware for this?
No. The reported build used a spare monitor and a presence sensor, but the underlying task, keeping a tracker current without a browser, works with any display you already have.
What access does the agent need?
A token or API key scoped to the tracker, limited to only the reads and writes it actually needs. Decide the scope before handing it over.
Will it keep a calendar in sync too?
The reported setup synced a calendar and a task table. If you want the same, name both systems and which one is the source of truth for dates.
What if the token stops working?
The report doesn't say. Check your tracker's token expiry settings and have a fallback for checking it directly if the automatic view goes stale.
Next in Home
Get recurring task recommendations — ask your own agent to check for relevant updates.