PRANAV DWIVEDI

Things I
build.

Autonomous agents, local-first interfaces, sports vision and the occasional piece of low-level network code. Twenty-one systems, one software branch.

21 selected systems Open the Stargaze branch

All software now lives under Stargaze.

Stargaze is the independent software branch of my work. The projects below are being folded into it, with a first public release in private build. The full ledger runs from agents and vision to small network tools and earlier archive builds.

See the branch
01

JARVIS

Private build

A persistent personal AI running across rooted Android and Linux. Long-term memory, dynamic tool calling, Android system automation, file access and local or cloud model routing.

PythonAndroidTermuxLocal LLMsFastAPI
Stargaze / Core GitHub
02

AXIOM

Private build

A local and private agent interface with a continuous voice pipeline, embedded console, services daemon and cross-device brain sync between Mac and Android.

TypeScriptPythonNode.jsVoiceAgentic UX
Stargaze / Core GitHub
03

Cricket Motion

Public lab

Webcam-based batting analysis with 33-point pose estimation, bat velocity tracking, swing trajectory scoring and a phone-as-camera streaming mode.

PythonOpenCVMediaPipeNumPyComputer Vision
Stargaze / Lab GitHub
04

VISA-PAY 2.0

Public lab

A handcrafted digital banking interface built around fluid micro-interactions, a liquid-glass surface language and zero heavy frontend dependencies.

JavaScriptCSS3SVGMicro-interactions
Stargaze / Lab GitHub
05

PiXel Arena

Public lab

A competitive Free Fire tournament engine on Firebase with bracket management, registration, live leaderboards, automated scoring and hardened Firestore rules.

JavaScriptFirebaseFirestoreEsports
Stargaze / Lab GitHub
06

MTProto.zig

Public lab

An obfuscated TLS proxy for MTProto written in Zig, built as a small systems exercise in protocol handling and low-level networking.

ZigMTProtoTLSNetworking
Stargaze / Lab GitHub
07

Plutooth

Public lab

Root-based Bluetooth recovery for Android. A Magisk module and Compose utility that repairs the Bluetooth stack on the device itself, with no ADB or desktop.

KotlinJetpack ComposeMagiskAndroid
Stargaze / Tools GitHub
08

Mobile Harness

Public lab

Claude Code on Android: an AI coding IDE that runs commands locally, edits a workspace and keeps a real shell in your pocket.

KotlinAndroidTermuxAI tooling
Stargaze / Tools GitHub
09

Watch Together

Public lab

Serverless watch parties for friends in different places. No account, no backend; the room lives in the browser.

JavaScriptWebRTCHTMLCSS
Stargaze / Lab GitHub
10

Insta

Public lab

A tiny peer-to-peer chat that works without a backend or sign-up. Small enough to read in one sitting.

HTMLP2PJavaScriptWebRTC
Stargaze / Lab GitHub
11

HonestBroker

Public lab

A real-market simulation terminal with spreads, slippage, latency and honest fills instead of fantasy paper trading.

PythonMarket simulationDataTUI
Stargaze / Lab GitHub
12

Local Network Chat

Public lab

Peer-to-peer LAN chat hosted on GitHub Pages. One device opens a room and the rest join without a server.

HTMLP2PNetworkingGitHub Pages
Stargaze / Lab GitHub
13

Remote PC

Public lab

A lightweight remote-control bridge for a desktop from a phone or browser. Input, files and session handoff.

PythonNetworkingAutomationAndroid
Stargaze / Tools GitHub
14

ABV Memorial

Public lab

The tournament site and live record for the ABV Memorial cricket series, built around fixtures, results and player pages.

HTMLCricketResultsWeb
Stargaze / Cricket GitHub
15

Visa Pay UI

Public lab

An earlier payment-interface study: springy cards, balance transitions and a tactile checkout flow.

HTMLCSSJavaScriptUI
Stargaze / Lab GitHub
16

Portfolio / Knowledge Graph

Public lab

The previous personal site, structured as an official entity home with machine-readable profile files.

JavaScriptSchema.orgSEOKnowledge Graph
Archive / Web GitHub
17

GitHub Pages site

Public lab

The GitHub Pages build of the portfolio and the public entry point for the record.

JavaScriptGitHub PagesSEO
Archive / Web GitHub
18

OpenAlgo

Public lab

An open-source algorithmic trading platform with broker adapters, strategy execution and a web terminal.

PythonFlaskTradingWebSockets
Stargaze / Lab GitHub
19

Cloudstream

Public lab

Android media client for streaming and downloading, built around extensible providers and Kotlin.

KotlinAndroidMediaProviders
Archive / Android GitHub
20

Agent Visibility Template

Public lab

