← All journal entries

Running an assistant · Tested in August 2026

Running two assistants on one Raspberry Pi

I rebuilt Neebs and Spud on a Raspberry Pi, then tested Telegram access, file boundaries and approval before sending email.

When I rebuilt the Raspberry Pi setup in August, I gave Neebs and Spud separate places to run and separate access to their files. Neebs is my personal assistant. Spud helps with OPL administration; it does not create our music.

The checks included real Telegram conversations and inspecting the access each assistant actually had. One early Spud reply described broader access than its configuration allowed. I corrected its instructions and tried again. The next test described the intended limits properly.

I also tested the email route for Neebs. It could prepare a draft, but sending required approval of that exact version. A test using an unrecognised identity was rejected, and a harmless attachment test worked. No email was sent during those checks.

That was useful experience. An assistant can sound confident about its abilities, so I wanted the behaviour and the underlying access to agree. I kept the August test record so I could return to what had actually been checked.

26–27 August 2026

What came out of it

Telegram access was tested; a misleading assistant capability description was corrected and retested; draft/attachment tests worked and an unrecognised identity was rejected.