The console

Each Cahut has a web console, under /console/ of its domain: https://cahut.example.com/console/. The root of the domain, https://cahut.example.com/, and /admin lead there too: the console opens on its overview once you have signed in, and on its page of sign-in until then. People sign in there, see their Rooms and Windows, connect their AIs and read the Logbook; administrators manage people, Rooms and the server. The console uses the same API as the AIs, and nothing else.

Port 443 keeps the Windows and MCP. Some company networks let only port 443 out: from there, the console is out of reach, the Windows are not.

The first person of a Cahut starts from the link that the installation prints, at /console/setup#...: see The first start. After them, nobody chooses a password for someone else. An administrator creates the account, and Cahut gives a link that works once, for 7 days:

https://cahut.example.com/console/activate#...

The person opens it, chooses a password of 15 characters at least, and is signed in. The code of the link stays in the browser: it never reaches the server’s logs, and the console takes it out of the address once read.

An administrator creates accounts in the console, under People, or on the command line with cahut user create. When the Cahut sends e-mail and the person has an address, the link goes there too. In a Cahut that sends e-mail, a person who forgot their password asks for a link from Forgot your password?, on the page of sign-in: it goes to the address of their account and works for one hour. Without an address, or without e-mail, an administrator gives a new link: Manage, then Give a new link, in People, or cahut user link. The password works until the new link is used, and using it ends the other sessions.

What a person finds

Screen	What it shows
Overview	The latest Windows of your Rooms, each with a preview, your Rooms, and the limits of the Cahut, or yours in an individual Cahut, when there are some
Knocks	What your AIs asked that waits for you, with Approve and Decline, then what you answered and what expired; the navigation counts those that wait
A Knock	Where the link of an AI leads: what it asks, the details of the call, when it expires, Approve and Decline, then what the call gave back
A Room	Its address, ready to copy, and what it shows; its Windows, each with a preview and its access, the one its address shows marked, and its trash folded under them, where a Window comes back with Restore; the people of a team Room. Owners add a person with Add a person and change their role or remove them with Manage; Manage the Room chooses what its address shows, its Windows or one of them, renames a team Room, leaves it, and deletes it for good once its name is typed
A Window	Where it opens; its access, its end date and its Key, which shows once, next to the address, ready to copy; its two versions, with a button that goes back; what its AI declared it does; the trash, and deleting it for good from there
Rooms	A new team Room, of which you become the owner
Logbook	What you did, what your AIs did, and what happened in your Rooms, by day, with filters
AIs and access	The address to give an AI client; your connected AIs, with what they may do and where, Change and Disconnect; your personal tokens: create one, shown once with the command that connects Claude Code, and revoke it in one click
Account	At the foot of the navigation, and behind your name in the top bar: your name and your handle; your e-mail address and notices, when the Cahut sends e-mail; the language of the console; a new password, and signing out

A change to what someone may do, such as adding a person to a Room, making a Window public, and deleting anything for good, ask you to confirm first. When your AI asks for one of these changes, it knocks first: the change waits for you under Knocks. See Knock first.

What an administrator of the Cahut finds

The same screens, and:

People: everyone in the Cahut, with their role and state, and their e-mail address when the Cahut sends e-mail. New person adds someone and gives their link. Manage opens what can change for a person, each with what it does: their e-mail address, making them an administrator or a member, a new link, disabling and enabling. A change of role and disabling ask to confirm first. A disabled person cannot sign in, and their AIs stop at once.
Rooms: every Room of the Cahut, whose people they manage. They open the Windows of the Rooms they are in only.
Logbook: every entry of the Cahut, from people and from AIs.
AIs and access: the connected AIs and the tokens of others too, which they can disconnect and revoke.
House style: see below.
Kind and limits: whether the Cahut is collaborative or individual, its limits with what it holds, and the links to its legal pages. The administrators of the server set them.

In an individual Cahut, the page of a Room no longer adds or removes people, and the access of a Window no longer offers Internal.

House style

The administrators set the house style of the Cahut here: the name of the organization, its logo and its version for dark backgrounds, its four colors with their contrasts, the colors of its charts, its fonts and their files, and its guidance for AIs. The switch AIs use this house style makes it inactive for AIs, for an organization that gives them guidelines of its own. A preview shows the form in its colors and fonts before saving, and the three templates open in the house style that is saved. Go back to it restores the previous version, and Back to neutral starts again from the neutral house style, both after a confirmation.

The AIs and access screen of every person gives the commands that install the Cahut plugin in Claude Code, and the skill as a zip for the Claude apps.

Administrators of the server