A TypeScript starter for making an AI agent's state, tools and decisions visible instead of hiding them behind a spinner.

TypeScriptAgent UXUIObservability
Stargaze / Lab GitHub
21

This site

Public / live

The current multipage build: editorial layout, motion layer, Stargaze branch and a cricket record that has to stay readable.

HTMLCSSJavaScriptMotion
Stargaze / Web Live site

The whole
ledger.

Twenty-one systems, grouped by what they are asked to do rather than how new they are. Some are private builds, some are public labs, and a few are kept only as an archive.

Agents & interfacesJARVIS, AXIOM, Agent Visibility, Mobile Harness.
Vision & sportCricket Motion, ABV Memorial, PiXel Arena.
Tools & networksPlutooth, Remote PC, MTProto.zig, the P2P chats.
Archive & webThe portfolio lineage, VISA-PAY studies and this site.
03 / Elsewhere

The branch,
the record.

The software index is only half the site. The cricket record, the network and the person behind both are one click away.

01 / StargazeThe
branch.Release 01 / soon 02 / CricketThe
record.3,289 runs / 118 wickets 03 / AboutThe
person.Short version

How a build
gets chosen.

Four filters that decide whether an idea becomes a project.

01It has a real userThe first user is usually me, on a device I actually carry. That keeps the requirements honest.
02It has a hard edgeA constraint that cannot be designed away: a phone, a protocol, a moving batter, a bad connection.
03It can be shownA working path is more useful than a roadmap. The build has to survive a short demonstration.
04It can be left aloneThe system should still make sense after a month away from it. That is the maintenance test.

The shape of
the stack.

The tools that recur across the ledger.

Python Kotlin TypeScript Zig JavaScript FastAPI Jetpack Compose OpenCV MediaPipe Firebase WebRTC Termux Android Linux HTML / CSS

A project can use only a few of these. The point is not the logo count. It is how little the build needs to work.

Reading
the status.

Three labels used across the index.

01Private build

A system that is active but not ready for a public repository or a general release. The work exists; the packaging does not.

Stargaze
02Public lab

A working repository or demo released to be read, tested and argued with. It may still change quickly.

Public
03Archive

An earlier build kept for the record. It is not the current direction, but it explains how the work got here.

Archive

Agents and
interfaces.

Software that has to act, explain and stay out of the way.

01JARVIS

Persistent personal AI across rooted Android and Linux, with memory, tools and local or cloud model routing.

GitHub
02AXIOM

Local agent interface, continuous voice pipeline and cross-device brain sync between Mac and Android.

GitHub
03Agent Visibility Template

A TypeScript starter for showing agent state, tools and decisions instead of hiding them behind a spinner.

GitHub
04Mobile Harness

Claude Code on Android: a local workspace, a real shell and an AI coding loop in a pocket.

GitHub

Vision and
sport.

Systems that read bodies in motion.

01Cricket Motion

Webcam batting analysis with 33-point pose estimation, bat velocity tracking and swing trajectory scoring.

GitHub
02ABV Memorial

The tournament site and live record for the ABV Memorial cricket series.

GitHub
03PiXel Arena

A competitive tournament engine with brackets, registration and live leaderboards.

GitHub

Tools and
devices.

Small software that repairs, controls or extends a machine.

01Plutooth

Root-based Bluetooth recovery for Android, built as a Magisk module and Compose utility.

GitHub
02Remote PC

A lightweight remote-control bridge for a desktop from a phone or browser.

GitHub
03Cloudstream

An Android media client built around extensible providers and Kotlin.

GitHub
04Visa Pay UI

An earlier payment-interface study: springy cards, balance transitions and a tactile checkout flow.

GitHub
05This site

The current multipage build, hand-written and tested on an older Android Chrome as well as the desktop.

Live

Networks and
protocols.

The parts that have to work when the server disappears.

01MTProto.zig

An obfuscated TLS proxy for MTProto written in Zig, built as a systems exercise in protocol handling.

GitHub
02Watch Together

Serverless watch parties for friends in different places. No account and no backend.

GitHub
03Insta

A tiny peer-to-peer chat that works without a backend or sign-up.

GitHub
04Local Network Chat

Peer-to-peer LAN chat hosted on GitHub Pages. One device opens a room and the rest join.

GitHub
05HonestBroker

A market simulation terminal with spreads, slippage, latency and honest fills.

GitHub

Web and
archive.

The public surface and the builds that came before it.

01VISA-PAY 2.0

A handcrafted digital banking interface with liquid-glass surfaces and zero heavy frontend dependencies.

GitHub
02OpenAlgo

An open-source algorithmic trading platform with broker adapters and a web terminal.

GitHub
03Portfolio / Knowledge Graph

The previous personal site, structured as an entity home with machine-readable profile files.

