"
Omg !
I started using Qordinate !
And it’s incredible.. I have been on search for something like this from the time ChatGPT came out with tasks feature..
I am making it a lifeOS and it’s incredible . Thank you bro !
"
This is the kind of thing which keeps me moving @qordinate_ai
Glad to make difference one step at a time.
@nikunj i actually did something similar but i made chrome extension, which would scroll and capture things and output in structured format
doing this for X, reddit, and linkedin
and a UI on top
right now using this to monitor web for my ICP and related discussions
@bensen@Microsoft@openclaw if always-on means agents constantly scanning inbox/calendar, that gets expensive and noisy fast. better shape imo is intent-based triggers: tell the system what the agent cares about, let a small event layer watch M365, and wake the agent only on matches.
@alphabatcher i'd also split level 4 into cron vs wake rules: weekly reports can stay scheduled, but inbox scans / backup issues should probably wake only on a real match, with proof the agent actually ran. otherwise one VPS becomes five agents politely hallucinating uptime lol
wild numbers. one thing i'd love to see in the architecture post: how much of Slash is human-pulled through Slack tags vs system-pushed from events like PR opened, alert fired, ticket created, deploy shipped?
feels like that trigger/filter layer is where a lot of the reliability + inference cost tradeoff lives.
@andrewchen Building Watchline: an event layer for proactive agents. Developers or Agents define "watches" over any source, and we find signal from noise without expensive LLM polling.
About me: AI infra eng, 4.5y workflow/agents platforms; OpenAI Hackathon 3rd, ICLR’26 KG retrieval.
@adrielyong@speedrun I built a personal assistant and hit the same wall while making it proactive: when should it wake up, and how do you avoid burning tokens on every event?
Now I'm building the infra layer that lets agents subscribe to what they care about and receive only the events that matter.
@snowmaker While applying to YC, I reached out to many alums for helping with a review of our application
Many of them went out of their way to help even when they didn't have any reason to.
Thanks @Andydy42 , @dexhorthy, and all others.
I've a genuine question: for codex desktop app, does it go through proper testing before releasing updates?
After every update something seems unusable/broken from before.
for eg: in latest build, the right scrollbar is not scrollable because of the branch details pop up taking over.
before, the popup from + icon in command bar didn't come up unless you are at some level of zoom.
I love codex, but these issues make using the app very hard tbh.
Best part about applying to @ycombinator ?
It forces you to introspect, and articulate in simplest words what you are doing, why you are doing it, and for whom?
This is the skill you anyways need to master as a founder to hire, and to sell your thing.
@lifeof_jer stop blaming others just because you fucked up. if you don't know what kind of tokens to keep and give access to, don't blame cursor or railway for your mistakes