# GenSpark: AI Memory and Hardware Strategy

**Podcast:** Chain of Thought | AI Agents, Infrastructure & Engineering
**Published:** 2026-09-17

## Transcript

Intelligence is what we leverage to get work done.
We built a FSD vehicle so that you don't even need to touch the steering wheel.
All you need to do is just articulate the destination.
We get you there.
Our view is meeting notes are just start points of work.
It's not the end point.
Majority of these devices out there, they basically say, here's your meeting note, and my job is done here.
Well, we say our job is getting started here.
LLMs are geniuses with goldfish memories.
New sessions are a blank slate without supporting infrastructure.
My guest today is building the AI workspace and hardware to provide LLMs with all the context they need.
Wen Sung is co-founder and COO of GenSpark, which went from launch to $250 million in ARR in about a year, recently shipped their first piece of hardware, a card-thin meeting recorder, which I have in my hand right here, and open-sourced an entire AI-native office suite.
When GenSpark has been busy taking on a hard problem, aligning AI-enabled software with hardware, because you clearly see a new way for people to collaborate with AI agents that includes a hardware interface.
How do you think we should be altering our approach today to work with AI?
First off, Conard, thank you for having me here.
Super excited to be here, and you ask excellent questions.
So today's world, to what you just said, on the one hand, You know, majority of the AI applications out there, if you interact with them, you ask them for answers, for tasks, geniuses with goldfish memories.
They don't know you every time you have the prompt all over again.
So we believe the AI should interact with human beings just like how we interact with each other.
That's why we believe it is important for the AI to have memories.
Not only that, they should also be able to...
tap into the world that we literally live in the physical world instead of just being trapped with whatever's already been digitized.
I mean, some of the most important conversations we have in our lives are in-person conversations in real life.
So why shouldn't our AI agents being able to tap into those content and then do real work for us?
That is what motivated us to break the grounds and then...
essentially unlock some of the most important information that is going around in our lives with the Second Brain Notes.
I have one myself here as well.
Awesome.
Yeah, I'll say thank you, by the way, for letting me have a review copy of the Second Brain Notes.
It's been very fun to test it out.
And before we get too far into the conversation, I do want to say a quick thank you to our presenting sponsors for the episode as well.
In jest, Walrus Memory and Zfix, who are sponsoring Season 4 of Chain of Thought, you can find their links in the episode description.
And G2i has joined them as well, helping teams find specialized engineering talent.
But we're here to talk about GenSpark today.
And GenSpark's seeing this incredible growth across the last year or two since you've started the company.
You've been open sourcing quite a few tools.
You've been building on top of hardware.
And you brought up memory and context for agents, which I think are very important themes that we talked a lot about on this show.
How do you think about this infrastructure that you're constructing around the models?
And when should we be focusing on the outputs of these in-person conversations versus inputs that maybe we're making from documentation and these other sources?
So if I got your question accurately, Connor, you're asking about our consideration behind the technology architecture?
Yes.
Yeah.
Yeah.
So look, our view of the world is this, Connor.
Frontier Labs, they've done amazing work to build the next generation intelligence.
Now, those are engines.
What we do is we build.
vehicles, we build cars around the engines for our users, for our customers.
Intelligence does not equal to work results or the output.
Intelligence is what we leverage to get work done.
Now, Frontier Labs, a lot of good partners of ours, OpenAI, Anthropic.
Google, we work with all of them.
We also work with open-weight model hosts, providers like Fireworks, Fel, Together, all of them.
Now, these folks, they've done great work, especially Frontier Labs, to allow us to see the possibilities, and they would build products as well.
But their focus is always, how do we make the model smarter?
How do we make the models solve partial differential equations?
That is important.
That is where the raw power come from.
But for the 1 billion plus global knowledge workers, for people like you and me, you might be very technical.
I'm a mechanical engineer by training, so I don't know how to code.
So for me to maneuver a Fable 5 and trying to get the full power out of it, I don't know how.
Even when I'm using some of these work applications.
If I'm asking one of these applications to give me a presentation, a five-page slide deck, it's going to ask me to download 10 things from GitHub.
I don't even know where those things are.
I don't want to think about that sort of stuff.
I want all my tools, applications, everything's already packaged up.
I just want to interact with my agents like how I'm talking to a very competent, fast, tireless associate of mine.
So that's what we do at Jamespark.
We don't even build a Formula One racing car for you.
We built a FSD vehicle so that you don't even need to touch the steering wheel.
All you need to do is just articulate the destination.
We get you there.
That's how we think about it, Raji.
I love that you brought up Formula One, even though it's not exactly what you're doing.
It is immediately what I thought about when you're like, oh, we work with engine providers.
We built the chassis.
We built the car around it.
But to your point, you're building a self-driving car, hopefully.
Yes, exactly.
Yeah.
To that, a little bit on the technology maybe.
We have a three-layer kind of a technology architecture.
On the bottom, exactly as you pointed out, we actually released the world's first mixture of agents tech architecture.
Today, we sit on top of 70-plus models.
of each different model to do different things.
The models that are good at reasoning and planning, we use them to come up with the work plan for a project.
The models that are good at coding, we ask them to code.
For example, if you're building a presentation, we ask them to code in HTML first.
And the models that are good at image video, we use them for multimodal media stuff.
And there are obviously the models that are fast and cost effective.
We might leverage them to kind of kind of visualize data or do something else.
So it's a combination.
On top of that, we also built out 150 plus in-house tools to put them in place so that models could call on these tools under the right context to accomplish the real world work.
On top of that, we also paid to get access to premium data sets, PitchBook, Crunchbase, S&P, all the good stuff.
Like we're in conversation, for example, with the Unlight SE because they have a data business that is called ICE.
And we're also talking to the Wall Street Journal because they have a data business as well.
So our target audience are the non-technical knowledge workers.
We want to make sure they not only have their own data, they not only have access to the web, they also have access to these premium data sets to ground and align the output so that they're reliable, useful, and ready to go.
You can't just rely on what people say on Reddit.
That's one big part of the source of information, but that's not 100% what you can rely on.
You've got to have access to all of it.
Data integrity definitely matters.
I had a great conversation with the CTO of Thompson, Reuters recently about their Thompson One model and basically how they're leveraging legal AI data in that framework.
And really what enabled them to fine tune and train their model much more cheaply was the fact that they run Westlaw, which has annotated case law for all this different content.
And to your point, I think things like PitchBook, et cetera, can give you a huge leg up.
And I have to point out too something, you kind of skated past this, but...
I actually did not realize that GenSpark were the originators of the first commercial mixture of agents architecture that was out there.
I knew together really led the research around that back in 2024.
But, you know, as I'm hearing you talk and looking it up, like, that's very cool to see that you were the first commercial users of this.
Yeah, because very early on, we realized, you know, For the knowledge works, for our target audience, they don't care about what model is behind us.
They just want the results.
And everything else is a means to an end.
So we're like, okay, we got to put this all together.
That's what drove the model orchestration and architecture.
Well, I also think you're a little too humble here because you're calling yourself non-technical, but you spent, what, a decade leading Y Combinator-backed.
analytics company that was acquired.
You have a doctorate in mechanical engineering.
I think you picked up a few tricks along the way.
But I hear you for sure on the idea that we want to extend ourselves with agents because I agree.
I don't want to spend all my time fine-tuning the little bits and pieces of whatever I need for my Git stack to get a repo over the line.
I want my coding agent to handle those problems for me.
I want to never have to worry about a merge conflict ever again in my life.
I want an agent to handle that for me.
Yo, when it comes to...
the user how users would experience AIs these days.
Human beings, we're smart.
It's pretty easy for us to tell if I'm burning the tokens, wasting my time teaching AI and not getting what I want or it's like one prompt.
Oh, this is exactly what I need.
Right.
So to that one key thing is how people do eval.
Our good partners, Frontier Labs, when they do eval, they truly focus on the analogies.
And when it comes to our e-mail, it's the autonomous recursive learning algorithm that grades every interaction between our users and our product that but it focuses on if the users are getting the boardroom ready materials, if the users are getting the.
So, for example, personally, for me, I haven't solved one partial differential equation in my last 10 years running.
last company, but I wrote a lot of business emails.
I built a lot of financial models.
I did a lot of documents, put together a lot of sales proposals.
I care about if my sales proposal responded appropriately to every point that RFP had in it, right?
So those are the reliability, the accuracy, the usability of the work output.
That is what our eval benchmark system focuses on, right?
So those things make a huge difference.
Let's talk about that work output.
So if I have my second brain note and I am recording a meeting, what should I expect from the follow on through that?
You have a variety of agents built in the platform.
You've got a transcript that comes out of it.
A meeting produces an hour of audio.
What does it actually look like as a memory a week later when an agent needs it?
And what kind of workflows are you running across it?
That is such an excellent question, Carter.
So exactly to what you said.
There are many devices out there on the market that you could use to get the audio file, to get the transcript or even a summary.
Someone would even say that I don't need anything else.
I could just use my iPhone.
Right.
But I know.
Yeah.
Well, if you do do that.
First off, iPhone is not designed for a boardroom setting.
It will pick up one-on-one conversations very clearly, but there's a lot of...
It's not designed for that, and battery would just drain out in two hours.
But a lot of these devices solve that problem, including Jazz Park second brain node.
It could go on for 35 hours.
But our view is the meeting nodes are just start points of work.
It's not the end point.
Majority of these devices out there, they basically say, Here's your meeting note and my job is done here.
Well, we say our job is getting started here.
You could now talk to your meeting notes in a way that, hey, turn everything.
in this meeting into a sales proposal into a pricing model into a roi analysis for our clients or turn this into a presentation i could send to the client or to the master to follow up on all the things that you know they asked about or hey based off this meeting notes do all the research around the topics that we left open Come back with a collection of the answers for me and then turn that into something.
So we carry our users and our customers end to end.
That's one thing.
Secondly, when it comes to the memory piece, this new piece of meeting note is now going to be incorporated into your second brain, which is a layer of the semantic understanding.
we've built for you so that your Jenspark super agent would be able to tap into when it when it's working for you.
Instead of like every time you got to introduce yourself, you got to introduce your work, you got to ask the agent to say you're the world's best expert in this and that.
No, none of that.
Your preferences, how you do things, who is your most important relationship?
What are your work priorities?
Is this meeting some of the most important things you got to follow up this week or it's okay to follow up next week?
It remembers and understands all of that.
It synchronizes this new piece of context into the Jen Sparks holistic understanding of you as a person.
And it's all human centric.
It does work around you, not the other way around.
So information retrieval is information collection.
Retrieval is only the start point.
The true understanding is what the second brain does for you when it comes to that layer.
And then the real power comes from the output, right?
Like you can just turn your meeting notes directly into results.
Now, on top of that, beyond individuals, if you are an enterprise company, say if you have...
a thousand team members on your business team or your revenue team.
Now you finally have the opportunity toward the end of month to say you can ask the 1,000 second brain notes.
Okay, so what are some of the good meetings we had in the past month?
What is the market asking for?
How can we do better from a product perspective to make our customers' lives a lot easier?
What are the opportunities?
What are the risks?
And the way it works is you don't have to kind of send a fleet of biz ops analysts into each of those meeting notes to look through, copy and paste, and then do none of that.
You can just ask Jens Mark Second Brain to answer those questions directly because not only you have access to data, but you also have a full layer of understanding of what's going on as well.
as individuals, as organizations.
Season four of Chain of Thought is presented by Walrus Memory, the portable memory layer for AI agents.
Your agent has learned your code base and how you work.
Now you want to use that context in another tool.
Exporting a file gives you a snapshot, but what happens when the context changes?
Walrus Memory is a portable memory layer that lets your agent store context for later use across tools.
Python and TypeScript SDKs plus native MCP support let you connect it to your agents no matter where they are.
You said who can read and write, so sharing context doesn't mean opening up your whole memory store.
If you are building across tools or model families, take a look at Walrus Memory.
Learn more at walrus.xyz slash C-O-T.
That's walrus.xyz slash C-O-T.
So if I'm understanding the approach here correctly, You know, what you're calling the second brain is essentially memory and quite a bit of context, but it's not the whole context layer.
It's this base layer of a lot of information, though.
You then have an intelligence layer that's running across that and helping pull up the right information, make decisions, run workflows.
You then have your tool suite, which is, you know, your open source tools, other tools you want to bring in.
It also includes a lot more like content and context.
And then you have like a collaboration layer where you're both collaborating with agents and then also with teammates.
Is that a correct understanding?
I love that.
Yeah.
So, Carter, essentially the models, the tools and the premium data sets, those three things packaged up as we call it the execution layer.
So those are the arms and legs of your agents that will do things with the intelligence from the models, obviously.
Now, to examine what you said, now we have built out the memory layer.
which enables you to interact with Genspark in a way that this is a breakthrough for us, right?
Like the agents know, they know you intrinsically.
Not only you can get understanding from, you know, it could get understanding from your work, from the meeting notes, it would tap into your emails, it could tap into your drive, and all of these information on an ongoing basis when they refresh the memory layer of the second brain of yours.
It will refresh itself and it will have new, better understanding of you on an ongoing basis as well.
And it's holistic.
It's not limited to the launch system.
If you work in sales, it could tap into your CRM and truly understand the latest dynamics of your pipeline.
It may also, you know, if you have, you know, kind of trade-offs to make next week, do I go to this conference or do I focus on this client?
Just nail down this lead or this opportunity.
It could understand where you are and then actually work with you to your preference, to your priorities, not just limited to the meeting notes.
Now, on top of that, one thing you pointed out is our collaboration layer, which is also a new capability we've built out of our 6.0 package, which is called Gen Team.
So basically, it's kind of an instant message, kind of an experience, but not only you can talk to your team members.
you can create and interact with your AI agents, team members, and you can ask for work output.
And all of them could have the level of understanding of you to the extent you allow them to tap into those data sources.
And if you allow them to tap into your second brain, they know you instantly.
Fun story, I was in Bora Bora with my family for about 10 days because my kids, they have their summer vacation and we took them out.
But I was sufficiently unplugged, but I obviously couldn't unplug entirely.
So every morning I would spend 30 minutes talking to my executive assistant, my AI agent, Chloe, on my gen team.
Verbally, or I could type, but I could call my EA as well and we'll get the work done for the day.
And then I'll get on to the quality of the time with my family.
When I came back, some of my team members, they were like, wait, you were out for...
vacation we didn't even notice that i was unbeat with everything so that's how work can be done these days yeah i didn't bring my labs off i'm curious so you know i've talked to slack recently and they obviously have a big focus on enabling collaboration between agents and humans within slack a huge focus um Do you view Gen Team as competitive to what Slack's doing with agents, or do you view it as something like, oh, we could integrate Gen Team into Slack, or maybe that's something that's already happening?
So both, I'll be honest.
Yeah, I mean, like, we human beings, we get work done a lot of times through talking to each other.
That's how collaborations happen.
And from an experience standpoint, there might be a kind of overlap when it comes to that.
But at the same time, we understand.
So we are working on making GenSpark capabilities, GenTeam capabilities available everywhere.
So we would want our users to be able to call up your GenTeam agents right within Slack.
That's one.
But beyond that, also, if you just wanted your entire AI stack to be on GenSpark, we offer an AI native experience for you.
that you don't necessarily have to go anywhere else to get everything done because our world view is this, Connor.
The world was tool-centric.
Each of us would have to tap into So many different tools, 20, 30, 40 tools.
May it be Microsoft Suites, Google Suites, Slack, Notion, Salesforce, you name it.
All of these things.
And then we do the busy work.
We do the grunt work, copy and pasting, same piece of business context from a piece of meeting note to an email to a Slack message.
We do all of that to get the work done.
Now, with platforms like James Park, you no longer have to do that.
The world is not human-centric in a way that we only need one entry point.
to work.
And that entry point is, say, if it is Jenspark, it's not the next generation of software.
It's the next generation users of software.
So Salesforce went headless.
We're building the head is basically the case.
All you need to do to get work done is talk to your Jenspark agents and the agents would run around to tapping to all of these different systems, system records and or messages, etc, etc, etc, etc.
Get it done for you.
You don't have to go anywhere else.
But if you prefer to be there, you can.
Here, the reality that, for example, Jensbart team lives in is this.
A lot of our enterprise clients, they prefer Microsoft Teams.
That's where their work is done.
We interact with these folks there because they prefer that.
A lot of the Frontier Labs and our partners, the techies, they live in Slack.
We collaborate on model testing and so on and so forth over there.
And then there is a group of people just love.
Google suites, the advertisement agencies that we would work with as clients as they just love Google.
And we have to interact with them over there.
But for me as a human being, I'm like, my head is exploding.
I don't even know when to check what.
And then there's WhatsApp, there's iMessage, clients love you so much that they put you onto their, you know.
So it's all over the place.
And in APEC, like in Japan, for example, we have some major clients.
They love to be on the line.
So you have to be there.
It's a lot.
So we wanted to meet with our customers, our partners where they are, but at the same time, it's too much.
So we have this place where I can just tell my agents, hey, look through all of these platforms.
Give me just a bit and draft the responses for me to wherever they are.
Like maybe email, Slack, Teams, mine, WhatsApp.
I don't care.
You make it happen.
So that is the beautiful experience we can offer.
So that's how we operate internally because luckily we're a global company from day one.
And unfortunately, because of that, you have to deal with so many systems.
Yeah, you get pros and cons for sure.
Definitely challenges that come with the opportunities there.
I'm curious about one thing that I've been thinking a lot about recently, which is how to decide when context or memories are no longer valuable.
What's the approach that...
you're taking to updating memories.
So let's say, you know, two weeks ago, something was true on a sales deal, but now based off of recent meetings or a change in strategy, we've had alterations.
What does it look like to make those updates within Second Brain and within GenSpark's, you know, memory and content architecture?
So today, we basically...
Our desire is twofold.
One, we wanted to make it as painless as possible.
Two, we wanted to make sure it works to the customer's user's preference.
So basically, we allow you to choose if you wanted to load new memories in every day, like you would sleep on it and then you have new memory.
Or if you wanted to do it every week, every month, that's completely up to you.
And you could set this up for different system records.
It could be for your drive, for your email, for your meeting notes, for your Jazz Park project history.
And you can do one-click migration or let's say memory loading from your Notion, from your CRMs.
It's available.
So you could manually trigger it.
You could let it trigger by itself automatically and then turn on this cadence.
It's completely up to you.
We work with your preferences.
Season 4 of Chain of Thought is delivered by Sphix.
We spend a lot of time talking about what agents need in production, and one of the least glamorous answers is events.
Your customers want agent workflows that react to things happening inside your system, which means your API needs webhooks that actually work.
Not just a post request and a prayer.
Retries, ordering, idempotency, replay protection.
Sphix does that as a service, and they wrote standard webhooks.
The spec that Anthropic, OpenAI, and Google bailed against.
So if your API doesn't have reliable webhooks, that's turning into a lost deal.
Join Brex, Drada, Daytona, and many others on Sphix.
Get started at link.svix.com slash C-O-T, or go to the show notes to grab the link.
Qualified startups will get $12,000 in credits, $50,000 for YC companies.
I can't recommend Sphix enough.
I'm a huge fan of their open source project.
I've actually contributed a bit myself.
And they're so easy to integrate with.
I think you'll really enjoy it.
Check out Sphix at link.svax.com slash C-O-T.
And then one of the ways you've obviously specialized all of this is through hardware.
And we've alluded to the second brain note a couple of times throughout the conversation.
But I want to talk a bit more specifically about what that looks like because A, it's less rare than it used to be, but it's still rare for software-first companies to launch hardware.
B, I've heard you say this is just the first hardware piece you're going to launch.
And so I'm interested to know if you'll give us a bit of a preview there.
But let's start first on what you've done today.
You know, we mentioned phones earlier and phones are designed for one-to-one conversations.
They're not necessarily designed to record and understand multi-person conversations.
What was the engineering approach behind the second break note?
And how does it...
What were the decisions that you've had to make along the way to get to where you are?
Yeah.
So look, Connor, such excellent question.
So first off, we understand in real life, we would have conversations in the one-on-one settings, yes.
But we would also have conversations with a group.
We might sometimes want to talk to ourselves.
We're getting a little sprawl.
So we want to cover it all.
The goal is to make sure that the context in the...
real life can be put in place for your agents to work for you as well.
That's why when we designed it, it's not just like the phone has like one microphone and then that's it, right?
Like it's really meant to do this for you.
But then for us, we designed an array of microphones along the edge so it could pick up signals.
If you sit in a big boardroom, if there was a group of people, wherever you sit, we've done testing to make sure that it could pick up everybody.
This voice.
So this is one.
Secondly, as I mentioned earlier, if you use your iPhone to do the recording, you can.
But it is not designed to do that.
One, the battery will drain out in two hours.
Two, obviously it's going to get white hot.
Two, all you get is an audio file.
You would have to do the processing of transcript in it and then turn it into a memory or summary and that does not connect to anything.
So we take care of all of that for you.
You don't have to go through any of the middle steps.
So you can, the moment you tap this button.
It's in there.
A few seconds later after the meeting, you can just open up your Jazz Park application and you can ask questions directly with the meeting notes and then turn it into presentations or AI podcasts.
You know what?
I love this meeting so much so that I wanted the TLDR version of it verbally.
We can have that through Jazz Park.
It's interesting because...
You know, I spoke with Drev Batra at UTORI on this show a few weeks ago, and we talked about their Navigator N2 and N1.5 models, which are designed for browser usage, computer usage.
And what we really talked about was like most of the web will never get APIs for AI agents.
You know, like the top companies are building APIs, we're building agent first, but a lot of the long tail of the web is going to take years, maybe decades to up-level it to be.
design for agents first.
And the physical world today is even more so.
It's not designed for agents to operate with it.
We're having to redesign the meeting rooms like we talked to Neat about a few weeks back.
Do you think about the note almost as like an API for the room you're standing in to enable you to upload the context into your second brain?
I think that's a great way to look at it, Connor.
I think...
Yeah, and to that, I would say right now we're covering the conversations which contains a lot of information.
I wouldn't be surprised if we started to capture image, video, some other modality in the future as well.
I'm not saying we're working on any of that, but I am saying that for all of us, we live in a real world that information comes from everywhere.
And yes, we have our tools, system records, but also, yeah, we're having conversations, we're seeing things, we're hearing things.
So all of those information that human beings can get, AI probably would get.
So without asking you to pre-announce anything, what's your decision framework for what is going to deserve dedicated hardware support versus what stays software?
So that's amazing.
That's an amazing question, because we think about this a lot.
So really, the selection comes from the breaking point of the current digital world and what we need to get done from a work perspective.
So if you go out and then visit a client, you're going to have a conversation.
But if you're just, you know, scribbling down the notes while you're having that conversation, that's hard.
So that's where we see the break.
So we wanted to make sure you can focus on human beings.
Let the AI focus on all the other stuff.
That's kind of how we look at it.
Same thing when it comes to some other scenarios.
Like, for example, right now, a lot of us, we have to...
interact with our AI through typing.
That's fine and dandy.
We've done it for decades.
But this is unnatural for human beings.
We're not born to do this.
This did not exist when our DNAs were formed.
So what we have is our voice.
That's why we have a product called Speakly.
You just talk to your AI.
That's how we should be able to interact.
So we're trying to get as closer as possible.
We're trying to indefinitely approach the very humane kind of characteristics to make it as smooth, easy for us to incorporate all the contexts, work context for our AI agents so that they could truly understand us.
They could learn about us and they could work for us like a fleet of...
Goldman Sachs analysts who know you really well.
That is the goal.
And I imagine that there have been challenges along the way here because hardware is famously where many software companies struggle, whether it's inventory, return, support, firmware.
You ran a SaaS company for a decade.
What did you learn from building a physical supply chain at what, just over a two-year-old AI company?
Well, first off, I wouldn't take the credit.
So to your point, I was running a pure software company.
I know very little about the hardware stuff.
But the beautiful thing is my co-founder, Eric K., before this, they built a company from $0 to $5.5 billion worth.
And that company leveraged the last generation deep learning technologies to build voice AI.
And one of the key products there is a hardware piece.
And they built...
tremendous expertise in designing, testing, building, shipping, and iterating hardware devices.
This first product is actually, I'd say, much simpler than what they built before.
So, yeah, and we have solid engineers to cover all of these areas for us.
And to be honest, the expertise and relationships they've built from the supply chain side of the world in the past decade has been tremendously valuable.
It's yeah, the know-how.
Yeah, I mean, there are many options.
So yeah, yeah, this is kind of us playing to our strength in a way.
Fair, fair.
Another big decision that I'm sure you've had to make along the way has been when to go closed source versus when to open source.
And you open source a full AI native office suite instead of keeping it as a paid feature.
How did you come by that decision?
We wrote a blog about this.
Really, on the one hand, this project was, how do I put it?
A little spontaneous, I'd say.
One of our engineers, he is obsessed with the capability to build tools for people to easily do all the office-related work.
He just had this idea.
We went unlimited tokens policy back in, I think, in March or April.
I can't remember.
But he was like, okay, great.
So he started hacking around.
And then he just thought, hey, I mean, so many people use these sort of tools.
Can we make it not only easy for it to use, but also I could have my own version of it, given that building new things is so...
afford when possible today.
So he started hanging around and then it was one week he spent I think $10,000 worth of tokens and voila the prototype was done.
And we were all surprised how capable it was and we were like okay I mean the world has some solutions out there but we do also know a big chunk of the world one they don't necessarily have access to these things two they can't have it in a way that they prefer.
And three, we believe that the world is pulling away from kind of a tool-centric world, but more into a human-centric world, meaning that for all of these things, you have to have AI natively built in.
So we just wanted to have as many as possible people to be able to benefit from it, to be able to change it to their preferences.
So that's why we released GenOffice, fully open-sourced.
with our agent AIK police built in.
From a business standpoint, I'll be honest, it is to create certain traffic for AIK police so people would see that, oh, hey, you know what?
While I can edit this document, it's great.
I could just ask Jensmark to do all the work.
That's even better.
So that's kind of how we wanted people to experience it.
Yes, you can have the tool, but you'd prefer your agent to work with the tool, not you.
So that's kind of the logic there.
I love it.
And I think it speaks to where we think the future of work is going, which is changing the level of abstraction across what we're doing with knowledge work.
We're already seeing with coding, we're seeing it with math.
We're starting to see it in other areas, though I'll argue that things like writing are far from solved.
If agents with persistent memory are handling busy work end to end, what do you see knowledge workers spending their time on day to day in the coming years?
So the way we look at this, Connor, is that if you look at, so we cater to the, as I mentioned earlier, one billion plus global knowledge workers.
And this group creates 30 to 50 trillion dollars worth of value, according to some of the McKinsey study.
Now, the way we create those value, if you distill it down on an individual level, it's really three things.
We collect information, we process information, we generate output.
Regardless if you work in banking, consulting, advertising, food and beverage, regardless.
As long as you're not working with your hands, you're basically typing in front of the computer and all that, right?
So those are the S's, the core parts of it.
Now, in each of those steps, much of our time, 60, 70, 80% of our time is spent on the busy work.
The work that does not directly generate, leverage creativity or generate strategic values.
It's like we have to do those work to get the real work done.
So our view is...
with agents autopilot a lot of those busy work.
We actually can focus on decision making, handshaking, meeting with making human connections, use our creativity.
Everybody could work like a Jensen one because when the journalists interviewed Jensen, hey, you work hard.
And how do you do that?
Jensen was like, I don't feel like I'm working hard.
People feel like they're working hard because they're working on things that they don't like to spend time on.
When I work, I feel like I'm dreaming.
I'm thinking about what can be, what is possible in the next three, five years.
That is what we want for everybody.
We believe now with this wave of AI breakthroughs, many of us, maybe all of us could have that opportunity to leverage, to tap the full potential out of each of us.
So the tools, the time we have to spend on busy work is no longer the limit of what we can create.
It's ourselves.
So speaking to creativity, as a developer who is building systems for myself, you know, obviously I can use the GenSpark platform.
But if I want to build tools that interact with GenSpark or that work with my second brain node, you know, what can I do today to customize to my needs?
Oh, 100 percent, Akata.
We have a CLI that you've leveraged.
You could just, yeah.
As a matter of fact, this is not only for individual developers.
We just went live with one of the major enterprise companies in the world that their developer teams, they love our CLI capability.
So they just built their...
application on top of our harness in that sense.
So yes, you could put JetSpark anywhere in your world, in your workflows, and enjoy the amazing capabilities we've built out of that three-layer kind of package.
And yeah, take full advantage of it.
Season four of Chain of Thought is presented by Ingest.
Agents in production run long.
They call models and wait on APIs and people.
But the longer agents run, the more they break.
Ingest handles that with durable execution.
You build your agent as steps in TypeScript, Python, and go.
When a step fails, Ingest retries it with exponential backoff and completed steps are saved and skipped.
A run can wait on an event for minutes or for months.
You can trace runs and replay past runs against new code.
And Ingest has built-in observability, evals, and experiments, so you can wrap your agent tools and steps and use it as a full-on agent harness.
The dev server is open source and you can get started for free.
Grab the Ingest link in the description or visit ingest.link slash C-O-T dash pod to get started.
It's definitely a really exciting space, but I also think we should address some of the concerns that I know folks have.
So, I mean, like an obvious one is I live in Washington state.
It's a two-party consent state.
you know, a card in my pocket that picks up voices from a few meters away may concern some people.
What do you see as the line between, you know, a second brain and note taking versus surveillance?
And, you know, what's the advice you're giving to people who are out there using these products day to day?
100%.
So whenever, so we recommend it, whenever I use second brain notes, the consent has to be clear and explicit.
So I would ask for permission.
Hey.
Could I record this meeting?
It's the same thing as when we do it online.
No difference.
And then I will tap this.
And then you see the light will turn on.
So the consent got to be clear and explicit.
The recording is visible.
Right.
And then the data access, the control is to the human being, to you.
Like if you're using second brain notes, you are the decision maker.
You are the automated controller of.
the access, the editing, the deletion of all the information.
That's how it should work.
So we believe that privacy matters a lot.
And the way to use this is no different than how you would use an iPhone to record the ambient environment or how you use an online meeting bot to do the meeting notes.
It's the same thing.
explicit consent, visible recording, and human responsible control.
And speaking of individual control and customization, I also know that GenSpark has launched your own claw, GenSpark Claw.
I'm curious how that interacts with everything else in the stack.
So GenSpark Claw is basically, we got inspired by the open claw kind of framework.
that now not only you can interact with your AI agents within this one place, the AI basically follows you.
You can interact with your agents anywhere you want.
But then the challenge for non-technical folks is that I personally don't know how to set up a Mac mini and run Node.js and update the overclock versions and then keep it all secure and safe.
So we thought, you know what, for people who wanted to...
talk to their agents through WhatsApp or whatnot, you don't have to deal with any of that.
We stacked the whole thing on top of Microsoft Azure Infra.
It's enterprise-grade security and all that.
And we made it so easy that if you wanted to turn on connections between your agent and WhatsApp or Slack, you just click a button.
That's how simple it is to set it up.
So we created that experience.
And basically, your claw lives in this virtual machine environment by Microsoft Azure.
And you don't have to deal with any of that, you know, setting up, maintenance and all that.
You don't have to have an IT team and you don't have to pay $1,400 up front to get it set up.
So that's kind of the premise of it.
Now, I would say, though, claw, not only you can have it just through Jensper Claw now, you can also have it through Gen Team.
which in my view is an even better kind of work environment because with that, I'd say the stability, the performance of the claw is getting operated.
So the claw gave us, I'd say, inspiration.
I mean, today's world, you see disruptors getting disrupted all the time.
We're disrupting ourselves is basically the case.
So yeah, we're constantly...
taking on these new possibilities and turning them into more reliable, useful, and just easy to use technologies for target users.
Because look, AI is happening fast, right?
AI is happening so fast so that Marc Andreessen said AI is already here.
But to his point, it's not everywhere.
He's right.
So we see that gap.
Our view is the world shouldn't be one that only the elite developers in Silicon Valley would have access to the greatest and latest AI and they can just turn magics out of this.
Our view is if there is something that is amazing from a technology standpoint, we want it to, through our technology products, level the playing field for everybody, for billions of people so that you don't have to know how to maneuver those advanced models, but you can...
have the top speed of this engine, just like a Formula One racing car.
But all you need to do is to just say, hey, I wanted to do this.
And then FMSD delivers to you.
That's kind of how we think about this.
That's why when it comes to claw and so on, we wanted to break it down so that, you know, a non-technical person like me, I just say a few words and then voila, it's mine.
It's interesting to look at the areas in GenSpark's approach where you're going very simple, which is like a, I mean, essentially a cheaper version of some of these other like pins that we've seen.
You've seen Humane's pin, Rabbit R1, et cetera.
They're like $700.
And you're saying, look, you know, we want a more affordable, simpler device.
And yet you're also going complex as far as what you integrate with and what you enable.
And another...
element of complexity that has been added to a lot of AI conversations today, and particularly ones around agent memory, is as we start to slide into these deeper conversations about memory, we start talking about consciousness.
We start talking about model welfare.
Anyone who reads Steve Yege's work, I think, has seen a few different perspectives on this.
My general take is that letting agents carry context between sessions is simply correct infrastructure, regardless, whatever you believe about welfare.
I'm curious if you and the GenSpark team have a perspective on welfare for models in the long term and how you're thinking about persistent agent memory, or are you purely focused on, hey, this is what's right for enterprises anyways?
Yeah.
Look, there are a couple of things, Connor.
So first, we believe those are important topics for the entire humanity.
These things are happening in real time.
It's important to, I'd say, have deep discussions around these topics and have solutions collectively for the entire human race.
Now, at Genspark, though, we are a human-centric company, and we're a practical company.
What I mean by that is our worldview is AI is a piece of technology that should serve human beings, first and foremost.
And our work is all around that.
And our work is all around not only AI should serve human beings, it should serve as many as possible, billions of human beings.
That's why we're focused on building technology that is so easy to use.
If you can use a Google search, you can use Jetsmark to get the greatest and latest, most advanced AI capabilities to work for you, especially in a productivity world.
especially in the world where you want to get work done so that you could then work harder and earn more or you could sit back and then relax.
That's all up to you.
We want to create more freedom for each person, each individual.
We want you to feel like you can tap your full potential to create things because Jazz Park would take care of all the busy work, all the grunt work for you.
So that's our focus.
And we have a rather pragmatic view of how to do that.
The products we've developed, we've kind of essentially followed that philosophy that we want to build useful things for human beings.
We believe AI could be extremely useful here for us to do that, to level up.
And that is what we focused on.
Now, we are also a very active member in this entire community.
As I mentioned, not only we work with all the Frontier Labs, we're great partners with Microsoft.
We're great partners with NVIDIA.
pushed out the open-weight model letter.
We co-signed.
When the Open Secure AI Alliance was formed, we were one of the earliest members.
We believe in the importance of having optionality, having open-weight models to advance the entire industry together.
We also believe in the importance of agents, governance, security, privacy, all of these good stuff.
And we intend to contribute when it comes to these rather important.
aspects of this, you know, booming, but still in a baby infant stage kind of AI industry.
That's kind of how we think about this and look at the world.
How big is your human team today?
Obviously, you've seen incredible growth.
We have a lot of agents running around, yes.
Human-wise, we have 70 plus, almost 80 people around the globe.
So, yeah, we're headquartered here in Palo Alto, California, but we do also have a team in Japan that is focused on marketing, sales, customer support, customer success, solutions, engineering, we're for deployment engineering, all that good stuff.
We have a Singapore office and we have a few team members in Seoul, Korea.
We're thinking we're building up possibly our New York office very soon.
Our chief enemy officer and his team is based in New York.
That's our kind of.
New York has 10 million plus global knowledge workers still.
Good place to be.
Yes, yes.
And we're thinking about our next potentially a London office.
And we see great attractions now from the GCC region, from South America.
It's all coming up, Brazil and so on.
So we're thinking about how to essentially have human interactions with our users and customers and communities in these different parts of the world as well.
This episode is sponsored by G2i.
I've said before on Chain of Thought that most teams still treat evals like unit tests.
Write them once, check a box, and move on.
That doesn't hold up once an agent is making decisions.
G2i is about to close that gap.
For over a decade, they vetted and placed engineers at other companies, from startups to FANG.
Two years ago, they turned that same judgment inwards, building their own bench to review our own environments, evals, and training data that models are trained on.
These reviewers know the difference between code that runs and code that's actually good because they've shitted it themselves.
If your team needs that kind of work and doesn't have the engineers for it, check the link in the show notes to bring them in.
Wen, thank you for a wide-ranging and deep conversation.
As we close out, I'd love to get your take on what the future looks like.
We've talked from a variety of angles about what the future for GenSpark looks like, where you see hardware going.
Something we haven't talked about is this.
takeoff we may see from recursive learning and this new wave.
What do you expect to happen in the next couple of years?
And how are you thinking about the future of knowledge work and AI?
I mean, at least for 2027, maybe.
I don't want us to predict too far out unless you want to.
Sure, we'll talk about the full spectrum.
So, I mean, most immediately, what we are seeing today, Connor, I'm sure you're seeing it as well, is innovation is continuously happening on all levels of the whole stack.
New chips are coming out, new models are coming out every day.
And our mixture of agents, our tech architecture, it's a plug and play.
We constantly evaluate.
We constantly get early access from all the Frontier Labs partners.
We constantly evaluate the models from a genic use perspective.
From our use cases, we provide feedback.
And when they release new models, they would quote us, say, Genz Brock said, great things about this model.
You should all use it.
So we do all that.
And we're seeing that models are continuously not only improving from a performance standpoint, but we're also seeing new kind of models coming out, right?
Dr.
Faveh Lab just released their first model.
We're excited about all of these.
I had the opportunity to talk to Dr.
Yan Le Kun back in the RAISE Summit in Paris.
And I asked him, when is your new model going to come out?
And he shared his perspectives on the world models.
We're excited about all of these amazing stuff.
So that is going to continue to happen.
When new models and new model capabilities come out, I would say new possibilities are getting created on all the stacks above.
We're just the excited.
I'll give you one.
So before, so when Genspark, we launched our super agent or all-in-one AI workspace 1.0 last April.
That was only possible.
But before that, we actually worked on a search.
product.
But we knew that we wanted to not only let the AI get information for us, but also to do work.
But for AI to do work for us, they got to be able to reason really coherently.
And that was only possible because the new models came out toward the end of 2024.
So we took full advantage of that.
It's like waves of new breakthroughs.
You can only get...
you know, agentic actions going if the models can reason and then later on they can code really well.
And then you see, you know, even from our own products, AI Slides 6.0 now compared to AI Slides 1.0 is like day and night.
It's just insane.
So we continue to see new possibilities.
Secondly, the new possibilities would come out from harness standpoint as well.
You know, the proof points are being claw now, open claw 2.0, ARMYs.
We view this, now everybody's in a sandbox We see this kind of movement continuously happen so that Not only the models are getting smarter but agents are getting a lot more capable From a tooling standpoint, I think we're fairly ahead of the game there And from a virtual environment, computer user perspective I think we're fairly ahead there as well, like if you try I'm just going to do this play.
If you try Gen Team, you try Grog Bot, you try Buzz, you try them all, I'm very confident you will see the difference there.
That's because how you maneuver the models to use the right tools to build the right agents and let them collaborate with human beings, that makes a huge difference.
We see continued innovation there as well.
Now, with all that, we see continued innovation in memory, in collaboration.
But all this is pointing to one, I'd say one direction, that is the AI agents are indefinitely approaching the kind of endgame of how you would be able to interact with AI is going to be indefinitely approaching how you would interact with other human beings.
A lot of that is happening in the digital world, but we also know that there's the physical AI component there that is progressing as well.
That is what we all see, right?
So that's that.
much for their future, Connor, our belief is this.
When the 60, 70, 80% of the time we human beings today or in the past spent on busy work get pushed down to, I don't know, 20, 30, 10, 5, 0%.
Each of us would have so much more freedom to do a lot more valuable things, so much more freedom to spend time with our families or like people who we love and or our friends.
So that is, there is going to be an elevation of two things.
One, life quality.
Just like if you look back a thousand years ago, you and me, we're probably living a better life than a king a thousand years ago, right?
So that is going to happen.
Secondly, how we're going to create, how we're going to build is going to be on the next levels.
I would, I would, I would dare.
to say, to fathom that if we get to that point, there will be less people working on the specific things that will keep us human beings alive.
Like, yo...
create food or whatnot, but more people would work on things like explore the universe.
We have not gone out of the solar system just yet.
Come on, right?
There will be more than one SpaceX.
There will be more scientific progress that we will understand the world and ourselves a lot better, a lot deeper.
I would be able to maybe talk to the little shark when I saw Embora-Bora.
I don't know.
So, yeah, I'm excited about what is possible.
And then, yeah, yeah.
So that's kind of, yeah.
I love the inspirational view.
I think there is a lot of toil that we can vastly improve on and potentially eliminate or pass off to agents.
and a lot of creativity that we can unlock if we're using AI tools in the right way.
So Wen, it's been fantastic talking to you.
And if you enjoyed this conversation, you're listening, you're watching on YouTube, make sure you drop a comment.
Let us know what you enjoyed.
Let us know what we didn't talk about that we need to address next time we have one back.
And for folks who really love hearing from Wen, where can they follow you and the work of Jensburg?
So I'm on LinkedIn.
I'm on X.
I just searched Wen Sun.
I should pop up.
I think possibly I'm the only one there.
But also, more importantly, my recommendation, please try GenSpark GenTeam.
It is amazing.
Today, all my work starts there and ends there.
I don't get into my email inbox.
I don't go onto my three message platforms.
I just ask my AI agents to triage my email, triage my messages, to write social posts for me.
I'll proofread everything.
Human beings take responsibilities.
There's no question on that.
But otherwise, Internally at Jetspark, we do our product feedback triage with our agents.
We don't have like dedicated PMs.
You close the loop end-to-end between our users.
We build in public.
We have big groups of 500 people for Jets and Office to throw feedback into this.
Our bugs agent or product agent would triage those tickets and assign it directly to our dev.
Our dev would let their agents pick up those issues, push it onto GitHub issues, solve those, test those.
pull it back and then report back.
Full closed loop.
That's how things are getting built these days.
That's how we get over 660 forks out of GenOffice on GitHub.
Yeah.
Amazing.
And I'll say, Wen's content is great on LinkedIn and X, but...
Perhaps my favorite tweet I've seen from him for the last few days is him talking about how much he loves hot pot and his hot pot setup when he's on vacation, where he will even bring his own pot grocery shop and hit the slope.
So definitely recommend checking out WEN.
WEN, thank you so much for joining me today.
It's been a pleasure chatting with you.
Thank you, Connor.