Sivan Kaspi

134 posts

Sivan Kaspi

Sivan Kaspi

@sivank

building @igptai, the email intelligence API that gives AI agents actual memory. DMs open for builders hitting the email context wall. https://t.co/PYs9d0ZJAb

Katılım Şubat 2009
277 Takip Edilen55 Takipçiler
Sivan Kaspi retweetledi
iGPT
iGPT@iGPTai·
iGPT Skills are live! Connect, ask, get answers grounded in your real email and Drive. No more pasting threads, summarizing chains, or briefing the model on who matters. Skills cover sales, finance, customer success, recruiting, operations, and more. github.com/igptai/skills
English
0
2
3
65
Sivan Kaspi retweetledi
iGPT
iGPT@iGPTai·
Want to know why your AI hallucinates even when you give it the context? It's probably using RAG. RAG chops content into chunks and pulls the ones that look most similar to your question. That works for documents, but email isn't a document. Email keeps copying itself into every reply and buries the current state under quoted history. So the model sees real text and reaches the wrong conclusion. iGPT reconstructs the thread first and returns what actually happened, with citations back to the source igpt.ai/blog/why-rag-f…
English
0
1
3
17
Sivan Kaspi retweetledi
signüll
signüll@signulll·
every paradigm humans built like finance, communication, time management, all of it has to be reinvented from first principles for agents. if you really think about it the systems that were built weren’t necessarily designed around the underlying problem.. they were designed around human constraints around the problem which are limited attention, slow reading, status signaling, the need to make things comprehensible to other humans, etc. if you strip those constraints, nearly 80% of the scaffolding that exists collapses. what you’re left with is the actual function, which is almost always smaller than the ritual around it. the transition is going to be fascinating for the economy, for how people interact, & for what we refer to as “work” today even means.
English
43
34
382
18.9K
Sivan Kaspi retweetledi
Sam Hogan 🇺🇸
Sam Hogan 🇺🇸@samhogan·
most of tooling around llms was built for a world that largely doesn’t exist anymore RAG, GraphRAG, Multi Agent Orchestration, ReAct frameworks, prompt management/versioning tools, LLMOps tooling, eval tools, gateways, finetuning libs, etc all obsoleted in in the last 3 months
English
157
58
1.2K
395.1K
Sivan Kaspi retweetledi
signüll
signüll@signulll·
there are likely ~100 ppl alive today that deeply understand all of these together: product instinct, what makes good software, design, technical depth, a real model of ai, the psychology of a single user, the shape of culture, team building, the ability to motivate, & the narrative gift to make any of this actually legible to normal peeps. in consumer, where the tam is pretty much everyone, that combinatorial scarcity is the leverage. ~100 against 8 billion. pure asymmetry.
English
110
136
2.2K
147.7K
Sivan Kaspi
Sivan Kaspi@sivank·
Prompt 5: "Which 3 customers on my biggest accounts have gone quiet in the last 3 weeks? Show me the threads and the last message from each." (This one needs your email connected through @iGPTai) 4.7 can reason across hundreds of threads now, but it still needs clean input to work with, which is what iGPT gives it in one API call. The churn signal buried in your inbox surfaces before your QBR, not after.
English
0
0
0
23
Sivan Kaspi
Sivan Kaspi@sivank·
Prompt 4: "Rewrite this email but leave the second paragraph exactly as-is." 4.6 would "improve" the paragraph you told it to leave alone. 4.7 does what you actually said. You stop fighting the model over what not to touch.
English
1
0
0
19
Sivan Kaspi
Sivan Kaspi@sivank·
Opus 4.7 dropped this week and it's a real step up from 4.6. It reads screenshots properly, follows instructions exactly how you wrote them, and can handle long jobs without falling apart halfway through. Here are 5 prompts that actually use what's new. 🧵
English
1
1
3
77
Sivan Kaspi retweetledi
iGPT
iGPT@iGPTai·
Your agent can now reason across Google Drive in one API call. Another datasource alongside email and attachments. Together they give your agent the full picture. - Compare two versions of the same doc and pull what actually changed. - Check whether what was promised in one doc shows up in another. - Answer a question that spans forty files without adding them into the context window. iGPT handles the retrieval, structuring, and context assembly with ~20x fewer tokens.
English
1
1
3
28
Sivan Kaspi retweetledi
Benji Taylor
Benji Taylor@benjitaylor·
Making something people love is mostly making something you love and hoping the overlap is real
English
340
1.3K
8.4K
871.9K
Sivan Kaspi retweetledi
Garry Tan
Garry Tan@garrytan·
If your memory dies when your harness dies, you built the harness too thick. Memory is markdown. Skills are markdown. Brain is a git repo. The harness is a thin conductor — it reads the files, it doesn't own them.
Harrison Chase@hwchase17

