Hiding something is not the same as stopping it
When you remove a project from Styx's sidebar, nothing is deleted. Your files stay where they are, and the tasks, chat history and targets are kept out of sight in case you add the folder again. The thing I didn't want
When you remove a project from Styx's sidebar, nothing is deleted. Your files stay where they are, and the tasks, chat history and targets are kept out of sight in case you add the folder again.
The thing I didn't want to leave behind was access. A project that's gone from the sidebar can still have an agent running in it, or a grant open on a deploy target, and you'd have no screen left to notice either. So before the project goes, Styx stops its agents and closes every grant on its targets.
It's the same idea as the rest of the grant lifetime. Left alone, a grant ends when its time is up, after an hour without use, or when the task ends, whichever comes first. Each of those is an event that already exists, so access never depends on someone remembering to switch it off.
The lesson I keep applying: tie a permission to something that will end, such as a clock, a task or a project, instead of to a person's attention.
When it doesn't apply: a grant you deliberately make persistent. That's on purpose, but it's the one kind you do have to go and look at.
I'm building Styx, where this came from.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes โ full credit and traffic to the original publisher.