Force5 Development
Back to builds

Migizi.app

Migizi.app started on March 27, 2026 as a web evolution of Rivet Core. It keeps the useful planning pieces, but shifts them into a hosted personal hub shaped by how Codex changed my day-to-day workflow.

3/27/2026

  • Started March 27, 2026 as an evolution of Rivet Core, not a literal desktop-to-web port.
  • Built around markdown-lite import, LLM-friendly copy/export, scratchpad work, and day time-block review.
  • Private hosted system today, with shared-planning SaaS handoff and possible broader access later if there is real interest.
PrivateHostedActive daily use
workflownotestodoaiazurescheduling

Related build: Rivet Works

Timeline

  • March 27, 2026: started as a web evolution of Rivet Core desktop
  • Early direction: keep the useful planning and review pieces, but stop treating it as a literal desktop port
  • Current state: active hosted personal hub, still private

Relationship to Rivet Works

Migizi.app sits close to Rivet Works, but it is not just “Rivet Core in a browser.”

Rivet Works came out of a capture-everywhere problem: extensions, local stores, desktop hub, and moving notes or TODOs between them without losing flow.

Migizi.app came from the next version of that same problem. Once Codex changed how I work, I needed less “capture from every app” and more “keep the right information in a hosted place where I can review it, reshape it, copy it into an LLM, and turn the result back into practical next actions.”

Problem as experienced

My daily loop shifted. A lot of planning now happens with Codex inside VS Code, not by manually filling out TODOs inside an extension.

That changed what mattered:

  • easy note and TODO review
  • import of simple markdown-lite content that an LLM can produce cleanly
  • easy copy/export of notes and TODOs back into an LLM
  • a scratch pad for rough text work
  • a day time-block layout that is more practical for my planning than a normal calendar

Core workflow

  1. Draft or generate lightweight task and note text in the editor or with an LLM.
  2. Import that markdown-lite content into Migizi.app.
  3. Review, edit, and reshape TODOs or notes in a simpler hosted interface.
  4. Use the scratch pad and day time-block schedule while working.
  5. Copy or export text and schedule metadata back into an LLM to analyze what got done, what slipped, and what the next TODO pass should be.
  6. Push items into a shared planning SaaS when they need to leave my personal system and be shared with other people on a project.

What is working now

All of the core pieces I wanted from this version are working now:

  • markdown-lite import for structured note and TODO capture
  • LLM-friendly copy and export for notes and TODOs
  • scratch pad for plain-text staging, cleanup, and quick paste work
  • day time-block scheduling instead of a conventional calendar layout
  • export of schedule-related metadata for LLM review and regenerated planning
  • shared planning SaaS handoff for collaborative project lists

Hosting and implementation notes

  • hosted on Azure Web Apps
  • Azure SQL plus blob storage behind the app
  • current AI workflow is mostly Codex in VS Code, sometimes T3 code
  • auth is intentionally minimal right now: one preseeded account, no self-serve account creation

Current state

Migizi.app is active and useful right now, but it is not a public product yet.

There is no general-access signup flow, and there is no reason to point people at a login screen that only serves my current private use. If that changes, this page will change with it.

If you are interested in trying it, email migizi@force5dev.com.