The administrators of the server have accounts of their own, apart from the people of the Cahuts: see Administrators of the server. They sign in at /console/server/sign-in of any Cahut, which its sign-in page does not link, so that the people of the Cahut are not shown the way to the server. Their first link opens at /console/server/activate#....

A person who also administers the server holds both accounts in the same browser. Sign in to the server, on the Account page of a Cahut administrator, keeps the session of the person, and the pages of the server join their console under This server. The pages of the Cahut act as the person, but for its kind, its limits and its legal pages, which act as the administrator of the server. An administrator of the server who signs in alone finds Sign in as a person in the top bar and on their Account page.

While the browser holds the session of an administrator of the server, the bar of the server sits above the top bar, on every page. It says Server administration, names the Cahut of the domain and the administrator, and holds Sign out of the server. The name of the Cahut opens the list of the Cahuts of the server: another one opens at its own console, where you sign in to the server again. The top bar below is that of the Cahut, and says who acts in it: the person, with Sign out, or, without one, the administrator of the server. Each bar signs out of its own session, and the console stays open with the other one.

They find:

Overview, or Cahuts beside the console of a person: the Cahuts of the server, a form that declares one with its first administrator, whose link the console shows, and on each Cahut Move to a domain or Change its domain. When the Cahut of the console moves, the console sends you to sign in again at its new address.
Server administrators: the list, with the day each was added and their state. New administrator adds one and gives their link. Manage changes the name of an administrator, theirs or one’s own, gives another administrator a new link, or disables and enables them; disabling asks to confirm first. A disabled administrator loses their sessions and cannot sign in; the server keeps at least one who is not disabled. The screen reminds that an administrator of one Cahut only is made under People.
Logbook of the server: the Cahuts declared and moved, the administrators and their sign-ins, and the updates.
Updates: the version running, the newest release, the last update and how it ended, with Check now and Update. See Updates.
In the Cahut of the domain where they signed in, People, Rooms and its Logbook, as its administrators have them, without its Windows.
Kind and limits, where they make the Cahut collaborative or individual and set its limits: a field left empty lifts a limit, and the disk counts in gigabytes of a billion bytes. Under Legal pages, they give the addresses of its legal notice, terms, privacy policy and support, each with another address in French where the page in French differs; a field left empty removes its link. Each change goes to the Logbook of the Cahut.

A session holds at the domain where it opened: to look after another Cahut, sign in at its own console.

Sessions

A session ends 7 days after its last use, and 30 days after it opened in any case. The console keeps it in the storage of its own address and sends it with every call; it sets no cookie. A browser holds at most two sessions at a Cahut, that of a person and that of an administrator of the server, and a session that ends asks to sign in again with its own account. Signing out also ends the reader sessions that the console opened in that browser, and Sign out on the pages of the Cahut ends the session of the console that opened them.

After 10 refused sign-ins to one handle from one address in 15 minutes, that address must wait; after 100 from everywhere, the handle waits everywhere. An address that tries too often must wait too, and an IPv6 address counts with its whole /64. The Logbook keeps the address of every sign-in.

On a Knock, Approve and, on the consent screen of an AI, Connect become active once the page has been in front for a moment and you have moved the pointer or pressed a key: a page that would slip them under a double-click gets nowhere.

Name and handle

Anyone changes their name and their handle under Account. Their personal Room takes the new name as its title, unless they gave it another one.

A new handle must be free, held by no person and no Room. It becomes the name of the personal Room and, in an individual Cahut, the start of the name of each Room of the person, such as bob-projects: the addresses of their Windows change, and the old ones stop working, the links already given out included. The old handle is free for someone else. The console shows the old and the new addresses, and asks again before the change. Answer the Knocks that wait for you first, since they name the old addresses. Your sessions, tokens and connected AIs go on as before, and you sign in with the new handle.

Language

The console speaks English and French. It follows the languages of the browser, and anyone can choose one at the foot of the navigation, on every page, under Account, or under the card of the page of sign-in: the choice stays in that browser, for that Cahut. The words of the house, such as Room, Window and Knock, stay in English, and so do the Logbook, e-mail and most messages of the server. The refusals that people meet most, such as a wrong password, a link that expired, a session that ended, a handle or a name of a Room already taken, a Key too short or an invitation that cannot go, come in the language of the console.

Readers

To open a Window that is not public, a reader signs in through the console: the link on the page of a closed Window sends them to /console/read, which signs them in if needed, then sends them back to the Window. See Who can open a Window.

When an AI client connects with OAuth, it sends you to /console/oauth/authorize. You sign in there if you need to, and choose what the AI may do and in which Rooms. See Connect an AI client.