x.com/i/article/2042…

English
74
198
2.2K
450.1K
Sivan Kaspi
Sivan Kaspi@sivank·
This framework is missing a category. All four types of state here are things that accumulate through AI interaction. But most organizational intelligence isn't being created by agents, it already exists. Email threads, attachments, decisions people made months ago across dozens of messages. That context is already yours, the problem is no agent can access it properly. Using iGPT you can pull structured, attributed context from all of that with one API call, works underneath whatever harness or model you're on. No lock-in by design.
English
0
0
0
126
Sivan Kaspi retweetledi
Aaron Levie
Aaron Levie@levie·
Security another great example of a job category that is about to have its Jevons paradox moment as well. “And counterintuitively, I think better AI tooling for security will increase the demand for security talent, not decrease it. Autonomous exploitability automates the proving step, but it doesn't automate the response. More real findings surfaced faster means more triage, more remediation, more architectural decisions that need human judgment” AI is going to generate 100X more code, and along with that, there will be an enormous increase in security discoveries. AI is the only way to triage all of these new threats and risks, but an expert still will be needed on the other side to manage the process. Going to be a massive category of opportunity for talent.
Tal Hoffman@talhof8

x.com/i/article/2043…

English
35
59
378
119.9K
Sivan Kaspi
Sivan Kaspi@sivank·
This is great for the accumulated stuff, preferences, interaction history, cross-session recall. But there's a whole category of context that isn't memory at all. The decisions that already happened in email threads, the attachments with the actual numbers, the commitments people made three months ago. Your agent doesn't need to "learn" that over time, it's already there, it just can't access it.
English
0
0
0
139
Sivan Kaspi
Sivan Kaspi@sivank·
Calling it the "chat era" is interesting for something that's been around for maybe three years. I don't think we're leaving it behind, I think agents are just adding a layer on top of it. Chat stays because it's great for thinking, exploring, asking a quick question. Agents handle the structured, repeatable work. But the part that keeps tripping people up is "process data." Agents can call tools and trigger workflows fine. Getting them to actually understand what's in your communication data, the threads, the attachments, the decisions that got made across months of back and forth, that's still where most of them fall apart. @iGPTai handles that part. One API call, and the agent gets structured, attributed context instead of raw threads. Who said what, what was decided, what's still open. The "process data" step stops being the bottleneck.
Aaron Levie@levie

Another week on the road meeting with a couple dozen IT and AI leaders from large enterprises across banking, media, retail, healthcare, consulting, tech, and sports, to discuss agents in the enterprise. Some quick takeaways: * Clear that we’re moving from chat era of AI to agents that use tools, process data, and start to execute real work in the enterprise. Complementing this, enterprises are often evolving from “let a thousand flowers bloom” approach to adoption to targeted automation efforts applied to specific areas of work and workflow. * Change management still will remain one of the biggest topics for enterprises. Most workflows aren’t setup to just drop agents directly in, and enterprises will need a ton of help to drive these efforts (both internally and from partners). One company has a head of AI in every business unit that roles up to a central team, just to keep all the functions coordinated. * Tokenmaxxing! Most companies operate with very strict OpEx budgets get locked in for the year ahead, so they’re going through very real trade-off discussions right now on how to budget for tokens. One company recently had an idea for a “shark tank” style way of pitching for compute budget. Others are trying to figure out how to ration compute to the best use-cases internally through some hierarchy of needs (my words not theirs). * Fixing fragmented and legacy systems remain a huge priority right now. Most enterprises are dealing with decades of either on-prem systems or systems they moved to the cloud but that still haven’t been modernized in any meaningful way. This means agents can’t easily tap into these data sources in a unified way yet, so companies are focused on how they modernize these. * Most companies are *not* talking about replacing jobs due to agents. The major use-cases for agents are things that the company wasn’t able to do before or couldn’t prioritize. Software upgrades, automating back office processes that were constraining other workflows, processing large amounts of documents to get new business or client insights, and so on. More emphasis on ways to make money vs. cut costs. * Headless software dominated my conversations. Enterprises need to be able to ensure all of their software works across any set of agents they choose. They will kick out vendors that don’t make this technically or economically easy. * Clear sense that it can be hard to standardize on anything right now given how fast things are moving. Blessing and a curse of the innovation curve right now - no one wants to get stuck in a paradigm that locks them into the wrong architecture. One other result of this is that companies realize they’re in a multi-agent world, which means that interoperability becomes paramount across systems. * Unanimous sense that everyone is working more than ever before. AI is not causing anyone to do less work right now, and similar to Silicon Valley people feel their teams are the busiest they’ve ever been. One final meta observation not called out explicitly. It seems that despite Silicon Valley’s sense that AI has made hard things easy, the most powerful ways to use agents is more “technical” than prior eras of software. Skills, MCP, CLIs, etc. may be simple concepts for tech, but in the real world these are all esoteric concepts that will require technical people to help bring to life in the enterprise. This both means diffusion will take real work and time, but also everyone’s estimation of engineering jobs is totally off. Engineers may not be “writing” software, but they will certainly be the ones to setup and operate the systems that actually automate most work in the enterprise.

