Hi there 👋

Hi, I'm Steve 👋

📍 New York City ↔ San Francisco | 🧪 VP of Engineering @ Flox | 🚀 Former: Founder & Asana, Instagram, & Yahoo!

Working with Ron Efroni on the future of agentic infrastructure — reproducible environments, deterministic agents, and the build loop after CI/CD. Leading Flox's AI transformation across engineering.

If it isn't reproducible, it didn't happen. Spending most of 2026 figuring out how engineering org workflows change when agents do the typing.

🌱 flox.dev — open source infra for reproducible environments and agentic workflows.

Start Here

• 🌱 Flox — reproducible dev environments built on Nix, the AI-transformation layer for your build loop
• 🎤 GitHub Universe 2026 — two panels on agentic infrastructure (see Speaking below)
• 🦉 thoth — multi-provider deep-research CLI; orchestrates OpenAI Deep Research + Perplexity in parallel
• 📺 TikTok / @stevemorinnyc — making AI concepts make sense for people who don't have time to read papers

Current Projects

• 🦉 thoth — AI-powered research assistant; CLI that runs deep technical research across OpenAI and Perplexity in parallel and ships clean, citable reports
• 🌀 thothspinner — Claude Code-inspired TUI animation library for Python (Rich-based): spinners, progress bars, timers, shimmer effects
• 📝 envgen — Generate and validate .env files from a single spec; self-documenting, consistent across environments, secrets stay out of git
• 📐 agent2linear — Linear CLI built for humans and AI agents; optimized to minimize token usage and context-window waste
• 🔀 toggle — Rust CLI + library for toggling, adding, removing, and updating code/comments across many languages, with configurable extension mappings
• 🌳 worktreeflow — CLI for spinning up git worktrees against OSS projects and managing PRs without losing your mind
• 🐍 py-launch-blueprint — Production-ready Python project template with the best practices already wired in
• 🌱 filegardener — File maintenance utilities: dedup, only-copy detection, prune empty dirs
• 🪨 substrata — Foundational tooling layer (WIP)
• 📦 vagrant-flow — Vagrant plugin for a seamless dev-to-prod workflow with Ansible; auto-generates inventory files, runs playbooks, manages hostfiles

What I'm Building at Flox

• 🧬 Flox CLI extension system — Rust port of the gh extension architecture, with environment inheritance and a phased rollout plan
• 📊 nixpkgs vs Homebrew strategic dashboard — coverage, freshness, overlap; informing where Flox lifts vs. competes
• 🤖 Codex-plugin-shaped long-running agent — broker / job-tracking architecture inspired by the OpenAI Codex plugin for Claude Code
• 🚀 AI transformation — helping transform culture to be AI First: pair programming show-and-tells, tooling standardization (Anthropic + OpenAI), shipping real features, producing artifacts to train the rest of the org

Speaking

• 🎤 GitHub Universe 2026 — Secure every commit track "From Vibes to Verified: Engineering Deterministic, Secure Agents" with Ron Efroni (Flox), Dex Horthy (HumanLayer/CodeLayer), Ankur Goyal (Braintrust)

Previously

• 🛫 CTO, Tripping.com (acquired by HomeToGo)
• 📸 Engineering Leadership, Instagram
• ✅ Engineering Leadership, Asana
• 📞 Engineering, AT&T

GitHub Activity

What I'm Doing

• Leading an AI transformation — pair programming workflows, tooling standardization (Anthropic + OpenAI), shipping the boring rails so the interesting work compounds
• Teaching AI on TikTok — translating agentic patterns for engineers who don't live on hn
• Hiring — Flox is bringing on contractors and full-timers around platform + Nix work
• Hiking — the only meeting I never reschedule

Connect

---

Philosophy

"Reproducible or it didn't happen." Most engineering wins are unglamorous: shorter feedback loops, fewer special snowflakes, more determinism. Agents amplify whichever side of that ledger you've invested in.

Random Facts

• Run multiple Claude/Codex instances in parallel; the bottleneck is reading their output, not generating it
• Powered by Pacific Heights fog and two kids' worth of pre-7am energy
• Believe most "AI transformation" is just finally writing down what your senior engineers already do
• Hiker first, VP second
• Self-aware about context-switching across N projects; building tooling so the switching tax goes to zero