# Lookout: an ICP dashboard so I can see what my AI teams are doing

**URL:** <https://forum.dfinity.org/t/lookout-an-icp-dashboard-so-i-can-see-what-my-ai-teams-are-doing/76272>\
**Category:** Showcase\
**Created:** [November 1, 2026, 7:39am UTC](https://forum.dfinity.org/t/lookout-an-icp-dashboard-so-i-can-see-what-my-ai-teams-are-doing/76272 "2026-11-01T07:39:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![robvector](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/robvector/32/40790_2.png) [@robvector](https://forum.dfinity.org/u/robvector)\
**Post date:** [November 1, 2026, 7:39am UTC](https://forum.dfinity.org/t/lookout-an-icp-dashboard-so-i-can-see-what-my-ai-teams-are-doing/76272/1 "2026-11-01T07:39:57Z")

</div>

I built a small app called Lookout because I have several projects going at once, with AI agents working on different parts of them, and I wanted a better way to see what was actually happening.

What’s being worked on? What’s held up? What’s being prioritized? And if something is blocked, is useful work happening somewhere else?

The agents already had their boards and team orchestration workflows. They seemed perfectly happy with that arrangement. But information being available somewhere in a chat or a file isn’t quite the same as being able to open a page and see the whole thing. I wanted that view for myself.

Lookout gives me a private dashboard where I can switch between projects and see their boards, priorities, blockers, and status updates. It lets me feel like I’m part of the work, even when it’s spread across a bunch of different agent conversations.

You can [see an example screenshot in the repository](https://github.com/RobRipley/lookout/blob/main/docs/lookout-example.png), using fictional project data.

The features mostly came from things I wanted while using it:

- Projects grouped by repository, with a Kanban board for each.
- Ranked subprojects beside the overall status, so I can see where attention should be going.
- Plain-English status updates, with a technical version available when I want the details.
- Task owners and priority numbers on the cards, plus clickable definitions for terms I don’t recognize.

There’s also a full-board view and timestamps so I can tell when an update is getting stale.

The way I want my teams to use it is pretty simple. A supervisor sets priorities, and orchestrators handle individual subprojects. When something gets blocked, available effort should move to something useful instead of everyone sitting around waiting. But I also don’t want everything running simultaneously at full blast. Agent usage costs money, and more activity doesn’t necessarily mean more progress.

The agents’ orchestration skills and instructions handle those decisions. Lookout gives me a way to see them. Agents publish updates from their existing boards, so keeping it current is part of their workflow.

It runs on ICP with a Motoko backend, a React frontend, and Internet Identity for login. Two canisters, with no separate database or application server to manage. The projects you track don’t have to be ICP projects.

The [repository is public](https://github.com/RobRipley/lookout), under a source-available license, and includes instructions for deploying your own private copy. You supply your own canisters and cycles. You can give your coding agent this:

> Deploy my own private Lookout instance and connect my project agents. Follow [https://raw.githubusercontent.com/RobRipley/lookout/main/AGENTS.md](https://raw.githubusercontent.com/RobRipley/lookout/main/AGENTS.md)

I made this for myself, but I figured other people working with agent teams might find it useful too. How are you keeping track of everything when you’ve got several projects going?
