Live · release v245 Built for the OpenAI WebMCP Challenge Open source · MIT on GitHub

inite

Live product

Adaptive planning with Codex

Plans that survive contact with reality.

A trip, a renovation, an event. Something changes, but the limits do not. Tell Finite what moved. Codex explores the trade-offs on your plan, Finite checks them, and you choose which revision to accept.

Open Finite Run the live walkthrough

Use your ChatGPT sign-in to save plans in Finite. The demo needs no Finite account; its guided walkthrough uses Codex. How to connect · Start your own plan

Planning only: Finite does not book, buy or pay.

Human orderAdd three nights in Paris.

Demo / revision 1 → 2
Reality changed

Three more nights cost A$660. Keep the total budget and at least A$500 of breathing room.

  1. 01

    Total budget

    A$6,500 held
  2. 02

    Paris stay

    4 → 7 nights
  3. 03

    Netherlands

    2 fewer nights
  4. 04

    Accommodation

    3 more hostel nights
  5. 05

    Optional tour

    Removed
  6. 06

    Breathing room

    A$910
Changed realityAccepted revision 2

One choice, not a free upgrade The prepared demo finds five distinct directions. This one saves A$820 to cover A$660 of new costs, leaving A$910 spare. Inspect the actual run.

Captured walkthrough / release v245

Compare. Choose. Keep the receipt.

A real run using a prepared example plan. Finite checks 26 combinations, rejects eight and presents five distinct directions from the 18 that pass its rules.

Finite's Decisions surface: 26 bounded combinations tested, 18 satisfy the demo rules, eight are rejected and five distinct directions are shown.View full size ↗
01 / Compare the trade-offsFive distinct directions pass this example's rules. Compare what each preserves and what it gives up before making a choice.
Finite after the person confirms Protect breathing room: Codex can apply only this exact update to revision 1.View full size ↗
02 / Only you approveThe approval is tied to one option and one version of the plan. Codex cannot fake it, and nothing changes until you give it.
Finite's demo receipt: revision 1 becomes revision 2, the recorded duration changes from 18 to 21 days and AUD 910 remains free.View full size ↗
03 / Codex applies your choice onceThe plan moves from version 1 to 2 with a receipt. Reload and it is still there. Run the same call again and nothing doubles up.

What this example proves: budget trade-offs, an exact approval and a saved revision. The fixture blocks the flight-change option but does not model flight dates. Its receipt records 18 → 21 days; that is not a verified flight-compatible itinerary. Inspect the demo model ↗

Try the same change.

Open the demo in a browser connected to Codex. Check for Demo mode · Local only, select Hand off to Codex, then Start the live walkthrough. If you receive an introduction to copy, paste it into your Codex task and keep the Finite tab open.

The guided run needs Codex and a WebMCP connection, but no Finite sign-in. Follow the browser setup guide ↗. You can inspect the example without connecting an agent.

Run the live walkthrough

Different plans. Different surfaces.

The plan sets the shape.

A trip has stays. A renovation has phases. An event has a running order. Finite gives each its own working surface, with the same rules for checking and approving a change.

Illustrative previews These explain the plan surfaces. The captured walkthrough shows the running product.

Same engine. Travel surface.

More Paris. Here is what gives.

Demo directionProtect breathing room

Request

“Add three nights in Paris. Keep the total budget and preserve at least A$500.”

Finite checks

Tests combinations of the demo's permitted changes against its budget and rules.

26 tested → 5 directions
+ A$660 costParis

Three extra nights

A$320 savedNetherlands

Two fewer nights

A$260 savedHostel mix

Three more hostel nights

A$240 savedOptional tour

Removed from the plan

Budget resultA$750 spare + A$820 saved − A$660 added = A$910.

Awaiting human approval

Why WebMCP

A kitchen for your AI. A result for you.

You should not have to carry a plan back and forth between an app and a chat. WebMCP lets Codex use Finite's tools on the page you are looking at.

Codex handles research and proposals. Finite checks the modelled rules and records the accepted revision. Your approval belongs to one exact choice, not a blanket permission to act.

View the engineering and build log ↗View source ↗

Your plan / your starting point

Start with what you know.

You do not need a finished brief. Describe what you want to make happen, then add the dates, budget and commitments you already have.

  1. 01 / Describe

    Write the outcome.

    A sentence is enough to start. Include what changed and anything that must stay put.

  2. 02 / Build

    Choose how to work.

    Build with Codex or use the manual workspace. Add missing details and edit the plan as you go.

  3. 03 / Review

    Check before accepting.

    Review the assumptions, limits and proposed changes. Decide what becomes the accepted plan.

Accounts and storage. ChatGPT sign-in gives you a saved Finite workspace. Codex is the operator for the guided route; signing into Finite does not connect it automatically. The demo stores its plan in the current browser.

Open Finite Continue with ChatGPT

Current scope. Finite organises and revises plans. It does not make bookings, purchases or payments.