DevelopmentAutomation
Cody
Cody handles account and welcome tasks by email. Hermes supplies the underlying agent software. I adapted it to the systems I work with and built the email and account integration, the permissions around its actions and the way it talks.
Reading a real email thread
Email is where people already look for an invitation or ask about access, so a small request doesn't need another application. The messages themselves are messy, though. People refer to earlier conversations, leave out the account name and reply on top of long quoted trails. Cody has to connect the current question to the parts of the thread that actually belong to it.
I worked on short, relaxed replies: name the missing detail, say when an action is done and give the person the next step. Someone trying to get into an account shouldn't have to read a technical explanation first.
The sender has to match the account
Behind the easygoing tone are checks on the sender and the account involved. Each request is tied to the person entitled to make it, and Cody handles an account task only where that task is allowed.
A welcome that arrives once
One of Cody's jobs is welcoming someone after a successful Nextcloud sign-in. Creating an account and actually entering it are different moments, and the welcome belongs to the second one.
Authenticated self-service requests follow a separate path once the account setup is ready. Cody keeps those situations apart and remembers which welcome it has already handled, so refreshing a page or checking the account doesn't produce another copy.
I built the custom email and account integration around Hermes and shaped how Cody communicates.










