•
I am always in a flow state now
I used to spend my day navigating tools and tabs. Grafana, Slack, AWS, Snowflake, GitHub, Linear—the list goes on. The work itself wasn't hard. The friction was the work between the work, and that friction constantly broke my flow state.
Now it feels different.
A few days ago, Rajoshi posted on Slack that new users weren't seeing the "Connect Data" button. In the old world, that would've meant a rabbit hole: clone the repo, grep through components, cross-reference with Linear, maybe Slack someone who touched the code last year. Hours of tab-switching before I even understood the problem.
Instead, I dropped the Slack link into PromptQL. And just stayed there.
I asked it to investigate.
Aisura (our remote coding agent connected to PromptQL) cloned the console repo, traced the rendering logic, and built a matrix of every condition that controls when those buttons appear. The root cause became obvious: users were getting redirected to "my threads" because the #general room was being created asynchronously and wasn't ready in time.
I tagged Tanmai. He confirmed the hypothesis and suggested using Postgres triggers. I asked PromptQL to check the backend initialization code. More people joined—Sandeep, Rikin, Karthik—each adding context without anyone having to re-explain what we were looking at. The conversation accumulated context instead of losing it.
PromptQL came up with these recommendations:
And then proceeded to create a PR to implement the selected option.
When the fix was ready, I asked who should review the PR. PromptQL ran git blame on the changed files, identified the original author, and I tagged them right from the thread. They reviewed it. We merged it.
Seven people collaborated. One thread.
I went from 'someone reported a bug' to 'fix is in production' without opening a single other tool."
That's the part that still gets me. There was no break in thought. No moment where I had to stop and figure out how to get the answer. The thread was the workspace, the communication channel, and the solution—all at once.
PromptQL collapsed my tool sprawl into a single conversation. Version deployments, cost analytics, incident analysis, on-call schedules, security compliance checks, customer lookups—it all starts in PromptQL now.
I’ve stopped thinking about how to get answers and started just getting them.
