One example, three parts

Fictional example, matching the concept on the home page.

  1. The source application

    A task app, here called Sample Tasks, holds a project called Spring newsletter. Its screen is busy: sidebars, toolbars, eight columns. It stays exactly as it is, and it remains the place where the data really lives.

  2. The integration (adapter)

    An adapter for Sample Tasks describes what Roscelin may do there: read the tasks in the open project, change a task’s title, status or priority, create a task. Anything not listed, such as deleting, is unavailable. Access is granted by you, for that app only.

  3. The surface

    Roscelin shows the one task you are working on, its next step and the two controls you need. Every item says where it came from and when it was read. If you want the full table, you switch to a detailed layout; the task is the same.

Planning reads. Checked controls act.

The part that proposes a layout is kept apart from the part that changes anything. A layout can only be assembled from components Roscelin already trusts, and a control can only call actions the integration supports.

Your surface

What you see, approve and can undo. Each item shows where it came from.

a layout built from trusted components

only the action you approved

Planning

Proposes a layout using only trusted components and actions the integration supports. It cannot invent an action or run code of its own.

Today fixed, deterministic layouts

Planned model-assisted proposals

Trusted controls and checks

Sends the approved action through the app’s supported route, then reads the app again. A result it cannot confirm is reported as unknown, not as done.

capabilities and current state

supported action read back

Original app

The source of truth. It stays as it is and stays available to you.

How Roscelin is designed to work. The planning side reads; only the checked control side acts.

Generative UI here does not mean that model-written code runs on your computer. The intended model role is to choose and arrange trusted components; it does not get new permissions.

What personalization changes

  • Which information you see, and how much of it
  • Layout, density, text size and contrast
  • Which controls are close at hand, and their wording
  • Whether a task is shown at once or as guided steps

What it does not change

  • The data inside your apps, unless you approve an action
  • What an app allows. Unsupported actions stay unavailable
  • Your access to the original app
  • The app’s own permissions and rules

Saved preferences and task layouts are different things

A saved preference

Something about you that holds across tasks: larger text, compact rows, keyboard-first controls, plain wording. It is stored as your profile and contains no app content. In the prototype it is local to your browser.

A task layout

An arrangement for the job in front of you, built from your preferences and the app’s capabilities. A new layout is shown as a preview; you accept it or keep what you have, and you can undo it. In the prototype these layouts are fixed; generated layouts are planned.

Why every action needs real support and a check

Changing an app on someone’s behalf is only useful if it is reliable. So an action is something an integration explicitly supports, and success means the app was read again and shows the intended result.

  1. Propose

    You choose a change on your surface, such as marking a task done.

  2. Review

    You see what will change, in which app and item, and what stays the same.

  3. Approve

    Riskier actions, such as creating something new, need an explicit approval.

  4. Send

    The change goes through the app’s own supported route. Nothing else is attempted.

  5. Read back

    Roscelin reads the app again and compares the result with what was intended.

  6. Report

    Verified, refused or unknown. An unconfirmed result is never shown as done, and is never silently re-sent.

Where it runs

Browser first. The starting point is an extension for Chromium-based browsers that works with web apps through tested integrations.

Desktop later, separately. Native desktop applications would need a separate companion program and their own tested support. That companion, planned for Windows first, has not been started.

Not universal. Each app is supported only once its integration is built and tested.

Current limitations

As of .

  • Not available to the public. The prototype is a development build.
  • One third-party app tested: Vikunja v2.8.0, run locally with synthetic data.
  • Layouts are fixed. No layout is generated by a model yet.
  • Chromium only. No other browsers, no macOS, no desktop apps.
  • Same-field race. With Vikunja, a change another client makes to the same field in the few milliseconds between Roscelin’s check and its write can be overwritten. The app offers no conditional write, so this is documented and treated as unsupported.
  • Setup is fiddly. Creating a correctly scoped access token in the tested app is error-prone, and the prototype cannot see a token’s scopes.
  • Not yet checked: a screen-reader pass of the prototype, and a broad task benchmark.

Questions

Is this a new browser?
No. Roscelin starts as an extension for Chromium-based browsers. You keep using the browser and the apps you already have.
Does it replace my apps?
No. Your apps remain the source of truth. Roscelin is designed to sit alongside them as a different surface, and the original app is always one step away.
Is it only for accessibility?
No. It is for anyone who wants their tools to fit the way they work: simpler on some days, more detailed on others. Accessible interaction is built in rather than treated as a separate mode.
Does it work with every app?
No. Each app needs an integration, and each integration needs its own tests before it counts as supported. Today one third-party app, Vikunja, has been tested in the prototype. Broad support is a direction, not a promise.
Is it available now?
No. Roscelin is in development. There is no public download, account or waitlist yet. The project status page lists what exists and what does not.
Does the demonstration connect to my accounts?
No. The concept on this website uses fictional sample data, makes no network requests and stores nothing.
Separately, the development prototype does connect to a real app: it has been tested against a locally run copy of Vikunja with synthetic data. That prototype is not part of this website and is not publicly available.