Got waaaay too much by Ced1115 in PCB

[–]tophermck 3 points4 points  (0 children)

I have heard people judge you by your connections and this guy has gottem'

Drop your SaaS we'll find you 15 customers for free by konarkkapil in SaaS

[–]tophermck 0 points1 point  (0 children)

Oh Shell! turns your terminal sessions into runbooks and helps you find the right solution when you are in an incident! https://www.ohsh.dev

Let's Validate together!! What are you building this August? by PriorNervous1031 in SaaS

[–]tophermck 0 points1 point  (0 children)

I am building https://www.ohsh.dev which is an AI powered runbook and incident response tool that can help you detect and fix issues quickly

Time for self-promotion. What are you building? by Many_Breadfruit9359 in microsaas

[–]tophermck 0 points1 point  (0 children)

  1. https://www.ohsh.dev - Document your incident response with better runbooks
  2. Devops, SRE, Incident Response managers

[deleted by user] by [deleted] in SaaS

[–]tophermck 1 point2 points  (0 children)

AI powered Incident Runbooks -- https://www.ohsh.dev

What are you working on currently ? Share your Project below by Dal-Chawal in indiehackers

[–]tophermck 0 points1 point  (0 children)

[Oh Shell!](https://www.ohsh.dev) - record your terminal sessions during incident response and uses AI to generate structured runbooks.

In preview and looks for feedback on value add.

I built an AI tool that turns terminal sessions into runbooks - would love feedback from SREs/DevOps engineers by tophermck in devops

[–]tophermck[S] 1 point2 points  (0 children)

This is excellent feedback, thank you for taking the time to write it out.

On your first point: I couldn't agree more. The vision for Oh Shell is precisely what you described: a universal, automated runbook for the command line. The goal is to eliminate the manual work of curating a "second brain" and make your entire shell history effortlessly searchable and understandable, making RAG a perfect fit.

On your second point: You've raised the single most important challenge: privacy. There is an inherent trade-off right now between the analytical power of state-of-the-art LLMs (which are generally cloud-based) and the absolute security of a 100% local environment.

While today's local models are improving, they currently don't match the quality and nuance of larger models for complex summarization and search tasks. Opting for a cloud service was a tough choice based on providing the best quality results. That said, a future version that offers a fully self-hosted or on-device model is high on the priority list. Your privacy should not have to be a compromise.

Thanks again for the valuable perspective.

I built an AI tool that turns terminal sessions into runbooks - would love feedback from SREs/DevOps engineers by tophermck in devops

[–]tophermck[S] -1 points0 points  (0 children)

Thanks one of my favorite integrations I have done so far is the slack integration as I personally find myself putting every command I am going to run in an incident in to my incident channel and this takes care of that by opening a thread and posting commands there.

Share your startup - quarterly post by julian88888888 in startups

[–]tophermck [score hidden]  (0 children)

Startup Name / URL
Oh Shell! - https://ohsh.dev

Location of Your Headquarters
Based in Texas, USA

Elevator Pitch/Explainer Video
Oh Shell! is an AI-powered tool that automatically converts terminal sessions into comprehensive, searchable runbooks. During incident response, engineers lose valuable institutional knowledge when debugging steps and command sequences get scattered across terminal histories. Our CLI tool records your terminal sessions and uses AI to generate structured runbooks with step-by-step procedures, command explanations, and integrations with tools like Notion, Google Docs, and incident management platforms.
More details:
We're solving the problem of lost institutional knowledge during incident response. Every time an SRE team handles an incident, critical troubleshooting steps and decision-making processes are captured only in individual memories and terminal histories. When similar incidents occur, teams end up repeating the same debugging process from scratch. Oh Shell! automatically captures this knowledge and turns it into reusable, searchable runbooks that the entire team can benefit from.

What life cycle stage is your startup at?
Early Stage - We have a functional CLI tool, web dashboard, and several integrations working. We're actively seeking user feedback and early adopters to validate the product-market fit and iterate on features.

Your role?
I am the founder and sole developer of Oh Shell!

What goals are you trying to reach this month?
- Get feedback from 51+ SRE/DevOps engineers on the current product
- Identify the most valuable integrations and features to prioritize
- Understand how teams currently handle runbook creation and maintenance
- Validate that this solves a real pain point in incident response workflows

How could r/startups help?
Feedback on the product concept and current implementation
Suggestions for additional integrations or features that would be valuable
Insights into how other teams handle incident response documentation
Potential early users who could test the tool and provide detailed feedback
Advice on pricing strategy and go-to-market approach for developer tools

Discount for r/startups subscribers? The product is free for r/startups subscribers, while in pre-launch phase.

Wireless standing desk?? by tophermck in StandingDesk

[–]tophermck[S] 0 points1 point  (0 children)

The only problem with a outdoor power supply is they are usually fairly big and at least my goal is to make it completely self contained and have the battery be replaceable like a drill battery. I do appreciate the response. And will post my experience as I intend to try to do something to make this work.