Veb.Release status

Seven starting points. More to come.

The page asks.
You get the tools.

Whatever the web asks you to do, your browser should give you the right controls to do it. Try these examples. Change something and see what follows.

application / make this doable

The instructions become the interface.

Turn file limits into preparation tools, count words, match dates, and fill templates only with details you supply. PDF compression and conversion belong in that same workspace; this preview demonstrates the checks with local and sample files.

Application, made doable

5 small things to resolve.

Applicationapplication.pdf · 6.20 MB · sample
Over 5 MB
Proof of addressOne PDF · up to 5 MB
PortfolioOne PDF · up to 5 MB
36 / 250 words
Named template Add your name

Application for [your name] · 2026-11-01

This preview uses only the name and date you enter.
1 of 6 requirements ready for review.

Sizes and word counts are exact. Local files are checked for a PDF header, not full document validity. Sample controls don’t compress or upload files.

Interactive preview · sample dataYours to try. Nothing is submitted.
Katchy × Veb · proposed connection

Start in a tab.
Give an agent the next step.

Veb could turn the page into a useful workspace. A Katchy agent could take the selected context further—research a choice, prepare a coding task, or keep a follow-up with the conversation.

Veb → Katchy → back to your taskLocal simulation
Start with two tabs in Veb

Find a room for the workshop.

Choose the pages and set the brief. The sample pages below are fictional.

The proposed agent handoff

A research agent follows the sources.

  1. Read only the venue pages you selected.
  2. Compare capacity, day hire, and access against your brief.
  3. Return a shortlist and the facts still worth checking.

Look over the information and the work you want the agent to do.

Interactive examples with sample data. No Katchy account is connected and no agent request is sent.

The Veb connection is a proposal. We’re also considering how it could fit Katchy subscriptions; access, pricing, and timing aren’t decided. Read the launch note →

Different work needs different controls.

A form needs a word counter. A purchase needs compatibility checks. A complaint needs evidence that stays attached to the claim. The point is to give you something useful to work with, right where the task is.

We’re exploring reasoning for the difficult calls, fast extraction for the routine ones, generated visuals when they help, and voice when you choose it. File limits, dates, counters and compatibility rules still need exact checks.

These examples use local sample data. The desktop browser is an early hackathon prototype. Read about free testing and what comes next →