From GitLab to Kilo Code (Interview)

7 Jan 2026 · 1 h 17 min · 28 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

The Changelog: From GitLab to Kilo Code (Interview) - Episode Summary

Episode Overview In this episode of "The Changelog," hosts Jared Santo and Adam Stacoviak engage in an in-depth conversation with Sid Sijbrandij, founder of GitLab and the newly established Kilo Code. The discussion traverses Sid’s remarkable journey from leading GitLab to its IPO, navigating a cancer diagnosis, and insights into his current ventures.

Key Themes

  • Health Journey: Sid shares his battle with bone cancer, the treatment process, and his ongoing quest for innovative medical solutions.
  • Startup Evolution: Exploring the transition from GitLab’s IPO to founding Kilo Code, an all-in-one coding platform.
  • Agentic Engineering: The capabilities and future scope of Kilo Code, focusing on integration and AI-driven solutions in software development.

Detailed Notes

Introduction

  • Sid returns to discuss his experiences post-GitLab IPO and his health challenges.
  • The conversation begins with reflections on Sid's career and personal life.

GitLab Journey

  • Sid reflects on his time at GitLab, emphasizing:
  • The importance of transparency and remote collaboration.
  • Leading GitLab through its IPO in 2022.
  • Discusses his transition from CEO to Executive Chair at GitLab, while continuing to work on key projects, particularly improving observability.

Health Challenges

  • In late 2022, Sid was diagnosed with bone cancer (osteosarcoma), which led to:
  • Surgical interventions, including the removal of a vertebra and spinal fusion.
  • Treatment involving radiation and chemotherapy.
  • Sid highlights the challenges of navigating cancer treatment:
  • Importance of patient-driven research and diagnostics.
  • Utilization of emerging therapies, including experimental treatments.

Innovations in Cancer Treatment

  • Sid discusses his proactive approach to combating cancer:
  • Development of personal treatment strategies, including multiple therapies.
  • The role of diagnostic technologies and data in personalizing treatment.

Kilo Code

The Next Chapter

  • Kilo Code Overview: An all-in-one agentic engineering platform for software development.
  • Combines features for coding, code reviews, security assessments, and deployment.
  • Agentic Coding:
  • The platform’s unique approach to empower developers with AI-driven tools.
  • Focus on enhancing productivity through parallel processing and agent collaboration.
  • Business Model:
  • Open core strategy, where basic functionalities are free, and advanced features are subscription-based.

Future of Software Development

  • Sid expresses optimism regarding the future of developers with AI integration:
  • Encourages a shift from tedious programming tasks to creative development processes.
  • Advocates for developing software without extensive prior training or formal education.

Closing Thoughts

  • Sid emphasizes the importance of personal resilience and continuous learning.
  • Invites those interested in opportunities at Kilo to explore roles in tech startups, encouraging individual contributions over collaboration constraints.

Key Takeaways

  • Resilience in Adversity: Sid’s journey illustrates the intersection of personal challenges and professional ambition.
  • Innovation in Health: Highlights the potential of technology in advancing medical treatment pathways.
  • Empowerment through AI: Kilo Code exemplifies the future of software development, where AI tools can significantly enhance productivity and creativity.

Conclusion The episode concludes with a positive note on the advancements in technology and the promising future for software developers. Sid’s narrative serves as both an inspiration and a call to action for leveraging technology to overcome challenges, both personal and professional.

---