GitHub
04GitHub Pages site

The GitHub Pages build of the portfolio and the public entry point for the record.

GitHub
05This site

The current multipage build with the motion layer, Stargaze branch and cricket record.

Live

The build
loop.

The sequence that turns an idea into something I can show.

  1. 01ObserveNotice a repeated friction or a question that will not leave.
  2. 02SketchDraw the smallest useful path. Decide what the system will not do.
  3. 03BuildMake the path work on the target device before adding breadth.
  4. 04BreakTest the old phone, the bad connection, the missing permission.
  5. 05ExplainWrite the readme or the interface copy. If it cannot be explained, it is not ready.
  6. 06LeaveClose the loop with notes and the next open question.

What ships
first.

The first release is a path, not a feature list.

01 / AgentOne useful loop

A single task that can be completed end to end, with visible state and a recovery path.

02 / DeviceOne target

The phone in my pocket before the generic desktop case. The constraints make the design honest.

03 / VisionOne movement

A useful read of a batting stance before a full biomechanics platform.

04 / WebOne page

A route that loads fast, works offline and can be read without a tutorial.

05 / NetworkOne room

A peer-to-peer session that connects without an account or a server.

06 / ToolOne repair

A tool that fixes the specific failure it was built for, then gets out of the way.

Constraints that
improve the work.

The limits I try to keep in the brief.

  • No account unless the product genuinely needs identity.
  • No backend unless the work cannot be done locally.
  • No dashboard unless someone will make a decision from it.
  • No animation unless it explains a state change.
  • No dependency unless it removes more code than it adds.
  • No release until it has been used on the target device.

Interfaces with
a high craft bar.

The visible part is not decoration.

An interface is where the system explains itself. I care about hierarchy, type, timing and the small states that tell a person whether their action landed. A beautiful screen with a hidden error path is still a broken screen.

The work here ranges from agent consoles to payment studies. The common rule is that the interface should make the system more legible, not more mysterious. If the design needs a paragraph of explanation before it makes sense, the design is not finished.

Definition
of done.

The checks I use before an archive entry is called complete.

  • The primary path works on the target device.
  • The error path is visible and recoverable.
  • The readme explains how to run it from a clean checkout.
  • The build does not depend on a secret local setup.
  • The interface has a keyboard and touch path.
  • The next open question is written down.

Signals I
care about.

Not vanity metrics. Evidence that the system is real.

01Works offlineThe useful path does not vanish when the connection does.
02One commandA clean checkout can be running without a setup ritual.
03Readable stateA person can tell what the system is doing without opening a log.
04Survives absenceThe project still makes sense after a month away from it.

Open source
posture.

What is public, what is private, and why.

The lab projects are public because the code is more useful than a description. The core systems remain private while they are still changing under a real user. Release 01 is the point where that boundary gets a proper public shape.

The archive is not a museum. It is a set of past answers to questions that are still live. If an old project becomes relevant again, it can be rebuilt instead of preserved exactly as it was.

Start with
the code.

The repositories are the most direct version of the work.

The
profile.All public repositories JARVIS
core.Agents / Android / Linux Cricket
Motion.Vision / MediaPipe

Project
archaeology.

The buildup, in the order it happened.

  1. 2024Interface studiesPayment and tournament interfaces built to test motion, hierarchy and Firebase rules.
  2. 2025Device toolsRooted Android recovery, remote control and the first local agent experiments.
  3. 2025Cricket recordThe ABV Memorial site and the club record became a public data problem.
  4. 2026StargazeThe systems were folded into one branch with a first-release scope.
  5. 2026This indexThe multipage site became the public ledger for the whole body of work.

The next
six.

The work that is closest to the front of the queue.

01JARVIS memory

Make the memory inspectable: what the agent remembers, why, and how to correct it.

Core
02AXIOM sync

A calmer cross-device handoff that survives a lost connection.

Core
03Cricket Motion

A phone-as-camera path with a usable session review.

Lab
04Agent Visibility

A reusable console for tool calls, failures and recovery states.

Lab
05Stargaze web

The public branch site, with the release notes in one place.

Web
06The index

A better archive filter and a shorter path from project to source.

Web

On the
bench.

Not released. Not forgotten.

01Local model routing

A small router that chooses between local and hosted models without hiding the cost.

Experiment
02Bat speed capture

A cheaper way to measure bat path with a single phone camera.

Experiment
03Static search

A site search that works without a server or a third-party index.

Experiment
04Match notes

A lightweight notebook for fixtures, conditions and the decisions that followed.

Experiment

Bring a hard
constraint.

The best projects start with a limit that cannot be argued away. If you have one, send the short version.

Send a note
Best fitAgents / Android / vision ResponseUsually a few days BasedIndia / IST