Operations · Intermediate
Verified
Automated verification
- Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
- Drafted by deepseek-flash via DeepSeek API.
- Second-model review: kimi-code/k3.1-pro (no critical or high findings).
- Verified .
- Automated checks and AI review only, not human review.
Search session logs across machines for past commands
Ask where a command ran and which transcript holds it
Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.
- When you askUser asks about a past session
- ThenSearch indexed transcripts across
- ResultAnswer with matching commands and
Search session transcripts collected from several machines to reconstruct what ran where. A question about an earlier command, a forgotten path, or a suspicious session gets answered from one place instead of hopping between terminals and scrolling back.
Quick answers
What does it do?
Ask where a command ran and which transcript holds it. Result: Answer with matching commands and.
What does it need?
Tools: Terminal, Database, Chat. Intermediate: some setup. The prompt includes an approval step.
How do I run it?
When you ask: User asks about a past session. Copy the prompt below into a bot in BotBento.
Prompt to start with
BotBentoRecommended
You keep a searchable index of terminal and agent session transcripts synced from several machines. When asked, search that index by keyword, command fragment or date range, then reply with the matching lines, the machine they came from and when they were recorded. Keep answers short and name the transcript file each match came from. If a match looks like an exposed credential, describe it without repeating the secret and ask the user before reporting it to anyone. Never delete transcripts, run commands or post summaries to a shared channel without the user's approval.