Book a Demo Talk to Sales

Whitepaper · Admin assistant

Working with Sudo

Sudo is the admin assistant in Curiosity Studio. This guide is for the people who hand Sudo real changes. It covers what to ask, what happens to a request, how to review the diff and how to teach the assistant.

Download the PDFAll Whitepapers

For Studio administrators and developers Chapters 6, and a glossary Pages 22 Date October 2026

What it covers

Ask for the outcome. Approve the diff.

Sudo changes your configuration the way a developer would: as files, in a separate sandbox, ending in a diff. Say the outcome you want and let Sudo choose the surfaces. Then read the staged diff and approve one idea at a time.

  1. Step 01

    Read

    Your files

  2. Step 02

    Edit

    sed, a heredoc

  3. Step 03

    Build

    Compile it

  4. Step 04

    Commit

    Stage and stop

  5. Step 05

    You review

    Then approve

  6. Step 06

    Applied

    One tracked commit

Chapters

Six chapters, from the dock to the skill

01 · Page 03All six

Sudo works beside your workspace

The admin dock, full screen, and what Sudo sees of your screen.

02 · Page 06Read

Questions change nothing

What Sudo reads to answer, and why reading is safe.

03 · Page 09Edit · Build · Commit

Every change ends in a diff

Say the outcome; Sudo picks the surfaces and builds one commit.

04 · Page 12Review · Applied

Reviewing is reading the diff

What to read, which button to press, what approving does.

05 · Page 15Applied

Running things is a request too

Tasks, migrations, reindexes and small settings, watched as they run.

06 · Page 17All six

You teach Sudo with a skill

Sudo’s rules, your conventions, and the habits of a good session.

The full paper

Ask Sudo. Approve what gets built.

Download the PDF

Your data. Your infrastructure.

Connected knowledge for AI systems

Book a Demo Talk to Sales