agybay_07

its great that you're interested in this topic, good luck)

Thank you. What do you mean by 'citations'? Each item has a 'Stroq show' feature that displays the basis for it

Everything is performed programmatically, without using a model

Thanks, the owl's name is Hoo) Stroq reads sessions logs and command text directly from the computer. There are no LLM models involved

Yes, the rules dont catch everything but since this is an open-source project, anyone can add new rules, and I'll be looking for new approaches. as for the llm, it reads the same text as the agent, so it can be fooled as well)

oh no, I hadn't made that connection until now lol

Yes, that’s correct. the rules already flag this kind of text

yes

to be honest, in the first scenario, the hook will only detect 'nom test' command itself. in the second scenario 'stroq inspect' will identify the hook before the folder is opened and issue a warning. thanks for these examples :) I'll use them to improve product

You’re right the command from my comment only generates a report and doesn’t actually prevent anything. stroq init sets up hooks that prompt for confirmation before a dangerous command is executed—but that’s a filter, not a sandbox

Thanks) good idea

I've built project that helps to protect your computer from dangerous commands that your ai agent might execute. Have you noticed how often dont even check what our agents are actually running? Thats why I created Stroq. Try it locally npx @stroq/cli

find sessions for secrets

would love to your feedback :)

I read through the Privacy Policy and noticed that the text of an article can be sent to an external AI service. Just wondering, will there be some kind of preview or confirmation before the content is actually sent? I’m particularly curious about this for internal or private pages, since those might contain information that shouldn’t be shared externall