What we are building,
and what ships next
ShadowPhone is actively developed. This page reflects our current priorities, what is in progress, and what is planned based on operator feedback and platform requirements.
Timelines are estimates, not commitments. Priorities shift based on real-world usage.
Active development
These are being actively built or are in final testing. Estimated ship windows are listed where available.
MCP integration layer
A Model Context Protocol endpoint so external AI agents and tools can trigger ShadowPhone workflows, read account state, and act on fleet data through a standard protocol.
Per-slot engagement locking
Prevents two scheduled slots from running engagement workflows on the same account simultaneously — eliminates a race condition in high-frequency schedules.
Reel trial posting
Post reels directly into the Instagram trial-reel flow. Trial reels reach a broader audience before committing to the main feed — useful for testing content before full publish.
On the roadmap
Confirmed direction items with no hard ship date yet. These will move into active development as current priorities clear.
Android 15 / GrapheneOS 2025 compatibility
Full validation and updated ADB selectors for the latest GrapheneOS builds. Includes recalibrated coordinate maps for all posting and engagement flows.
Multi-device campaign orchestration
A campaign layer that distributes posting and engagement workloads across multiple phones with built-in pacing, account assignment, and failure recovery.
Webhook outbound events
Push events (post completed, engagement session done, account flag detected) to any external endpoint — Zapier, Make, or your own backend.
Windows background service mode
Run the ShadowPhone executor as a Windows service rather than a foreground Electron app, allowing the phone to stay active when the desktop is locked.
Supabase-native account registry
Migrate account configuration from local JSON to a Supabase-backed registry so multiple desktop operators can share and sync account state without manual file transfer.
Engagement-only account mode
A lightweight run mode for accounts that only perform engagement (likes, follows, story views) without posting — useful for warm-up and reach-maintenance accounts.
Recent releases
Highlights from the last several releases. Full version history is in the changelog.
Multi-profile GrapheneOS isolation
Each Android user profile separates Instagram app data, sessions, cookies, and storage on one physical device. Profiles share the phone's underlying hardware and default network path.
AI content generation pipeline
Built-in caption generation, hashtag research, and image prompt tooling connected directly to the post scheduler — no external copy-paste step.
Fleet analytics dashboard
Per-account and per-phone KPI roll-up: reach, engagement, post frequency, and growth trend — across the full connected fleet in one view.
USB + Tailscale dual-path routing
Executor routes read-heavy operations over a local USB connection and write operations over Tailscale, reducing contention and improving reliability during active sessions.
Story viewing with randomised cadence
Story viewing runs at a random 1–6 view count per session with jitter between interactions — operating pattern that matches human behaviour.
Have a feature request?
The roadmap is driven by what operators actually need. If something is missing that blocks your workflow, reach out — real operator problems move faster than abstract feature votes.
Submit a request