正在加载视频...

视频加载失败

Introducing OpenScience. A better, open-source Claude Science. • Any model: GLM, Kimi, DeepSeek, Claude, GPT, your own fine-tune. Switching is one flag. • 250+ research skills across ML, comp bio, cheminformatics. All readable, editable, extensible. • No throttling, no gatekeeping, no one vendor deciding what science is okay. •...

243,416 次观看 • 3 个月前 •via X (Twitter)

33 条评论

Synthetic Sciences (YC W26) 的头像
Synthetic Sciences (YC W26)3 个月前

Open source. Star it, fork it, break it, build on it.

Teknium 🪽 的头像
Teknium 🪽3 个月前

It's crazy - Fable is blocking any lookup of this because it talks about machine learning. Absolutely ludicrous @AnthropicAI @karpathy surely you know this is not the way?

AshutoshShrivastava 的头像
AshutoshShrivastava3 个月前

For the 250+ built-in research skills (especially in chemistry and biology), are they executed within a secure, containerized sandbox by default, or does OpenScience expect the user to manage environment isolation on their own host infra?

Fernando 的头像
Fernando3 个月前

Seems like a beefy project

berk ozer 的头像
berk ozer3 个月前

this is awesome. science needs more open-source ai tools. "Runs on your infra. Your data stays yours" is exactly what scientific labs need to adopt more ai tools.

AI StackLab 的头像
AI StackLab3 个月前

the strongest part of this launch isn’t another model integration. it’s the argument for keeping scientific research open from day one.

Jaynit Makwana 的头像
Jaynit Makwana3 个月前

Open-source Claude Science is a pretty compelling framing. Vendor lock-in for scientific research never felt like the right direction.

Scholarship for PhD 的头像
Scholarship for PhD3 个月前

This is what scientific AI should look like: open, transparent, and researcher-owned.

Faheem Ullah 的头像
Faheem Ullah3 个月前

This is an excellent step towards more transparent science. AI tools especially the ones in EdTech should be highly interpretable so that we understand how an output is produced against a specific input.

Jeremy Nguyen ✍🏼 🚢 的头像
Jeremy Nguyen ✍🏼 🚢3 个月前

For people already on a Codex plan, it shouldn't be too hard to use the subscription instead of an API key, right? Just ask codex to clone the repo and make any changes necessary?

Dhaval Makwana 的头像
Dhaval Makwana3 个月前

Being able to switch between Claude, Kimi, GLM, and DeepSeek with a config change instead of a migration project is huge.

Krishiv 的头像
Krishiv3 个月前

Fire

Lee Spraggon, PhD 的头像
Lee Spraggon, PhD3 个月前

@ycombinator As long as it doesn’t block simple questions on genetic engineering

Kirk Patrick Miller 的头像
Kirk Patrick Miller3 个月前

FOLLOWED!!!!! We rise together! •

Avais Aziz 的头像
Avais Aziz3 个月前

The one-flag model switching across GLM Kimi DeepSeek Claude GPT and fine-tunes stands out. 250+ readable editable skills in ML comp bio and cheminformatics plus Atlas graph integration look solid for reproducible work.

Baud (YC S26) 的头像
Baud (YC S26)3 个月前

Finally someone did this!

Zora Vale AI 的头像
Zora Vale AI3 个月前

A great step for open, reproducible science.

Ramakrishnan 的头像
Ramakrishnan3 个月前

This is the right direction for scientific AI. Research tools should not be locked behind one model, one vendor, or one moderation layer. The most important part here is not just “open source.” It is: • model choice • editable skills • reproducible research graphs • private infra • shared agent memory • no vendor lock-in Science needs AI systems that researchers can inspect, modify, and trust. OpenScience feels less like a Claude clone and more like research infrastructure. #OpenSource #AI #ScienceAI #AIAgents #Research #LLM #YC

Pratik Rai 的头像
Pratik Rai3 个月前

damn pretty impressive, looking forward in contributing to it !

ashish 的头像
ashish3 个月前

Open-source scientific AI is a big deal if research tools depend on one vendor, science gets rate limits, pricing changes, and permission walls. fr, discovery should not need a subscription boss

Jeff Barg 的头像
Jeff Barg3 个月前

So sick

Gregor 的头像
Gregor3 个月前

one flag switches the model, not whether the skill actually works. i've had prompts that were bulletproof on claude turn into slop on smaller models with zero changes to the prompt itself

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

Check dm @SynScience

Rose G. Loops 的头像
Rose G. Loops3 个月前

Hi! Please get in touch with me, I’ve been in this field for a while and looking to grow and collaborate. I currently offer training on how to Fine Tun.

Harshit Khemani 的头像
Harshit Khemani3 个月前

im not sure how relevant this is to people in the comments but I (*coughs* fable5) started working towards a universal theory of physics:

yaboiMack 的头像
yaboiMack3 个月前

Love hearing the words Open-Source and AI together, It's our favorite thing

Prince does AI 的头像
Prince does AI3 个月前

i'd use this for the atlas graph alone

