News for hackers. Stuff that matters.

Gobhanu

how do you track where users are coming from?
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Wednesday March 11, 2026 @02:35AM (#47332310)
Thank you Nick!
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @07:17PM (#47269068)
funnily enough I was actually speaking to one of the founders of x.ai recently

I think they paved the way for a lot of the implementation we do today along with the model providers. That being said we are trying to do scheduling a degree greater of complexity.

Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @04:08PM (#47267317)
out of curiosity how were you planning on using it?
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @04:05PM (#47267292)
Fair feedback that the case studies don't show this well - they're simplified to demonstrate the flow. The multi-party dependency resolution is happening underneath but we could surface that better.

On the LLM point - agreed that context window alone doesn't cut it. The coordination and state management layer sits outside the model. We learned that the hard way early on.

Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @04:05PM (#47267288)
The concurrent resolution problem you're describing is exactly what we deal with. When a staffing coordinator has 15 interviews to book across shared interviewers, confirming one cascades into others. We track pending holds, rank by urgency, and when a confirmation on one thread invalidates a proposal on another, Vela detects the conflict and re-proposes. Theres

The only other alternative is a booking link but this, slows down business, doesnt work in many many real life situations and more :)

Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @04:03PM (#47267265)
open claw breaks so often with scheduling... given the number of things that need to be considered to get it right

We do not have a skill if thats what you meant?

Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @04:01PM (#47267237)
but there are a bunch of b2c options :)
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @04:01PM (#47267233)
we are b2b focused unfortunately
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @03:59PM (#47267203)
I like the name... very UK "ting." Would love to chat one sunday in April and see if there are learnings - feel free to use Meet-Ting to help get something on the calendar :)
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @03:57PM (#47267173)
if you dont mind me asking what makes the appointments hard to fill? as I understand it the demand far outweighs the supply?
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @01:37PM (#47265393)
very fair callout - and I can see how "scheduling solved" reads very differently to someone coming from the optimization/planning side of AI. You are right.

Appreciate the note on the slogan, definetly thinking of revamping our landing page in the near future to speak more directly to our audience.

Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @01:25PM (#47265257)
wow what a wonderful coincidence
Re:Launch HN: Vela (YC W26) – AI for complex scheduling on Thursday March 05, 2026 @01:24PM (#47265242)
Thank you for the advice - really appreciate it.

Was actually chatting with a large industrial staffing firm and they were saying the same thing that it was super painful to schedule 1000s of workers for drug tests and then shifts too!

Launch HN: Vela (YC W26) – AI for complex scheduling

Hi HN! We're Gobhanu and Saatvik (brothers), building Vela (https://tryvela.ai) - AI agents that handle multi-party, multi-channel scheduling.Scheduling is a constraint satisfaction problem disguised as email! It’s easy when it’s two people, one timezone, one channel. But it becomes a constraint satisfaction problem when inputs are unstructured natural language across multiple communication...

( Read More... | 46 comments | 28 points | on HN )