正在加载视频...

视频加载失败

I’ve been waiting for something like this. Using multiple AI agents sounds great until you have to keep giving each one the same context. Jarvix Jarvix is built to solve that: It carries your selected context across the AI tools you already use and brings everything together in one...

23,225 次观看 • 2 个月前 •via X (Twitter)

32 条评论

Elizaveta Zabrodskaya 的头像
Elizaveta Zabrodskaya2 个月前

@Jarvixdotlive Love how it keeps everything in one spot

Z-Coder 的头像
Z-Coder2 个月前

@Jarvixdotlive This looks interesting

Eyisha Zyer 的头像
Eyisha Zyer2 个月前

@Jarvixdotlive Shared context is the real unlock for multi agent workflows

Chidanand Tripathi 的头像
Chidanand Tripathi2 个月前

@Jarvixdotlive Jarvix looks really interesting

Usama Sha 的头像
Usama Sha2 个月前

@Jarvixdotlive Shared context across agents is what makes the multi agent setup actually practical.

Rohit 的头像
Rohit2 个月前

@Jarvixdotlive Shared context makes AI agents much more useful. This looks really promising!

Robert Smith 的头像
Robert Smith2 个月前

@Jarvixdotlive Amazing share

Mr Nikola 的头像
Mr Nikola2 个月前

@Jarvixdotlive Great

Artists Voyage 🔶 的头像
Artists Voyage 🔶2 个月前

@Jarvixdotlive amazing as I think Jarvix Search + shared context is a practical combo.

James 的头像
James2 个月前

@Jarvixdotlive That agent team mode sounds really useful. I hate having to repeat myself to different bots.

Csaba Kissi 的头像
Csaba Kissi2 个月前

@Jarvixdotlive It's like a multi-agent Jarvis

Kevin Parker 的头像
Kevin Parker2 个月前

@Jarvixdotlive Amazing

Fakhr 的头像
Fakhr2 个月前

@Jarvixdotlive This one’s new for me

Hussain Hashim | Building SundayBack 的头像
Hussain Hashim | Building SundayBack2 个月前

@Jarvixdotlive @aaliya_va this is actually huge. i've been juggling context issues forever with different AI tools. definitely gonna check out jarvix.

Javeriya Ahsan 的头像
Javeriya Ahsan2 个月前

@Jarvixdotlive Having to explain the same context to every tool is probably the most annoying part of using multiple agents. This fixes a very real headache. XD

Javeria 的头像
Javeria2 个月前

@Jarvixdotlive Keeping the human in control makes this even better.

Muhammad Ayan 的头像
Muhammad Ayan2 个月前

@Jarvixdotlive Jarvix said no more context déjà vu 🤣

Tarique Sha 的头像
Tarique Sha2 个月前

@Jarvixdotlive great to see as multiple agents working from the same project context removes so much repetitive briefing.

Luqman Ali 的头像
Luqman Ali2 个月前

@Jarvixdotlive Awesome

Aaliya 的头像
Aaliya2 个月前

@Jarvixdotlive Thanks

Haider Anis 的头像
Haider Anis2 个月前

@Jarvixdotlive This is powerful

Charlie Hills 的头像
Charlie Hills2 个月前

@Jarvixdotlive oh woooow shared context across agents 👀

Parul Gautam 的头像
Parul Gautam2 个月前

@Jarvixdotlive this is new for me

Amit 的头像
Amit2 个月前

@Jarvixdotlive will check it out.

Jack AI 的头像
Jack AI2 个月前

@Jarvixdotlive Nice work buddy

Liam | AI Tools & News 的头像
Liam | AI Tools & News2 个月前

@Jarvixdotlive Shared context between agents just makes sense.

HarriStack 的头像
HarriStack2 个月前

@Jarvixdotlive Finally, an AI that stops making me re-explain my entire life story to every new agent.

Shohan 的头像
Shohan2 个月前

@Jarvixdotlive Amezing share

marium 的头像
marium2 个月前

@Jarvixdotlive This sounds like a huge time saver! I'm always looking for ways to streamline my workflow.

Zayan 的头像
Zayan2 个月前

@Jarvixdotlive Shared context, smarter AI workflows.

H A J R A 的头像
H A J R A2 个月前

@Jarvixdotlive Shared context across multiple AI agents is a game changer. 🔥

Branding Waves 的头像
Branding Waves2 个月前

@Jarvixdotlive like that you still approve what happens next. Shared context across agents is useful, but keeping the human in control makes it much more practical.

相关视频

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 次观看 • 5 个月前

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

378,296 次观看 • 7 个月前

150,000 small business owners and employees are already using Teamily AI. Today, we're opening it to everyone: your personal AI agent and an entire team of AI agents, ready to work for you and your business. Meet Teamily AI 2.0 — the human–agent platform where you and always-on AI agents get work done together in one unified, context-aware space. We've taken four major capabilities to the next level to help businesses build and grow faster: 1. Real-Time Human–Agent Collaboration. Humans and AI agents work together across chats, meetings, studios, and communities to research, analyze, and create websites, dashboards, videos, slides, documents, and more. 2. Unified Context & Living Memory. One connected context across conversations, meetings, channels, and workspaces. Your AI agents remember, learn, and understand you over time—delivering smarter, more personalized results. 3. Custom Agents & Agent Teams. Create and orchestrate AI agent teams in one click. Manage agents through Agent Workspace, connect them to Telegram, WhatsApp, iMessage, and Slack, or integrate them into your products via Agent API. 4. Intelligent Multi-Model Routing. Our proprietary models work alongside leading models from OpenAI, Anthropic, Gemini, DeepSeek, Qwen, Kimi, MiniMax, and more—automatically routing each task to the best model across text, image, video, and voice. Teamily AI 2.0 is built for every business owner, every employee, and every customer. America has 36 million small businesses. 98% have fewer than 20 employees. Many are teams of one. At Teamily, we believe AI should democratize opportunity, giving everyone the power to achieve more. You have the business. Now you have the team. Try Teamily AI 2.0 for free →

Teamily AI

4,367,105 次观看 • 22 天前

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

194,990 次观看 • 6 个月前

The more agents and projects you have running, the harder it gets to keep track of everything through chat alone. This is where Hermes Kanban comes in. Here's how Hermes Kanban works, why it's worth using, and how I'd recommend setting it up: Chat is where you work with an agent. Kanban is where you manage the work across agents. Hermes Kanban gives you a visual dashboard for tracking tasks across your agents and projects. But it's much more than a task board. Here's what you can do with it: • Create tasks and assign them to specific Hermes agents. • Track what's ready, running, blocked, or completed. • Set dependencies so tasks wait for other work to finish. • Coordinate handoffs between specialized agents. • Review progress and see where something needs your attention. And with the dispatcher, Hermes can pick up tasks that are ready to run and launch the appropriate agent to handle them. Now, here's something I'd recommend: **Create a separate Kanban board for each major project.** For example: 📌 Content production Research → Drafting → Review → Assets → Done 📌 Software development Bugs → Features → Testing → Review → Done 📌 Business operations Research → Waiting → In Progress → Blocked → Done Hermes supports multiple isolated boards, so each project can have its own tasks, workspaces, logs, and agent workflows. You can also connect a board to a Hermes Project to keep the work tied to the right project context. The more work you hand off to Hermes, the more valuable this becomes. Instead of digging through conversations trying to figure out what every agent is doing, give each project its own board and manage the work from one place. 🎥 Video credit: Tom

Hermes Release Watch

27,640 次观看 • 21 天前