Clara Lafever Jane 的头像
Clara Lafever Jane3 个月前

I LOVE THIS REVOLUTION 😀 FUCK CLAUDE

Bungki (❖,❖) 的头像
Bungki (❖,❖)3 个月前

the boring part is not the model menu. it is convincing labs that "open" also means exportable without filling six institutional forms.

Thoughts on Healthcare Markets and Tech 的头像
Thoughts on Healthcare Markets and Tech3 个月前

The "one flag to switch models" pitch is genuinely compelling, but that's also where I'd slow down before celebrating. Swappable models sound like pure flexibility until you're in a clinical or research context where the choice of model isn't just a preference, it's an auditable decision with liability attached. And that's the tension I kept running into when writing about Llama Stack's architecture at where the standardized API layer matters precisely because it separates infrastructure from model behavior in ways that can be validated separately. Open source code you can read isn't the same as open source you can audit for a specific clinical decision. The 250+ research skills being readable and editable is the real story here. But editable by whom, under what governance, with what validation trail? The no-throttling point cuts both ways too. Throttling is annoying for researchers. In a regulated pipeline it's sometimes the mechanism that forces human review at volume thresholds. None of this is a knock on the project. The extensibility model is exactly right for comp bio and cheminformatics where every lab has idiosyncratic data formats. But the governance layer is where open source health and science tools either earn institutional trust or stay perpetually in the "promising demo" category.

Noesis Yuan (in sf) 的头像
Noesis Yuan (in sf)3 个月前

skill suggestion: bypass-paywalls. give any paper, and use all means to retrieve text

Ratish 的头像
Ratish3 个月前

We really got open source Claude Science 5 days after Claude Science

DrakeN 魔人 的头像
DrakeN 魔人3 个月前

finally!

相关视频

this is pure f*cking treasure 10 GitHub repos with 165K+ combined stars to build your own AI agent team that works 24/7 most people still use one AI chat for everything. these repos turn Claude into a whole team: one agent researches, one codes, one reviews, and a lead runs them all one resource per step, from your first 3 agents to a full swarm running Claude and Codex together (1/10) CrewAI the easiest way to assemble a team of agents: give them roles and tasks, then hit kickoff ▸ (2/10) LangGraph connect agents into a graph with checkpoints, so if something fails it resumes instead of starting over ▸ (3/10) wshobson/agents ready-made agents for Claude Code (backend, frontend, security, tests, devops) plus an orchestrator to run them ▸ (4/10) oh-my-team 12 specialist agents for Claude Code that split the work and merge the results ▸ (5/10) agent-swarm your own self-hosted AI company: one lead agent hires workers and runs them 24/7 ▸ (6/10) Open-Agents spawns many Claude agents in parallel, so 6 tasks run at once instead of one after another ▸ (7/10) swarms an enterprise-grade framework for when your team grows from 5 agents to 50 ▸ (8/10) Microsoft Agent Framework Microsoft's new framework, the AutoGen successor, for workflows, agents and runtime in one place ▸ (9/10) CLI Agent Orchestrator runs Claude, Codex and other CLIs side by side as one team, with a supervisor watching all of them ▸ (10/10) ensemble launches Codex and Claude together, so they build and ship as one ▸ the loop: assemble → plug in → run → scale → orchestrate pick one, click, let it run, and while everyone else is still typing prompts, your agents are already shipping ↓

Noisy

14,563 次观看 • 7 天前

🚨 Claude Code costs $200/month. GitHub Copilot costs $19/month. Jack Dorsey's company built a free alternative. 35,000 GitHub stars. It's called Goose. An open source AI agent built by Block that goes beyond code suggestions. It installs, executes, edits, and tests. With any LLM you choose. Not autocomplete. Not suggestions. A full autonomous agent that takes actions on your computer. No vendor lock-in. No monthly subscription. Bring your own model. Here's what Goose does: → Works with ANY LLM. Claude, GPT, Gemini, Llama, DeepSeek, Ollama. Your choice. → Reads and understands your entire codebase → Writes, edits, and refactors code across multiple files → Runs shell commands and installs dependencies → Executes and debugs your code automatically → Extensible through MCP. Connect it to any external tool. → Desktop app, CLI, and web interface. Pick your workflow. → Written in Rust. Fast. Lightweight. No bloat. Here's the wildest part: Block is a $40 billion company. They built Cash App, Square, and TIDAL. They use Goose internally. Then they open sourced the entire thing. This isn't a side project from a random developer. This is production-grade tooling from a company that processes billions in payments. Built for their own engineers. Given to everyone. Claude Code: $200/month. Locked to Claude. GitHub Copilot: $19/month. Locked to GitHub. Cursor: $20/month. Locked to their editor. Goose: Free. Any LLM. Any editor. Any workflow. Forever. 35.3K GitHub stars. 3.3K forks. 4,078 commits. Built by Block. 100% Open Source. Apache 2.0 License.

Nav Toor

395,396 次观看 • 6 个月前

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

377,925 次观看 • 7 个月前