I’m Srijan, a developer and student in India. I build native desktop and mobile apps, mostly things I wanted to exist and couldn’t find, and the agent tooling that helps me build them faster.
The habit I care about most: ship it properly. Signed builds, quality gates, useful release notes, and documentation that is honest about what works and what is still an experiment.
Swift & SwiftUI · Rust · TypeScript · Python · Kotlin
macOS · iOS · Android · agent tools & MCP
A few projects that best show what I build: native interfaces, useful everyday tools, and the systems behind agents.
|
The MacBook notch, put to work. Meetings, clipboard, media, Focus, and system status in a local-first AppKit and SwiftUI dashboard.
|
Give the desktop a little life. Live video wallpapers, a local library, and battery-aware playback. SwiftUI / AVFoundation on Mac; Electron on Windows.
|
|
Know what your connection is doing. Live traffic in the menu bar, manual speed tests, and outage detection. Public builds are ad-hoc signed, not notarized.
|
A new model connection. The same tools. A compatibility gateway that preserves Muse’s tools, approvals, and sandbox. Source-only, Apple silicon, pinned Muse version.
|
|
An inbox an agent can reason about. Typed triage capabilities for follow-ups, obligations, and daily briefs, with services for persistence and scheduling.
|
The Android typing feel, on iPhone. AOSP-inspired key geometry and multi-item clipboard history inside an iOS keyboard extension.
|
| Project | What I’m building | Where it stands |
|---|---|---|
| P-Agents | A Rust agent harness with streaming, isolated sub-agents, gated tools, and replayable sessions. | Learning and building in public. |
| P-Harness | A TypeScript research CLI: deconstruct, explore, deep-read, and produce cited reports. | Research tooling. |
| Sera | ReAct CLI, SQLite/FTS5 memory, provider adapters, approvals, and context compression. | First five phases of a 100-phase plan complete. |
| AI.Trader | Multi-agent market research, alternative data, backtesting, and portfolio experiments. | Research; not investment advice. |
| AI Constitution | A shared governance layer for my AI tools, with secret checks and launch safeguards. | Workflow infrastructure. |
| 120fps Player | An Android player exploring on-device motion interpolation. | Player and diagnostics run; frame interpolation is not implemented. |
| Budget Guard | An iPhone grocery budget tracker with integer-paise totals and weight-based entry. | Phase 1 complete; scanning and Live Activities are planned. |
Prompt Forge turns rough ideas into structured AI prompts.
claude-design-mcp prepares project context for Claude Design through a Rust MCP server.
iPhone Wallpaper Resizer is a drag-and-drop, offline HTML utility.
Research Pro packages academic research workflows as skills and commands.
New Jarvis starts a macOS workspace with a double clap.
Trieon Labs is the home for the things I’m building.
Existing logos and project artwork from the rest of the collection.
 P-Harness |
 AI Constitution |
 Veronica |
 Friday Core |
 Trieon Labs |
 Nagi / Anti |
 DockBuddy |
Play Quiet Days Quest →
Roll the dice or start the automatic tour. My mini avatar winds through the quiet squares, passing over contribution days. A small corner chart keeps track of active days, quiet days, and your journey.
An empty square means no recorded GitHub contributions, not “no work.” Studying, resting, and building offline belong in the story too. The README plays an animation; the linked playground is interactive.
Charts refresh daily through GitHub Actions. Calendar totals follow GitHub’s contribution rules. Language bars count public original repositories by their primary language, excluding forks; they are not percentages of commits.
The earlier assistants, prototypes, plugins, and forks are still here. Browse the complete public project catalogue for all 47 repositories found in the September 2026 rescan, including the Friday / Veronica lineage and the experiments that never reached a finished release. Forks are labelled as forks.
Profile history & how this page works
The previous README is preserved as a historical snapshot. The redesigned profile is generated from public repository metadata and the contribution calendar. The maintenance guide explains the data, animation, game controls, and daily refresh workflow.
Most of what’s here started because I wanted the thing to exist.
If one of them is useful to you too, that’s the best part.