English
0
1
2
75
Sivan Kaspi retweetledi
Aaron Levie
Aaron Levie@levie·
Another week on the road meeting with a couple dozen IT and AI leaders from large enterprises across banking, media, retail, healthcare, consulting, tech, and sports, to discuss agents in the enterprise. Some quick takeaways: * Clear that we’re moving from chat era of AI to agents that use tools, process data, and start to execute real work in the enterprise. Complementing this, enterprises are often evolving from “let a thousand flowers bloom” approach to adoption to targeted automation efforts applied to specific areas of work and workflow. * Change management still will remain one of the biggest topics for enterprises. Most workflows aren’t setup to just drop agents directly in, and enterprises will need a ton of help to drive these efforts (both internally and from partners). One company has a head of AI in every business unit that roles up to a central team, just to keep all the functions coordinated. * Tokenmaxxing! Most companies operate with very strict OpEx budgets get locked in for the year ahead, so they’re going through very real trade-off discussions right now on how to budget for tokens. One company recently had an idea for a “shark tank” style way of pitching for compute budget. Others are trying to figure out how to ration compute to the best use-cases internally through some hierarchy of needs (my words not theirs). * Fixing fragmented and legacy systems remain a huge priority right now. Most enterprises are dealing with decades of either on-prem systems or systems they moved to the cloud but that still haven’t been modernized in any meaningful way. This means agents can’t easily tap into these data sources in a unified way yet, so companies are focused on how they modernize these. * Most companies are *not* talking about replacing jobs due to agents. The major use-cases for agents are things that the company wasn’t able to do before or couldn’t prioritize. Software upgrades, automating back office processes that were constraining other workflows, processing large amounts of documents to get new business or client insights, and so on. More emphasis on ways to make money vs. cut costs. * Headless software dominated my conversations. Enterprises need to be able to ensure all of their software works across any set of agents they choose. They will kick out vendors that don’t make this technically or economically easy. * Clear sense that it can be hard to standardize on anything right now given how fast things are moving. Blessing and a curse of the innovation curve right now - no one wants to get stuck in a paradigm that locks them into the wrong architecture. One other result of this is that companies realize they’re in a multi-agent world, which means that interoperability becomes paramount across systems. * Unanimous sense that everyone is working more than ever before. AI is not causing anyone to do less work right now, and similar to Silicon Valley people feel their teams are the busiest they’ve ever been. One final meta observation not called out explicitly. It seems that despite Silicon Valley’s sense that AI has made hard things easy, the most powerful ways to use agents is more “technical” than prior eras of software. Skills, MCP, CLIs, etc. may be simple concepts for tech, but in the real world these are all esoteric concepts that will require technical people to help bring to life in the enterprise. This both means diffusion will take real work and time, but also everyone’s estimation of engineering jobs is totally off. Engineers may not be “writing” software, but they will certainly be the ones to setup and operate the systems that actually automate most work in the enterprise.
English
254
646
5.3K
1.8M