Spyglass: Dev Dashboard
See what the agents changed. Ship it from your phone.
An iOS-first developer dashboard for the agentic era: follow a branch, review what the coding agents wrote, make a small fix, commit and merge, without opening a laptop.
- Platforms
- iPhone and iPad
- Status
- In development · TestFlight beta in preparation
- Works with
- GitHub · Railway · Supabase · Vercel (next)
01 · The loop
Agents write the code. You keep the helm.
Coding agents open branches and pull requests while you're away from the desk. Spyglass is built around the few minutes it takes to check their work and send it on its way.
-
Notice
A push notification when an agent opens or updates a pull request, or when CI turns red or green.
-
Review
The branch's changed files against its base, as clean, swipeable diffs, with the PR's checks and description.
-
Fix
A lightweight, syntax-highlighted Notepad for the small fix. Edits are held as pending changes and survive restarts.
-
Ship
Commit and push in one sheet, with an AI-suggested message if you want one. Open the PR or merge it from the same screen.
02 · What it does
Small screen, whole picture.
Review
-
Projects at a glance
An overview of what needs you across every watched repository: PRs waiting on review, branches ready for a PR, recent pushes and merges.
-
Diffs made for a phone
Changed files against the base branch, one swipe per file, with local edits marked so you can tell your change from the agent's.
-
Agent-aware
Copilot and other agents' branches and bot-authored PRs are recognised, so agent work shows up where you look for it.
Edit and ship
-
Notepad editor
CodeMirror in a native shell, with Xcode-style highlighting, dark mode and Dynamic Type. For the quick fix, not a whole IDE.
-
Safe commits
Commits check the branch hasn't moved underneath you first, and a conflicting edit is kept for you to resolve rather than overwritten.
-
PRs, merges and nudges
Open or merge a pull request, re-run failed checks, or post a comment such as “@copilot please fix the failing test”.
Around the code
-
Railway
Deployments and per-service metrics, history and alerts, with confirmed restart, redeploy and rollback behind a separate switch.
-
Supabase
Schema, rows and read-only SQL for the project bound to a repository, plus a SQL terminal whose writes stay off until you turn them on.
-
Vercel
Coming next: the exact preview for the commit you're reviewing, its build output, and the merged revision's road to production.
03 · Vercel integration · Development / test integration
Preview this change, not the latest one.
The Vercel integration ties deployments to the commit under review. On a branch or pull request it will show whether that exact revision has a preview, open it, explain a failed build through its output, and follow the merged commit to production. A green build isn't called a healthy app, a preview is never mistaken for production, and the newest deployment is never assumed to be the one you're reading.
| Scope | Access |
|---|---|
| Integration Configuration | Read |
| Projects | Read |
| Deployments | Read |
| Everything else | None |
Read-only by design. Write actions such as redeploy or rollback would need a separate,
clearly labelled consent. The current registration is for development and testing, and
redirects to http://localhost:8977/callback.
04 · Principles
Fewer features, done beautifully.
-
Review over write
Agents write the code. The phone is for reviewing, nudging, small fixes and shipping. It isn't an IDE.
-
Branch-centric
Everything starts from a branch you care about. Repositories, PRs, CI and agents are context around it.
-
Three taps to ship
From a notification to diff, tweak and commit or merge, in three taps.
-
No local clone
Every git operation goes through the provider's API. The phone never clones a repository.
Spyglass wears the studio's own design system: the same deep-water palette, Cormorant display type and instrument-panel labels as this site, with full dark mode and Dynamic Type support.
05 · Roadmap
Charted, leg by leg.
Each stage ships only after it's been checked on a real device. “Device testing” means built and waiting for that check.
- Built
- Built · device testing
- In progress
- Next
- Later
- Built
Review core
GitHub sign-in, watched projects, branch changes and swipeable diffs, the Notepad and pending edits.
- Built · device testing
Ship from the phone
Commit, open and merge PRs, notifications for agent PRs and CI, and AI-suggested commit messages.
- Built · device testing
Railway and Supabase
Deploys, metrics, alerts and guarded actions on Railway; schema, rows and a SQL terminal on Supabase.
- Built · device testing
iPad, Sign in with Apple and sync
Two-column layouts on iPad, and settings that follow you across devices.
- In progress
Polish and TestFlight
Accessibility, launch and first-run polish, then the first TestFlight build.
- Next
Vercel: connect and preview
Connect selected projects, then show the preview for the exact commit beside its diff, with build output and production status.
- Next
Vercel: alerts
Signed deployment events and a 15-minute check that catches anything missed, delivered as notifications.
- Later
Vercel: guarded actions
Cancel, redeploy, roll back and promote, each behind its own consent and only once proven against real projects.
- Later
More git hosts
GitLab and Bitbucket, behind the same provider interface GitHub uses today.
Resources
Spyglass resources
- Documentation Install and connect the Vercel integration, choose projects, permissions, data and troubleshooting.
- Terms of use The licence, permitted use, termination and support for Spyglass and its integrations.
- Privacy policy What Spyglass reads from Vercel and your other connections, what it keeps, and for how long.
Want a look through the glass?
The TestFlight beta is in preparation. Email to be on the list, or to ask anything about Spyglass.
contact@anchoreddev.com