NIELLO Dex / Developer Empowered Experience

Every agent you already use.
One place to run them well.

One place for developers to run, govern and hand off work across the coding agents they already use — such as Claude Code, Codex and Gemini CLI — in a terminal-first workspace.

Explore Dex
n/DEX / WORKSPACEILLUSTRATIVE VIEW
DEVELOPER EMPOWERED EXPERIENCE

Every agent you already use.

$ dex doctor
  ok    harness registry  2 can host a governed session
                          (claude, codex)
  FAIL  harness gemini    no hook installer — a session
                          here would run uninstrumented
        fix: use a governable harness, or `start --force`
             to run this one uninstrumented
CONNECTED THROUGH NIELLO HUMAN CONTROL, BUILT IN

THE AGENT WORKBENCH

Every agent you use. One governed place.

Pick a session, see what the gate allows, refuses or holds, and continue the work with another agent.

NIELLO DEXINTERACTIVE ILLUSTRATION / SELECT TO EXPLORE
ILLUSTRATIVE WALKTHROUGH

A scripted rendition of the Dex app with example data. Nothing here runs an agent, calls a model or enforces a policy.

Implemented

01 / Check the machine first. dex doctor finds the agents installed here, says which can run governed and prints the fix for every gap.

Dex/Terminal/zshSearch sessions, blocks, code, receipts…⌘K
Filter…
SESSIONS+ new
acme / storefront

main

No agent sessions yet.

zsh
zsh~/acme/storefrontplain terminal

~/acme/storefront $ dex doctor

dex — boundary report

okdex binary~/.local/bin/dex
okharness registry2/3 harnesses can host a governed session (claude, codex)
oksession daemonanswering · 0 live sessions
okcontrol plane0 live sessions, remote control not armed
FAILharness geminino hook installer for this harness — a session here would run uninstrumentedfix: not supported yet — use a governable harness, or `start --force` to run this one uninstrumented

1 check needs attention (see fix: lines above).

~/acme/storefront $

session daemon connected0 sessionsacme/storefront · main
SESSION INSPECTOR / SELECT TO EXPLORE

Choose an agent to see how Dex treats its session.

AGENTS ON THIS MACHINE
CONTINUE WITH
DEX / CLAUDE CODE SESSIONGOVERNED
  • Read src/checkout/rate_limit.tsAllowed
  • Edit the gate configurationRefusedAn agent cannot edit its own gate.
  • Push to a remoteHeldWaiting for a person to approve.
CONTINUE WITH

Claude Code → Codex

The conversation and its lineage travel with the work.

Developer Empowered ExperienceExample content and controls. Your workflow is shaped during discovery.

MADE TO MOVE YOU FORWARD

A clearer purpose.
A more powerful possibility.

01

Every agent, in one place

See the agents and sessions on a machine, start them from one workspace and check their health with a single doctor command that names every fix.

02

Governed, and honest about it

A deterministic policy gate runs before tools execute and fails closed. An agent cannot edit its own gate, and a session is never shown as governed when it is not.

03

Continue with another agent

Continue a Claude Code session in Codex or Gemini CLI with its conversation and lineage intact, and keep a receipt of what changed in each pull request.

WORKFLOWS & OPERATIONSTHE NIELLO FILM COLLECTION

THE VALUE IS IN THE CONNECTION

Less between intention and action.

Connect the handoffs that keep important work waiting.

Explore the story ↗

HOW THE WORK MOVES

From intent to outcome.

01 /

Find your agents

02 /

Run inside the gate

03 /

Hand off with context

04 /

Review the receipts

A LITTLE MORE CLARITY

Good questions.
Clear answers.

How do we begin with Dex?

Bring a concrete use case to a discovery conversation. We will map how Dex fits the workflow, confirm the systems and access it needs, and agree on what a useful pilot should demonstrate.

Can we keep our existing systems?

The platform is designed to work with your systems and chosen model providers. Connector availability, infrastructure boundaries and data requirements are confirmed when scoping your deployment.

How is availability confirmed?

The site describes the Niello product direction. Specific features, integrations, deployment options and commercial terms are confirmed with your team before an engagement begins.