Reference Links

  • [The Changelog Website](https://changelog.com)
  • [Kilo Code Website](https://kilocode.com)

Acknowledgments

  • Special thanks to the sponsors and the audience for supporting conversations on software development and innovation.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

Sid's Journey from GitLab to KiloCode

3:37 to 9:50

Sid shares his experiences from leading GitLab to dealing with cancer and founding KiloCode.

“The last time we talked to you, the last time I talked to you, at least, was when you were leading GitLab to IPO.”

Innovative Treatment Approaches

9:59 to 13:00

Sid discusses his unique approaches to cancer treatment and the challenges he faced.

“So every time we do, we combine treatments.”

Health Update and Future Outlook

13:03 to 14:10

Sid provides an update on his health and outlines future treatment options.

“And most people die because they, not because they've run out of treatments, they've run out of time.”

Health Update: From Trials to Options

14:10 to 14:51

The speaker shares their current health status and available treatment options.

“So they have a much higher speed of running trials.”

Innovative Cancer Treatments and Technologies

14:52 to 16:52

Discussion on the technology and treatments that made the cancer undetectable.

“and I'm continuing the development of 10 different drugs and diagnostics that make a lot of sense for me to have.”

Radioactive Treatments and Their Effects

16:53 to 19:09

Exploration of the use of radioactive treatments and their impact on tumor removal.

“And this is because it would attack the scar tissue.”

Personal Stories of Sarcoma and Loss

19:10 to 20:48

A personal anecdote about a friend lost to sarcoma and the complexities of cancer.

“But she came to actually get the cancer.”

Understanding Sarcoma and Its Implications

20:49 to 22:42

Discussion on the various types of sarcoma and their genetic complexities.

“It was about a year, maybe a year-ish, devastating to our life and our friends.”

Navigating Cancer Diagnoses and Miscommunication

22:43 to 25:12

Experiences with misdiagnosis and the emotional toll of cancer news.

“and I get a message, a text from my GP, and he says, it's positive, not subtle.”

Current Status and Future Treatment Plans

25:13 to 28:00

The current status of cancer treatment and ongoing plans for managing health.

“And then the exact opposite when you're like, you know what?”
Show all 28 chapters

Immune Response and Treatment Options

28:00 to 30:00

Discussion on T cell infiltration and various treatment options for cancer.

“so that you preserve optionality to run these diagnostics later.”

Reflections on Travel and Health

32:20 to 33:50

Personal reflections on traveling and experiences with health treatments.

“A lot of meetings, mostly the whole day is meetings, 25-minute meetings, like 15 a day.”

Exploring Kilo and Open Source Agentic Coding

33:50 to 35:50

Discussion on the creation of Kilo and its approach to open source coding.

“And what made you want to get into open source agentic coding when you have all this, these medical companies, you've got to get a lot of stuff going on, you want to, but you want to work on this.”

The Competitive Landscape of AI Models

35:50 to 37:30

Analysis of the competitive nature of AI models and their pricing strategies.

“and then we also have an enterprise version with features that appeal to executives like centralized, bring your own keys so they can send it to Bedrock in their VPC.”

User Experience with Multi-Model Approaches

37:30 to 39:30

Discussion on user preferences for different AI models and the flexibility of Kilo.

“Yeah, I think the kind of the leading coding model, that's an incredibly competitive space where kind of the, it always feels a bit like OpenAI is a better model.”

The Rapid Growth and Strategy of Kilo

39:30 to 42:00

Insights into Kilo's rapid development and the team's strategy to compete.

“So it's kind of a mix and match approach.”

The Shift to Parallel Functionality

42:00 to 43:19

Explore how software development has transformed with parallel processing.

“The way I would look at it is it used to be that you needed like a team of seven people to do something.”

Free Models and Market Dynamics

43:20 to 45:55

Discuss the rise of free models in AI and their implications for users.

“Our parallel functionality where you have kind of, you farm it out to multiple agents in multiple work streams.”

Cost Implications of Agent Usage

45:56 to 47:56

Analyze the potential costs associated with using multiple AI agents.

“Maybe this is like when VC money was plentiful and the Ubers were really affordable.”

Integrating AI in Personal and Professional Life

47:57 to 51:15

Learn about the therapeutic and practical applications of AI in daily tasks.

“And we thought this AGI, where AI would be as smart as you, this is a seminal moment.”

The Future of Knowledge Work with AI

51:16 to 56:00

Discover how AI enhances the collaboration of deep thinkers in various fields.

“Like, think about how much stuff I had to learn this year.”

Kilo Code vs. Cursor

59:01 to 1:02:00

Discussing the differences and benefits of Kilo compared to Cursor.

“You mentioned$10 ,000 a month, something like this, you know, with a human and some agents doing their thing in the future.”

Kilo's Functionality and User Experience

1:02:00 to 1:06:27

Exploring how users interact with Kilo and its cloud-based features.

“So you may use a particular model and you're a REST developer.”

The Future of Software Development

1:06:27 to 1:10:00

Insights into the evolution of software development and the role of AI.

“Is that a version of what you're doing with Kilo in the mobile app?”

The Evolution of Programming Mindset

1:10:00 to 1:11:06

Explore how modern tools have transformed the software development experience.

“I read some of the code and I'm like, standard IO?”

The State of Play in Development

1:11:06 to 1:11:51

Learn about the concept of 'state of play' and its relevance in software development.

“And the way I look at it or the way I think about it is like the state of play.”

Balancing Individual Progress with Collaboration

1:11:51 to 1:14:12

Discuss the balance between individual efforts and collaboration in tech.

“For me, a state of flow is where I don't go off and check Hector News and Reddit on the side because I'm getting bored or I have to wait.”

Closing Thoughts on Kilo and Future Opportunities

1:14:12 to 1:14:42

Reflect on the discussion about Kilo and future opportunities for listeners.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:05Welcome to the Change Log, where we have deep technical conversations with the hackers, leaders, and innovators of the software world. I'm Jared Santo. On this episode, Adam and I are joined by Sid Sabrandage, founder of GitLab, who led the all-in-one coding platform all the way to IPO. In late 2022, Sid discovered that he had bone cancer. That started a journey he's been on ever since, a journey that he shares with us in detail. Along the way, Sid continued founding companies, including KiloCode, an all-in-one agentic engineering platform, which he also tells us all about. But first, a big thank you to our partners at Fly.io, the platform for devs who just want to ship.

0:47Build fast, run any code fearlessly at Fly.io. Okay, Sid Zabrandage, back on the changelog. Let's do it.

0:59Well, friends, I'm here again with a good friend of mine, Kyle Galbraith, co-founder and CEO of Depot.dev. Slow builds suck. Depot knows it. Now tell me, how do you go about making builds faster? What's the secret? When it comes to optimizing build times to drive build times to zero, you really have to take a step back and think about the core components that make up a build. You have your CPUs, you have your networks, you have your disks. All of that comes into play when you're talking about reducing build time. And so some of the things that we do at Depot, we're always running on the latest generation for ARM CPUs and AMD CPUs from Amazon.

1:39Those in general are anywhere between 30 and 40 % faster than GitHub's own hosted runners. And then we do a lot of cache tricks, both for way back in the early days when we first started Depot, we focused on container image builds. But now we're doing the same types of cache tricks inside of GitHub Actions, where we essentially multiplex uploads and downloads of GitHub Actions cache inside of our runners so that we're going directly to blob storage with as high of throughput as humanly possible. We do other things inside of a GitHub Actions runner, like we cordon off portions of memory to act as disk so that any kind of integration tests that you're doing inside of CI that's doing a lot of operations to disk, think like you're testing database migrations in CI.

2:22By using RAM disks instead inside of the runner, it's not going to a physical drive, it's going to memory, and that's orders of magnitude faster. The other part of build performance is the stuff that's not the tech side of it. It's the observability side of it is you can't actually make a build faster if you don't know where it should be faster. And we look for patterns and commonalities across customers. And that's what drives our product roadmap. This is the next thing we'll start optimizing for. Okay, so when you build with Depot, you're getting this. You're getting the essential goodness of relentless pursuit of very, very fast builds, near zero speed builds.

3:01And that's cool. Kyle and his team are relentless on this pursuit. You should use them. depot.dev. Free to start. Check it out. One line or change in your GitHub actions. depot.dev.

3:36Well, friends, we're back with a good friend of ours. It's been, Sid, way too long. Way too long, for sure. Way too long. The last time we talked to you, the last time I talked to you, at least, was when you were leading GitLab to IPO. This is pre-IPO. This is in 2022. It was speculative. That was obviously the North Star for you. You've accomplished that mission. You've had a cancer journey. You've had an investor journey. You've had the American dream journey and kind of back again in a way. So welcome back to the show. It's been way too long. Good to see you again. My pleasure. Thanks for having me.

4:12Looking forward to this. When we look at your story from, you know, some would say, you know, this shadow of GitHub from way back in the day to now, how do you personally reflect on your journey? I would say in tech, but also as a CEO, as just a normal person, as an investor, how do you reflect on this long journey of yours? Well, it's been amazing kind of living the American dream. 2015, I came to the U.S. We raised money for GitLab and we set our sights and grown the company, becoming a public company. And then six years later, we took it public, which was amazing. And we're very fortunate to.

4:57Six years to public, huh? Yeah. That's the speed. That speed. And you were very much a leader, too, with the way you opened the company, your open docs, a lot of the ways you hired, the ways that you showcased culture. A lot of that was even not so much not in public, but it was you were very much a star of that. And then you were also a company that IPO. That's that seems like maybe not the way it should be done, but it's obviously the way you did do it. Yeah, we try to lead the company with a ton of transparency. And we believe that helped us be an all remote company, but at the same time be super on the same page.

5:38And it's paid its dividends both in coordinating us, hiring great people, but also getting customers excited about the company itself and how we partner. Are you still involved in any capacity with GitLab? Yeah, for sure. I stepped down as exec chair last year, or stepped down as CEO, and now became an exec chair, which means that I'm still an employee of the company. So I still have two engineers reporting to me, and we're taking on projects that I'm super excited about. And right now we're working on adding observability into GitLab. So really, really exciting to work on that. So when you left GitLab as CEO, you were CEO, correct?

6:27That's what you stepped down from? Yep, correct. That position? It wasn't necessarily because you were done or because you've done your thing and you're ready to get a mojito and go to the island. You actually had a health problem, a major health problem. I mean, a health crisis in many ways around the end of 2022. and you've been on quite a separate journey, which is amazing to me. Some of the details that you've gone through in order to be here today, we're very happy that you are here today. Can you unpack a little bit of what you've been through in the last three years, four years with regards to your health and the journey you've been on to fight cancer?

7:04Yeah, for sure. So end of 22, one year after the IPO, I discovered I had bone cancer, a six centimeter tumor grown from my spine. And we had to do surgery really quickly. I was in a lot of pain. And we removed the vertebrae and most of the cancer and did a spinal fusion with a titanium frame. We did radiation, we did chemo. And I did my first single patient IND. I've since 2017 I've invested in one other Y Combinator company and over time that guy became my best friend his wife became my wife's best friend and every time he was fundraising the investors wouldn't put any money in and every time I said this doesn't make any sense to me that they're reluctant to put money in I'll finance the company so over time I became his biggest investor and what he's doing is is combining drugs with binders through glychemistry allowing you to target different parts of the body and when I became so very sick he he made a we asked for an exception to treat me with his drug and we got that exception and we did all the treatments and And then two years later, in 24, the cancer started growing again.

8:32And the doctor said, you're done with standard of care. There's no more treatment we have for you. Maybe there's a trial somewhere. And I started looking around. I have a weird HLA type, which disqualified me from a few trials. And I have a bone cancer, osteosarcoma. It's kind of a rarer disease. So there wasn't anything for me. And then it was my moment. I'm like, oh, if I don't move, I'm going to be dead soon. I had to step down as a CEO because I needed to focus my full attention on this. I started talking to anyone, traveling anywhere. I went to the medical conferences. I went as far as China to get scans.

9:14And I started doing maximal diagnostics, making my own treatments, doing treatments in parallel and trying to scale that for other people. and so that's been the journey I've been on in this over this last year and it's it's been a lot of ups and downs but also extremely interesting and I've learned a lot but I also think that there's a lot of things that could could be better and I'm trying to change those to be better and and making making the path I've been on easier for other people to to follow i understand the reasoning for parallel directions or testings because you only have so much time before it's too late and so i totally understand that it seems like as a software guy you want to try to isolate and do one thing at a time and then see if it works and then do the next thing versus having multiple factors i suppose if it's working it doesn't really matter which of the five or six is working if it's working but certainly for reproducibility and for helping others you do want to be able to have some sort of result that you can come out of it so tell me about the parallel side and some of the trials of that introduces and how you're maybe solving those problems as you go yeah if if you want to be able to reproduce you need to isolate the chains so when i started doing parallel treatments one doctor told me to my face but what if it works we won't know what would have cured you and then i let the doctor know that i wasn't interested in finding what cured me i was interested in getting cured that's right i'm not right i'm not researched i'm a real person that's right there the combination of treatments there's very little incentive for pharma companies to kind of spend a billion dollars it's now a billion dollars for a successful trial to spend a billion dollars for an approved medicine to to to research a combination of drugs so there's no incentives so all you see on the market are these drugs taken in isolation and doctors are reluctant to combine them because it's never been done before but if you look at the first principles you can say hey these treatments are probably okay to combine what you don't want to do is have like combine two things that both hit the kidneys because your kidneys are going to be over capacity and that's not good.

11:43So every time we do, we combine treatments. I have, for example, a pathologist in my tumor board to look at like, hey, can we combine these things? And we also look at my own markup, including genetics, but also histochemistry where you kind of, we do color slides in and we do multiplexing so we can color multiple things. For example, I told you I went to China three months ago, and I did that to get the first B7H3 scan available to me. And because of what we learned there, we were able to kind of change the development of one of the drugs I'm developing to remedy what we saw. We saw in China that I have higher B7H3 expression in the liver than any one of the 20 patients they saw before.

12:38And we decided to combine that medicine with something that's rarely expressed in the liver. So it's not going to destroy my liver going forward. So you got to be kind of, what I'm trying to do is kind of be first principles about it instead of kind of relying on evidence for the ability to combine because that evidence, it doesn't exist because no one has the incentive to do that. Right. And most people die because they, not because they've run out of treatments, they've run out of time. So why China? Is it a technical thing? Is it a regulatory thing here? They're just more advanced in certain areas.

13:15Like why do you have to go all the way there for this particular test? Yeah, so to be clear, most of my treatments and most of my tests are happening in the U.S., but Europe and China are also part of it. And what's remarkable about China, I found remarkable that I was the first, It was my first time traveling to that hospital. Within two hours, I was checked in. They formulated the diagnostic scan ingredients. They gave me the scan. They printed the results. They talked me through it, and I was outside again. I've not seen that speed in the US. One other thing that's happening is that these hospitals have a lot of patients.

13:55So instead of running a trial at 10 different hospitals, where it's a lot of work to combine all these investigators and to train all of them, you can run it in a single hospital, the same hospital where the investigator is at, the researcher is at. So they have a much higher speed of running trials. And you're starting to see a giant shift in the literature of trying to do more trials and making more medicines. So where do you stand? How's your health? How are you feeling? How are you doing? What's the future look like? Yeah, I'm doing well. Right now we cannot detect my cancer. So that's great.

14:35It's a really good spot. That is great. Yeah, that's a great spot to be. Compared to a year ago where it was growing and we had zero treatments. Today I have kind of a therapeutic ladder as in like if things get worse, we'll escalate the medicine and there's 30 medicines on it. So like we have options now. and I'm continuing the development of 10 different drugs and diagnostics that make a lot of sense for me to have. I've also started in the meantime six companies to scale treatments for other people, treatments that I've done but also treatments I've not done but just technologies we came across that we thought are underinvested in.

15:19Yeah. Do you know what has made your cancer undetectable then? I know that you weren't being in that research lab before, that research right before, but how do you, have you pinpointed what may have worked with these 10 different medicines you're developing? Yeah, for sure. I might have been one of the first people to do single cell sequencing as an individual patient outside of the context of a trial. It's kind of a strange name because you're not sequencing a single cell. You're sequencing thousands of cells, but you're able to see the genetic markup of each cell and you're able to see what the tumor is looking like, which cells are in there, how do they behave, and what's their genetic markup.

16:07It's an incredible, powerful technology. We compared that to an atlas of kind of what bone marrow should look like. and we zoomed in we were able to kind of zoom in on the cancer cells and one thing we noticed is that they had a lot of fibroblast fibroblast is kind of scar tissue and we were aware of a treatment in germany an experimental treatment that has an fap binder that binds to fibroblast and then the other on the other side you put a radioactive element lutetium or actinium and it did two treatments there with incredibly good results first of all no side effects I couldn't detect any and we saw 60 % necrosis and 20 % shrinkage which considering it was only two treatments that was a great result my cancer is in my back near my spinal cord because of the shrinkage it detached from the spinal cord, allowing a really talented surgeon to go in and go after it and remove most of it surgically, which wasn't possible before.

17:18And this is because it would attack the scar tissue. What was the name for the scar tissue? Is it because you were able to pinpoint that and allow it to detach from the scar tissue? Yeah. So what we were able to do, because of the scar tissue we had a binder for that called fap or this experimental treatment in germany had that and you combine the binder with the radioactive stuff so a lot of drugs you just give them to the entire body yeah a standard chemo drug it's devastating this drug is also like a really nasty thing like lutecium is like radiating you from the inside i was like 10 times as radioactive as an airplane at altitude from the outside let alone what was happening inside of me oh wow they have to like you they keep you in isolation because you can't be around people you can't be around people but because it was on this FAP binder it targeted my tumor especially and there's also a little bit of risk for like for example um your your loss of taste and smell but I had non side effects there so it was it very specifically bound to to the tumor tissue which is just amazing like most most cancer treatments are way worse and yeah enabling surgery was a was a big deal like if it's right up against the dura your spinal cord that's not great but in this case it was detached from there because amazing yeah it was really great how long were you really radioactive you're radioactive for kind of a week but only two days in isolation and then you get a letter and then you walk at the airport maybe you've seen those things in the u.s now you walk into the airport and there's a black thing i guess what beep beep beep we once had um three people with scanners around us uh and they had to call kind of washington because their sensors were showing plutonium which is not which would not be good wow but it was uh luckily uh it was the lutetium after all but they had to have a scientist in washington you were a person of extreme interest there for a little bit yeah they as soon as they knew it was me and not my luggage they were they were super chill about it they were super chill that's hilarious wow can you talk about the type of cancer the sarcoma there's like 70 different types and i i asked this question because i have a dear friend of me and my wife's who passed away probably 14 years ago and she had sarcoma in her lungs she was actually studying in houston which is a very popular place for cancer research at least here in the states it's one of the capitals of cancer research and she was studying to become a doctor in this field and actually not through the not through her lab time or anything like that.

20:21But she came to actually get the cancer. I don't know how to describe getting cancer, if it just develops or if it grows or what actually gives the cancer to you. But she developed the same sarcoma cancer that she was studying. And it was just really, really bizarre, bizarre. Yeah, quite bizarre. Like there was there was no real connection there. The same doctor that she was studying under was her doctor during her process. She obviously ended up passing away. It was about a year, maybe a year-ish, devastating to our life and our friends. But can you speak to the sarcoma type cancer and what that type of cancer does or does not do?

21:00Do you know much about? Obviously you probably do, but like there's 70 different types and I'm not even that familiar except for I know that she had sarcoma cancer and you mentioned you have a version of it as well. Yeah. Like I'm not a doctor. This is not medical advice. I know very little about that type of sarcoma. I do know sarcomas are genetically pretty diverse. So there's a lot more studying to be done. For example, the kind of the standard genetic reports showed like TFE3 amplification, but when we really started digging, it wasn't the driver at all. So because of all that copying of the genes, it's harder to analyze, but there's also more kind of special things about it that allow you to do more targeting.

21:45um yeah and you mentioned houston big big fan houston methodist is especially uh great here um and i know very little about lung sarcoa what i do know is that for bone cancer the biggest risk is that it spreads to the lungs um if you have these cells going on the loose the the first place they'll likely end up are your lungs also because your lungs are very tiny vessels so they get trapped the cells get trapped there the fastest but also because it's kind of a similar cancer that can can grow there so we were watching for that and at a certain point I did a kind of a regular pet scan where you look for activity that is out of the ordinary and I remember vividly I was talking with my direct reports and I get a message, a text from my GP, and he says, it's positive, not subtle.

22:54I'm like, it's positive. Okay, great. And I'm like, oh, no, positive in a medical setting. That means something else. It means positive for cancer. and not subtle that sounds bad and i opened up the report and i read my death sentence it spread to 50 sites in my lungs my lungs were lighting up like a christmas tree and the radiologist gave an undifferentiated diagnosis definitely cancer spread to the lungs way metastatic. 50 places means like surgical, your host. There's no way to do it with surgery. And so walked out of the room, collected my thoughts for 10 minutes, called my wife, called in my CFO, CLO.

23:49Like, this is the situation. What do we do? I'm going to tell or not. started to tell and we all took a long walk together started my doctor started coming in so sorry for you, so sorry for you, so sorry for you and then this the last doctor basically to chime in was like yeah 60 % chances isn't cancer I gave him a call like Chalo what do you say? he's like yeah the lymph note pattern, how it spreads, this doesn't seem like lung cancer to me. And this is a guy who've run the most osteosarcoma trials or the most sarcoma trials in the nation. So he might not, he's just seen so many patients and seen so many people who this happened to.

24:46So, okay. So I went And now I was a dog with a bone. And within a few hours, we cleared it up that this was the remnants of COVID. It wasn't. Because we were so afraid of this happening, including the radiologist, everyone had a bit of tunnel vision. But quite the experience to tell your team you're a goner. Yeah. Yeah. And then the exact opposite when you're like, you know what? They made a mistake. It was just COVID and not, not, cause that's, that's exactly it. Like it went to her lungs and brain quickly, very, very quickly. Those are the two places that tends to spread. So it may begin lower in your liver and in your back like you were, but it spreads quickly to other places and it sort of takes you quickly.

25:39If it, if it's not, if it's, if it's not COVID, if it's something different. Right. probably the happiest covid diagnosis of all time wasn't it yeah thank god it's covid for sure i wasn't super happy about the diagnosis though that radiologist and i are maybe not going to be friends yeah i mean obviously they put you through turmoil and terrible things i had a nowhere near as serious and yet relatable diagnosis with my knee when i was told that i had torn my acl and i would never play basketball again by a physician's assistant and then the actual knee doctor came in he's like no you're good he's like she's wrong i'm shortening the story but i had like 15 minutes of like oh i love basketball like my whole life changes in small ways yours obviously in a huge way but then him being like nah she didn't understand this thing and she messed up and it's not as bad as she thought it was and i was like let's fire her or something you know and these things are not trivial to diagnose.

26:38Yeah. Yeah. It's not easy. So it's undetectable. And this, in this moment, you just shared this dramatic story arc that you've gone through. You're recalling it here in this moment, this podcast is the expectation at this point with you and your medical staff that it's not going to come back or it's just undetectable and you're still actively trying to just work on it or treat it like what is the current status of how you're dealing with it is it just gone for now wait or how are you handling things yeah we we assume that it's not gone and the only reason it'd be gone we know that the surgery didn't cure it that they left positive so-called positive margins so they left cancer the only thing that was remarkable when we the cancer we removed we were able to flash freeze some of it which is amazing for people with cancer it's way better to flash free stuff because you it allows you to do many many more diagnosis on it later than if you do the standard which is ffpe which is like it preserves it but it precludes you from doing a ton of tests so if you want to have an active role in your treatment, you got to convince the hospital to do flesh, flesh free some of it, so that you preserve optionality to run these diagnostics later.

28:05And what we saw was that the T cell infiltration went up a lot, it went up from 20 % to 90%. So it was the place was buzzing with T cells, which is a good thing. And we think that is a combination of the two checkpoint inhibitors that I'm taking that kind of unleash your immune system. And one experimental treatment that is an oncolytic virus, so like modified common cold virus that drops the TGF beta. The TGF beta is something the cancer uses to hide from the immune system. And it kind of tears away that invisibility cloak. So that's good news. We don't super think that that's curative, but I'm gearing up in two weeks to take an mRNA vaccine and that's like a 50-50 of curative.

28:59But there's a reason we have like 10 drugs in the pipeline. It's where we're trying to cover all our bases and rather have a drug too many than one too few. Yeah. It sounds like you're in a buy time kind of scenario. Am I reading that right? You're buying time to research it more, to attack it more, to have a mRNA opportunity for a 50-50 chance? Is that kind of where you're at? Yeah, so the mRNA is potentially curative. So in that case, you're kind of, you're done with this. But it's certainly like buying time. You got to have enough treatments to make it to the new development, both science advancing and some of these drugs that I'm developing, they just take years, many years to develop.

29:43So you want to make sure you make it to the next spot and hopefully in as good of a state as you can with like no, hopefully no metastatic cancer, hopefully no fried kidneys. This is the year we almost break the database. Let me explain. Where do agents actually store their stuff? They've got vectors, relational data, conversational history, embeddings, and they're hammering the database at speeds that humans just never have done before. And most teams are duct taping together a Postgres instance, a vector database, maybe Elasticsearch for search. It's a mess. Our friends at Tiger Data looked at this and said, what if the database just understood agents?

30:31That's agentic Postgres. It's Postgres built specifically for AI agents, and it combines three things that usually require three separate systems. Native, model context protocol servers, MCP, hybrid search, and zero copy forks. The MCP integration is the clever bit. Your agents can actually talk directly to the database. They can query data, introspect schemas, execute SQL. without you writing fragile glue code, the database essentially becomes a tool your agent can wield safely. Then there's hybrid search. Tiger Data merges vector similarity search with good old keyword search into a SQL query.

31:11No separate vector database, no elastic search cluster, semantic and keyword search in one transaction. One engine. Okay, my favorite feature, the forks. Agents can spawn sub-second zero copy database clones for isolated testing. This is not a database they can destroy. It's a fork. It's a copy off of your main production database if you so choose. We're talking a one terabyte database, fort in under one second. Your agent can run destructive experiments in a sandbox without touching production and you only pay for the data that actually changes. That's how copy on write works. All your agent data, vectors, relational tables, time series metrics, conversational history lives in one queryable engine.

31:59It's the elegant simplification that makes you wonder why we've been doing it the hard way for so long. So if you're building with AI agents and you're tired of managing a zoo of data systems, check out our friends at TigerData at TigerData.com. They've got a free trial and a CLI with an MCP server you can download to start experimenting right now. Again, TigerData.com.

32:51A lot of meetings, mostly the whole day is meetings, 25-minute meetings, like 15 a day. I've also done some traveling for pleasure. We thought at the beginning that this might be my last year. So we celebrated the 25-year anniversary of me and my wife extensively. Thank you. With friends and family. That was great. also a lot of traveling like going to medical conferences going to treatments on a on multiple continents um but also doing doing fun stuff like adding observability to gitlab i started a ai accounting company called kilo um i'm still creating these companies around open source projects with open core ventures and then since september starting to biotechs every month.

33:42So how many companies are you currently involved in today and here in December? So I started 30 companies over the last three, four years. And what made you want to get into open source agentic coding when you have all this, these medical companies, you've got to get a lot of stuff going on, you want to, but you want to work on this. Why do you want to work on this particular problem? I saw kind of the rise of open, open source agentic coding companies. And And obviously, authentic coding is very cool. It's the future. And it was cool to see that open source had a chance here. I kind of, before I thought it's all going to be closed source.

34:24And I saw the rise of open source. And I thought, okay, time to join that game. Are you deploying a similar playbook that you deployed with GitLab back in the day? Yeah. the Kilo is it has great agentic coding but the the best reason to use it is that it's all in one so not only can you do the coding it can also review your code not only can it do that it can also do a security review not only can it do that it can also deploy it so it's available everywhere VSCO JetBrains CLI in the cloud and the mobile app and it can do the full life cycle, including deployment, and we're working on more there.

35:14So just like GitLab, the idea is to be the all-in-one solution where you don't have to switch applications the whole time to do what you need to do and to be open source where people can contribute improvements. Right. So what's the open core aspect with Kilo? So you mean what's the paid functionality? Yeah, where are the lines drawn? Like, what are you thinking? We're thinking if a feature is more appealing for managers or executives, that's where they need to pay. So for our team's functionality, for example, to see AI adoption throughout an organization, that's paid functionality, 15 bucks per user per month.

Read the full transcript

35:54and then we also have an enterprise version with features that appeal to executives like centralized, bring your own keys so they can send it to Bedrock in their VPC. That makes total sense. So are you working on models as well? Are you just a model agnostic? What's your look on that aspect of the world? Yeah, we're not working on models ourselves. We're working very, very hard on supporting all the models. So hundreds of models work over 500. We're the most prominent launch partner for new models. So a lot of new models, a lot of stealth models are first launched on Kilo. And our users, a lot of our users use free models like Grok, MinMax, GLM with Kilo.

36:45Interesting. I think I haven't even heard of a couple of those. I've heard of Grok, but MinMax I haven't even heard of. So this is either underground or upcoming or when you say new, Bleeding Edge perhaps? Oh yeah, it's all new. It's like all launched in the last two months. There's a lot of kind of Chinese frontier labs. And they want to quickly get their models more popular. So they offer incredible pricing just like Grok. It's Grok Code is incredibly good model and it's been free for months now. it's an interesting space because you've got a lot of things happening around google in particular there was an announcement today for a flash model i think it's called gemini flash if i can recall correctly but uh you know when you look at that they can essentially offer their models in the api layer for virtually free or a loss leader because they're trying to build their platform while open ai and anthropic are burning cash making money for sure but you know when you when you're fighting a competitor that essentially can outlast you because they already have so much incumbent cash or value elsewhere in the chain it's kind of hard to to battle somebody who's willing to lose or break even when you have to profit what's your take on the current landscape of just the competitive nature from nation states like maybe china etc maybe that's just companies there to the battle that's playing out here in the US.

38:14Yeah, I think the kind of the leading coding model, that's an incredibly competitive space where kind of the, it always feels a bit like OpenAI is a better model. And then Google has a better model and then Entropic comes back with like the best model by far, for sure. Yeah. But also the best kind of free model is incredibly competitive with DeepSync, MinMax, GLM, all these providers kind of one-upping each other. And what we offer our users is you're going to keep using the same application. You don't have to sign up for a ton of stuff. It's just our thing. There's no charge. It's completely free.

38:59and then you have the ability to use any model you want soon you can use different models you can use free models bait models whatever you see fit so in kilo you can also kind of define different profiles because a lot of people prefer to open ai models for planning and architecture that they prefer something something else like i use opus 4.5 or for a hard book troubleshooting I'd use Grok for kind of the smaller tasks that are easier. So it's kind of a mix and match approach. I think we're going to live in a multi-model world instead of one model that's the best at everything. For sure. One of the challenges I remember for GitLab, which I think you all overcame, was because you wanted to be all-in-one and you were providing the entire software development lifecycle tooling, almost every aspect of that, you had like startups and businesses that like their entire focus was that one thing whether it was like bug tracking or observability or you know deploying or whatever it is i feel like you're going to have the same situation here with kilo where it's like there are people attacking like separate slices of what you're trying to do and i wonder how you're going to do all the things well yeah the same way we did it with git lab go incredibly fast if you look at like where we've come from.

40:27We only started in March and now we have code reviews, deployment, all these things in one packet. So we're moving extremely fast also thanks to agentic coding plus contributions. And I think we can even improve a little bit on working with the wider community. And yeah, when GitLab grew up it was like, oh, but Travis CI has already dominated the CI space. It's now like, hey, hey, CodeRabbit is already dominating code reviews. Just, yeah, let us cook. We'll go faster than anybody else. You got the same people working on it, or how do you know you can cook so fast? I mean, it worked last time, but was it the same team?

41:10Because talented people make good products. There's some people who, after GitLab, went to work for other companies, and some of them have joined, but the majority of the team has never worked at GitLab. And they joined Kilo because they want to go incredibly fast. They know the bar is high. They know they've got to work really, really hard. For example, at some point, once a quarter, we come together. We do a focus week, and we all work our butts off for a week. And we do that together. And a week before focus week, it was clear that we weren't recruiting fast enough. So I put a LinkedIn post out.

41:48I said, look, apply by Monday. We'll make a decision by Wednesday. And then the next Monday, you're expected in Amsterdam. and four people did that, and they all shipped the initial prototypes of their functionality by the end of the week, and all of them launched their functionality December 10th, less than two months after Focus Week, and it's all held up so far, and now they're all going to make it better, but it's incredible speed. The way I would look at it is it used to be that you needed like a team of seven people to do something. now you have one person and kind of a whole team of agents working on something so yeah we have like 20 engineers but in reality they're all working with seven agent decoders and that's the expectation that you as an as one human you ship at the speed of what two years ago would be a team of seven or eight that's interesting so you've successfully parallelized your cancer treatments and your engineers are parallelizing their agents i can still only keep one agent busy at a time.

42:51Maybe I'm not ready for this new era. I couldn't work for Kilo. How do they do it? You know, when you got all these different, you know, down in the weeds of how they're managing multiple agents working on a singular feature, I suppose, or a set of features that support a larger feature and how are they staying productive and fast in that environment? That's common. Like you're not alone in only being able to keep one agent busy. But I think 2026 is going to be the year that that changes. Our parallel functionality where you have kind of, you farm it out to multiple agents in multiple work streams.

43:27That's just getting started. A month ago, the engineer who made Schaltwerk, one of the early ways to parallelize things, joined us and he's doing amazing work. There's still a lot to do. For example, Kilo has a functionality that's orchestrate. With orchestrate you say this is what I want to achieve and split it up into separate jobs so each of those jobs has small context windows because small context windows means it's cheaper to run, it's faster to run but most importantly it's not going to lose half of its context because it's kind of getting to the maximum context window that's effective.

44:06but in the coming weeks we'll ship something where those different agents are now able to work in parallel and you can do a runoff especially if you're using these free models you might as well have two models work and then see which ones have which one has a better result so i think you're you're we're we're going from you have one working directory today to in the future, you have multiple tasks running in parallel. And each of those tasks is running multiple types of agents because it's hard to predict up front which agent will be the best in any given thing. Right. That sounds cool. It also sounds expensive.

44:45I suppose commodity pricing just keeps going down. Is that the approach here? Just innovation and investment brings down the price of agent coding? If you go to kilo.ai and you look at our homepage, We see the 10 most popular models for TLO. I tried to count them this morning, and I think 8 out of 10 offer free usage today. So that's a way to afford it. Free as in freemium or free as in free? Free as in free. But until what? What's the catch? There is no catch. Grok is amazing. I've been told that plenty of times in my life, and then eventually there's a catch somewhere, somehow. Well, it might be that this whole thing ends at some point where these models...

45:31Yeah, the catch is it's temporary, maybe. Where these models... But what we've seen over time, this has been going on for half a year now, and there's models that kind of launch for free, and at some point they become paid. But the rate at which free models are launching is faster than the rate at which they're getting deprecated. So there's now more free models on the market than there were half a year ago. That's interesting. Eventually, you would think you'd have to make some money somewhere, you know? Yeah. Maybe this is like when VC money was plentiful and the Ubers were really affordable.

46:06VC dollars are plentiful and the leading labs have free models. I like. Right. Use it while you can. Yeah. Use Keylor to burn. Burn the VC money out. Burn the VC money. I think that's a legit strategy. the challenge with it is over time I think you do become hooked you know it's like uh like drug dealers the first one's always free now that for in this case maybe you get a lot for free but eventually it's like I don't know how to write software any other way and then you know three years from now and that's when they turn on the old money making machine and now you're just subjected to renting your life away but yeah it's I I think the what you're hinting at is that the cost will go up i think the cost will go up not so much because the same quality model will get more expensive like the same quality model gets 10 times cheaper year over year right but what we've seen is that the price of a frontier model per token has kind of held steady and every time we think it's going down there's like gpt 5.2 uh what is it thinking or pro the really expensive one and and so that's holding steady but the amount of tokens you can burn as a human that is shooting through the roof yes with this like split split up the work with my only one agent you know i'm only doing one agent i can burn some tokens i imagine if i had six agents going i mean that's just 6x my token ability exactly and the future we're going to live in is not one where you have like a hundred dollar or like like a twenty dollar subscription a month i think humans are gonna burn ten thousand dollars in tokens maybe a hundred thousand dollars in tokens per human you think so and they'll be they'll be a hundred times more effective than the humans of yesterday right it'll be worth it because one human plus all that is more effective than exactly however many humans would cost you that 10 grand doing what i guess is the question like is it just coding is it just planning this is next business man i mean this guy's got businesses coming out his ears doing doing everything like every knowledge worker is going to have a collection of agents working for them it's a wild world yeah it's interesting about the how that plays out though like you know it's it's almost unimaginable to think about like i couldn't imagine this year from last year for example i could i suppose but the vantage point the perspective is it shifts so quickly and so much like for example i just mentioned you know google and their flash model that's like news as of i believe today like in the last 15 hours you know every day or week we have a new model new flip a new change and it seems to be like ux is the moat ux is still being figured out i think kilo is an example of how you're trying to evolve or think about different use around agentic usage, it seems hard to predict where we'll go.

49:09It's incredibly hard. And we thought this AGI, where AI would be as smart as you, this is a seminal moment. And it happened in April. It just flew by. We hardly even noticed it. You said we had AGI in April? Is that what you just said? Yeah, I think in April, the models became as smart as the median human. Oh, is that what AGI is? Artificial general intelligence, yes. My definition, I stole April from Tyler Cowen, which I think is one of the smartest people on Earth. Okay. I must have missed it. I just don't know how generally, I guess maybe you're saying because most humans are generally unintelligent.

49:52Well, also like think about ChatGPD, like it might not know more than the expert in a field, but it knows a lot about everything. The ultimate polymath. Yeah. Yeah, I mean, like I was having some really interesting conversations with the chat GPT the other day that was very therapeutic. You know, I have been on the code side of things, and that's where I'm comfortable at, like with how it knows what to do. And I guess on the human side where I have a conversation with it, and it's not just a question and answer, it seems to know such detail about particular things. And I don't know how it does that, but it was a therapy conversation essentially.

50:36And it was just uncanny, the response type and the level of care. And it wasn't just how it outputs. It wasn't just formatting. It wasn't just user experience. It was this depth that I never expected a machine, basically, and potentially even AGI, who the heck knows, to give me back this feedback loop. I just never, like, I'm steeped in this stuff, right? I think we've been steeped in this stuff for years and it is just quite literally unbelievable. Like, unbelievable that I can have that kind of conversation. I'm being vague to a degree, but it was very therapeutic. It's incredible. This year, it helped us a lot.

51:18Like, think about how much stuff I had to learn this year. And even yesterday, I was like, I don't really know how a TCRT is different than a CAR-T. And wow, ChatGPT walked me through it and all the pluses and minuses. But we're going to give a talk at OpenAI soon because we did some things that were super beneficial to us. Like we did an RNA test of my cancer to know what RNA was going on. And we just sent a spreadsheet to ChatGPT. And what came out of it was really insightful. Can you be specific in any way? Like what blew your mind, I suppose? What you're looking for with RNA is like not so much, you have the genetics, but what's actually happening at the cell level, what's being expressed, and what are potential pathways that are overexpressed and you can target.

52:12Because I know from the genetic, there's something that sounds like a party drug, but isn't. MDM2 is overexpressed. But I want to see how like the thing it acts on, the p53 division how that's how that's going in my cell and there's better examples here but i'd have to hashtag gpt for them i don't want to be distracted while talking with you but like for sure just incredible things and it's not the end all be all like don't take a treatment without first checking it with a doctor but just if you have to get smart about a subject in a year what what a what a yeah an amazing blessing it is it can connect dots that's where i like in this the dot connecting is is across the board of all sorts of different disciplines and domains that's why i said polymath because like yeah that's probably not even a great example it's like you know uber ultimate ultra think polymath i don't know no polymath is great and that's also the big benefit right like we deal with a i've talked to hundreds of specialists this year but when you you start talking to people who are extremely narrow because they're like the expert in the world in one specific thing.

53:19Right. It's really hard to do the integration. You end up in these meetings with like eight people and they're incredibly expensive and hard to organize. And something like ChatGPT, which is like very knowledgeable about everything, is incredible for integrating the knowledge and giving you directions to go in. Yeah, that's where I really, and maybe this, I don't want to tangent us by any means, but this is where I get really, really conceptual, I suppose, about where the future might go. Because we need, I think at least, even in this moment, we need humans to go super deep and super thoughtful into a very specific domain.

53:58And like you had mentioned, you have to have eight humans in a room, hard to organize. But we need those kind of folks to think about the long-term future of humanity and not so much like in this way I'm saying it, but like feed this algorithm, this LLM, this model, its knowledge, not to replace them, but to augment how fast we can iterate through a problem set that requires eight humans and a polymath that sits above those folks to go so deep on a subject that's just basically impossible for eight collectivism. didn't mind us to do in one briefing room. Like it's just humans don't work that way.

54:37We don't share that way, even interpersonally, but a machine or an AI that's designed to do that can for us. And that's really where I, it's kind of like a headspace kind of thing, but that's where I mapped to is like, you got to have these super deep thinkers with this deep knowledge. And they, they're obviously going to be human because that's what, what we've been as a race to enable this AI to think so deeply and so vastly as a polymath would and connect dots that we just wouldn't normally connect as humans. That's the saying, if I've been able to look further, it's because I stand in the shoulder of giants.

55:15And it is, in a very narrow field, you're able to, some people are able to read all the relevant publications and to keep up with that. But it's incredibly hard work. and now with these AI things you suddenly have a thought partner that not just read everything in the field you're in but in all other fields so you're not you're not forming these people standing on top of each other in in one discipline it's like it's as far as the eye can see every discipline you're up to date on the latest knowledge that that is just incredible it allows you to like run around where before if you if you moved outside of your field that the whole thing fell down and now you're just able to combine disciplines like like never before yeah it really is amazing where it stands today and also where it's headed which none of us can really know but we can see that trajectory moving us forward so you just got this engineering meeting all the ideas are great and now you've got to go through your notes this time-consuming part read them all digest them all add action items put it in the right places tag team members this is all necessary work but it's tedious okay so flip side that take that same position and flip it over into notion and using notion agent notion agent does the busy work for me it's like having a project manager that keeps everything on track in the background while I focus on the bigger picture.

56:48Getting my work done, doing my best work, being the artist. Notion brings, as you know, all of your notes, all your docs, all your projects into one connected space that just works. Seamless, flexible, powerful, and actually fun to use. With AI built right in, you spend less time switching between tools and more time creating great work. And now with Notion Agent, your AI doesn't just help you with work, it finishes it for you. Notion Agent can do anything you can do inside Notion. It taps into your workspace, the web, and connected tools like Slack and Google Drive to complete assigned actions end-to-end so you can focus on the hard decisions.

57:33It's like delegating to another version of you that knows your style, knows your workflow, and knows your preferences because it learns from how you work. With a single prompt, Notion agent forms a plan, executes it, and will even reassess and try again if it hits a snag. Completing multi-step tasks like creating new pages or databases from scratch, summarizing entire projects, it does this all in minutes. You assign the tasks and your agent does the work. And since this is all inside Notion, you're always in control. You tell your agent how to behave and it will remember and update automatically.

58:12Everything your agent does is editable and transparent. You can always undo changes so you can trust it with your important work. And Notion, as you know, is used by so many people. Over 50 % of Fortune 500 companies and some of the fastest growing companies like OpenAI, Ramp and Vercel, they all use Notion Agent every day to help their team send less emails, cancel more meetings and stay ahead. So try Notion now with Notion Agent at Notion.com slash changelog. That's all lowercase notion.com slash changelog to try your new AI teammate Notion agent today. And when you use our link, you're supporting our show again, notion.com slash changelog.

59:01You mentioned$10 ,000 a month, something like this, you know, with a human and some agents doing their thing in the future. I just saw a post today about cursor, someone paying$1 ,400 a month for cursor and, and someone saying that's ridiculous. And then the other person saying it's worth it etc etc we can have these kind of battles but it made me think back to kilo because i i did see on your home page you're kind of attract trying to attract cursor customers i think there's even a billboard somewhere in the valley calling all cursors over to kilo can you explain the angle um the relationship i'm sure you have plenty of cursor users listening to the pod who are very familiar with that particular tool and maybe use that as a way to explain what Kilo looks like and how it works and all that.

59:47Cursor is always a little bit vague about what is list price and how much do you pay, and they make significant changes over time. With Kilo, we pride ourselves on, you can use over 500 different models, including a ton of stealth ones and free ones. Also, if you're going to pay for a model, you pay list price. We charge exactly what the provider lists as a price. so you know exactly what you're getting for your dollar. And I think as people start kind of consuming these AI tokens more and more, that is the way to go. Instead of like a subscription where it's a fixed amount, but if you go over, there's a charge, which might, it's probably higher than this price, but it's hard to exactly know.

1:00:37We think a great mix of free models for the problems where you can use those plus paid models at exactly this price without any commission or overcharge is a compelling proposition. And so Kilo uses this orchestrator itself in order to pick models in addition to orchestrating your own tasks based on complexity and the particular needs. Right now, people are still selecting their own models in Kilo. It's not trivial to select the best model, and people also have their own preferences. And what people especially don't want that choose Kilo, they don't want the model to switch up on them. They don't want auto model where you don't really know what it did.

1:01:27And they also want to be sure that they're using the exact same thing the whole time. So if I say I want that, I want exact that with the exact context window, because it's very frustrating if you're randomly using another model or somehow the context window is half of what you're used to. Right. I think humans are really good at kind of using, selecting the right model for the right task, but you don't want to, you don't want the software to change it up on them unless, unless they, they give you permission and then still you want to know what exactly was used. that could be configuration in a way right you can automate that that selection through configuration obviously we went convention over configuration in a lot of cases but that's a way where you can say well when you do these kind of tasks for me i'm cool with you being on the flash model for example or on the haiku model where it's faster more iterative planning whatever and but when we're planning what we're going to go deep and we're looking at a jira ticket or a looking at a pull request and we're looking at this i want you know the the better model the more reasoned model to to examine that for me in kilo you have profiles and you kind of set your own profile and that's a combination of want to use this model but i also want to include these prompts you can even share these profiles across your organization so you you collectively work together of like this is a really good agent for upgrading our java code or something like that Because those are going to change too.

1:02:53And your mileage may vary. So you may use a particular model and you're a REST developer. Or you may use a different model and you're a Java developer. And you may get better results per your team with a model. And that's something you should probably be able to select from. But you're still getting top tier models, but in a config where you can say, well, I prefer Opus 4.5 versus the latest Gemini, for example. Yeah, and you're basically creating team members. And just like in a real company, it's helpful to have the same team member. Now, these profiles don't have memory yet. That's something for the future.

1:03:28But they already have a collection of prompts that are super helpful for that company, for example. And simply your style guidelines are like, I tried to upgrade our Java before and it needed these and these prompts to be effective. So being able to share at least these prompts is super helpful. How does Kilo manifest itself to people? like what does it look like how does it work you mentioned it's in like all the major editors so i imagine it's just in the case of vs code extension and there's a windsurf deal can you explain kind of the surface area of the product yeah so it's all the vs both vs code based editors all the jetbrains editors it's available there's a cli that you can run anywhere and then we also allow you to kind of run it in the cloud cloud agents that's called and then we're soon launching it works on mobile already but we're soon launching a mobile app as well oh explain how that would work i think one of the cool things is if you have a thought you can just kick off kick off the agent yes with that so instead of kind of give it to me yeah look you're somewhere you're not going to go to your desktop you have an idea now you write it in your notes or whatever you do tomorrow you just kick off an agent and then you can pick up that agent whenever you get behind your notebook again.

1:04:47It's going to be available in JetBrains, in VS Code, etc. So all your sessions, you have a complete overview of your sessions, whatever platform you're on. And I'm looking forward to also getting kind of a mobile notification when my agents are done, because that's my primary thing. Like the agent is done. I need a ping so I can see what it produced. This is something that Cloud Web is what I call it. It's just cloud.ai, but it's not cloud code. It's Cloud Web. they just enabled you to connect a repo on GitHub. And I think this is like early days of this feature. And I didn't really have a repo to connect it to, to think about.

1:05:25So I was like, I just want to like do it in an isolated area where there's no damage. You know, I can't go write code accidentally or send a pull request or do something weird. And I connected to a brand new empty repo. And I just kind of one-shotted in a way this idea that was really just a basic GoCLI. Right. And in this case, it was kind of a coding session, but I was just trying to thought experiment. Okay, if you have this mobile interface or this web interface that is not a coding environment at all, it's not cloud coding in the terminal. It doesn't have terminal functions. It doesn't have your system or things like that it can use to write a Python script and run it kind of thing.

1:06:01I suppose it does in its own virtual environments. But I was like, how does this work where you can not be in any sort of way an IDE or a code editor and be, in quotes, a developer or a builder or someone who's thinking about software and planning it? But then it's like, hang on, I'll just go ahead and write this for you and commit it back to this repository. I'm like, what? Okay, do it. You know, that's a kind of a cool role. Is that a version of what you're doing with Kilo in the mobile app? Yeah, for sure. And that's available on our website, too. It's called App Builder, and it's more of the replet experience where you prompt what you want, and it starts coding that.

1:06:42And because we have these cloud agents, which are really the back end of that are Cloudflare containers, because we have that, we can also do code reviews. So as soon as you connect your GitHub or your GitLab, you can just say, hey, from now on, all the code that was written automatically kick off a review for that as well. you can already configure Kilo to focus on certain aspects be less strict more strict etc I think that just gives us more of a reason to always be working in a way it's like in the new knowledge worker world and it's like hey what are you doing over there well I'm not scrolling TikTok I'm I'm actually writing software right now but you're on your mobile device that's just an iPhone right yep no i'm knee deep in a problem and i'm i'm fleshed out a spec or i'm you know whatever you know like that's kind of wild to think that from this mobile device we could just be on the subway or at a birthday party and we're bored and working yeah i think i think these are your co-workers the most natural way i interact with my co-workers is either a video call or slack and we're like we're going to launch a slack integration in no hopefully this month and otherwise next month because that's that's the way i interact with a co-worker and that's the way i want to interact with an agent too so i think collaborating with agents is going to look a bit little bit less like this big monitor with an ide on it and more like slack on your mobile phone yeah think mode i said the term earlier polymath would you consider yourself a a polymath said well since this year at least i do two things but you're poly do a math maybe but i look i'm no i'm no call us and brother i'm no casey handma i uh i i get by i certainly have a broad set of interests which helps selling composter syndrome right there like you don't want to call yourself a polymath but you're a polymath he'll let us say it but he's not gonna say about himself yeah that's fair do you have any thoughts uh i'm thinking kind of like uh given your history with git lab your entire career arc uh even through a crisis in your life you've had the chance to mentor lead design the most effective culture take company to ipo live the American dream, have an amazing marriage of 25 years.

1:09:18Congratulations again. Something as simple as the hope for the future of developers. Can you weigh in or do you have any thoughts at all about the, I hear this idea of this come back to like, there was a lot of people let go, a lot of junior developers let go. And here you just have Matt Garman, CEO of AWS, saying that junior developers, it's stupid, don't replace them with AI. Don't do that. Do you have any outlook or any hope for the future of being a software developer and what that might look like? Look, I'm a very lazy person. I don't like tedious things. And although programming seemed interesting to me, I read some of the code and I'm like, standard IO?

1:10:04I'm not going to write code that way. that seems super boring so i never got into programming until i saw ruby and i'm like wow this is this is beautiful this is the opposite of tedious this is beautiful and it's efficient with my time and i i love this interface and i i think agentic development is another step towards this is no longer tedious i could just have an idea in my brain of how something should look how should something should work and I can just write that down or even use voice mode in kilo and it will it will get done it it's amazing like it's never been a better time to to create software because we can do so much more so much quicker and and it doesn't have to take you 10 years anymore you don't have to study computer science you don't have to solve these lead coding problems anymore.

1:11:02You can just make it yourself without any other human helping you. It's incredible. I agree. It is a fun time to be a developer. And the way I look at it or the way I think about it is like the state of play. There's studies on flow. Obviously, you can go back to that. It's neuroscience, basically. The state of play is where we learn and have the most fun and it feels like playfulness. It feels fun to do, Even if it's challenging, arduous in some cases, maybe there's a learning curve, you know, there's a research phase. You got to get caught up on, you know, how an API or CLI works or whatever.

1:11:38You got to learn things you didn't know beforehand. And because I think there's a level of learning in all of this, even if the AI knows a lot, I think you should still know just as much as well, or at least try to, or strive to have understanding. It's kind of wild to be in that space where it's the state of play. It feels like very playful. Yeah. For me, a state of flow is where I don't go off and check Hector News and Reddit on the side because I'm getting bored or I have to wait. And I think 2026 will be the year of the parallel agents. And it's like the spinning plate act where you have all these agents up in the air, all these spinning plates, and you continually have to kind of shake one of them to keep them all up in the air.

1:12:21you never have to be bored again or wait for them. And I think that new balance will be like, I don't know, balancing on a surfboard or something like that where you also have to focus and you don't have to. You mentioned starting 30 companies. I'd imagine you have a lot of opportunities available. Do you have a place where people can go? We have a large audience probably listening, potentially those who are chomping at the bit for either new opportunities or a opportunity or their first opportunity or change because of just new interests or new things that just are grabbing them? Are you hiring across these 30 companies?

1:13:03What do you personally need for new talent in your enterprises? Yeah, if they're listening to this podcast, they probably like the tech companies more than the biotech companies. So OpenCore Ventures has a portfolio on their website. And I think companies always need people who can get things done themselves and are able to go after something by themselves and get it done, get it over the finish line. One of the post hoc founders wrote a great article about stop collaboration. like there's there's a lot of because you now have a team of AIs reporting to you you shouldn't also be kind of trying to partner up as much with other humans like you you have all the ways to make it happen in order to go fast collaboration should never get in the way from making individual progress it should never delay kind of trying to get something over the finish line yourself it's great if people have suggestions and great if you ask for uh if you ask for feedback but but never stop never stop the progress and never delay because you have to coordinate with someone else just use your best judgment and get it over the finish line and i think for for people who are effective by themselves the the world's your oyster well said anything else sid you want to talk about with us or make sure we mention about kilo or anything else that's on your plate that you want our listeners to know before we let you go?

1:14:45I think we, we touched on a lot. This was super fun. Thanks guys. It's always fun, man. It's been, it's been too long. We use this each other more often. I'm glad you're, you're out there doing your thing. You've crossed the chasm it seems of your cancer situation. Obviously you're still out there hunting it. So I assume the treatments will continue. The research will continue and the hunting will continue. Hopefully that, that vaccine or the mRNA treatment you're going to take, 50-50 chance. Hopefully it lands on heads and you can be free from this. But it seems like you're not just surviving, but also thriving, at least from what we can tell.

1:15:20Yeah, for sure. With your many businesses and all your interests. So it's pretty cool. It's been great. And I'll settle for this as long as I'm having a ton of fun pushing all of this forward. And yeah, it was a bit hard to make the time when I was full-time CEO. That's a big job with GitLab and I have a little bit more flexibility in my schedule. So yeah, to be on the show again soon. Absolutely. Sid, always welcome back. It's good seeing you. Thank you so much for sharing your story and sharing your time. Thank you too. Bye.

1:15:54All right. This has been our first interview of 2026. We hope you enjoyed it. Who else should we talk to on the pod this year? And what should we talk about? Did you know we have a request form on the website? we do head to changelog.com slash request and tell us what you want to hear we want to hear from you big thanks to our partners at fly.io and to our beat freaking residents that's breakmaster cylinder for all of our dope beats and thanks to you for listening we appreciate you that is all for now but we'll be back in your ear holes with our old friend matt ryer and his guitar on changelog and friends on friday bye y 'all

1:16:41Thank you.

1:17:15Game on!

From the publisher

We're joined by Sid Sijbrandij, founder of GitLab who led the all-in-one coding platform all the way to IPO. In late 2022, Sid discovered that he had bone cancer. That started a journey he's been on ever since... a journey that he shares with us in great detail. Along the way, Sid continued founding companies including Kilo Code, an all-in-one agentic engineering platform, which he also tells us all about.

More from The Changelog: Software Development, Open Source

All 232 episodes
From GitLab to Kilo Code (Interview)The Changelog: Software Development, Open Source · 1 h 17 min
Listen in VO