注册并分享邀请链接,可获得视频播放与邀请奖励。

与「SLACK」相关的搜索结果

SLACK 贴吧
一个关键词就是一个贴吧,路径全站唯一。
创建贴吧
用户
未找到
包含 SLACK 的内容
🚨 BREAKING: Apple filed for a PRELIMINARY INJUNCTION against OpenAI AND asked a federal judge to put them under forensic supervision "Apple respectfully moves the Court for a preliminary injunction to stop THE THEFT OF ITS TRADE SECRETS" Apple filed NINE sworn declarations, a 28-page memorandum and a concurrent motion for expedited discovery What Apple now says, under oath: Chang Liu: 8 years at Apple, now OpenAI "Member of Technical Staff" exploited an authentication bug to steal Apple trade secrets "on AT LEAST FIVE SEPARATE OCCASIONS" from February to April 2026, WHILE working for OpenAI Liu downloaded "THOUSANDS OF PAGES of Apple's most sensitive trade secrets" The stolen files, NAMED: >DisplayNotes.key — "several hundred pages" on Apple's custom display power development program >Architecture analyses. Fabrication decisions. Testing results >Engineering data for an UNANNOUNCED Apple product: 'touch, display, and power systems" >Final.key + V2.key — compilations of two undisclosed Apple R&D projects >and those are "only four of the dozens of proprietary documents Mr. Liu stole" Liu fed OpenAI "a steady stream of Apple proprietary information that he actively concealed" Liu also "coached Yu-Ting "Alyssa" Peng, then still INSIDE Apple, how to access and copy files from Apple workstations "to avoid trouble with the security team" and directed her to communicate with him on the encrypted LINE app "to avoid detection" Tang Yew Tan: 24-year Apple VP, now OpenAI's Chief Hardware Officer, "used an Apple internal project codename for an unannounced product to elicit still more trade secrets from job candidates." Tan's own messages, quoted in the motion: >"Just like last time, bring some parts you worked on" >"mlb, battery, shields type of stuff is interesting" OpenAI recruiter, quoted: "No, you won't sign anything at the exit interview. If they do ask you to sign anything, let me know asap." APPLE TOLD FEDERAL JUDGE: >"OpenAI knows its misappropriation is wrong and has tried to conceal it." >"This is not a case of 'mere hiring'... it is a case of repeated instances of deliberate theft." Apple says OpenAI went after its SUPPLIERS: >OpenAI "directed a trusted Apple partner [name redacted] to perform [Apple's proprietary metal finishing] process for them, knowing it was proprietary to Apple... because they were involved in this partnership while at Apple." Apple put its own Surface Finishing Manager, Jackie Hughes, under oath to prove it. Apple named ELEVEN MORE former Apple employees at OpenAI — beyond Liu, Tan, and Peng — Fourteen people total. Apple also filed a concurrent motion for EXPEDITED DISCOVERY demanding depositions: - Liu. Tan. Peng. - A fourth unnamed OpenAI employee - Plus OpenAI itself, under oath, through Rule 30(b)(6) Apple has asked a federal judge to put OpenAI under forensic supervision RIGHT NOW: >Forensic inspection of ALL OpenAI devices >ALL cloud storage, Slack, email >Including anything that "previously contained" Apple data — deleted included Demanding the "first available hearing date," citing "imminent threat" to its trade secrets. APPLE: > "The harm is happening now — every day that passes without an injunction allows OpenAI to embed their knowledge of Apple's stolen information into its hardware development efforts." Hearing: October 1, 2026. Judge Edward J. Davila. ITS HAPPENING
显示更多
0
41
190
30
转发到社区
at openai, many people hook their chatgpt up to slack. people really don't like when a coworker's chatgpt contacts them asking for help with a task, even when they'd be perfectly happy doing that same work if asked by that coworker. reinforces how much people care about human relationships and helping each other, and want AI to give time back — or enhance time together — rather than become a layer separating people.
显示更多
0
346
5.1K
177
转发到社区
YC开源了他们内部使用的多Agent协作框架,名字叫QM。 QM的定位介于个人助手和企业级系统之间:市面上大多数Agent是按“个人助手”来设计的。QM从一开始就是为公司场景设计的,每个员工有自己独立的工作空间,互不干扰,同时又能在频道、群组、项目里跟Agent协同工作。每个人、每个团队都有各自的记忆、文件、密钥视图、权限、定时任务和持久沙箱。 YC自己在会计、法务、活动、工程等多个部门都在用QM,甚至QM本身的开发也用QM来做。项目原生支持Slack和Web两端。 核心的能力: · 触发器:支持定时任务(cron)和webhook · 记忆与共享文件:个人和团队两种作用域 · 连接器:连接内部知识、文档、数据库 · Agent浏览器支持 · 可分享的Web应用:能直接搭内部小应用并发布给指定人 · 多人协作项目 Github:
显示更多
0
18
135
27
转发到社区
We’ve decided to open-source a multi-agent harness we use internally at YC. We call it “QM” and it’s meant to be easy to customize, like Hermes or OpenClaw, but useful for a whole company. We use it across accounting, legal, events, and engineering (including building QM itself!). The whole project is under an MIT license. It is cloud-first and has Slack and web UI natively.
显示更多
0
320
8.8K
902
转发到社区
给关注了半年的agent team 交份作业。 这是一篇2w字长文,也是一份 Agent Team 的最佳实践。 01 一个 Agent,是怎么变成多个 Agent 的为什么真实工作会把 Task Agent 推向 Long-running Agent;为什么一个越来越好用的 Agent 最后又必须分化;多个 Agent 出现以后,瓶颈为什么会转移到 Human。 02 先让“谁负责什么”离开 Human 的脑子Agent 怎样获得稳定身份、Domain 和 Scope;Human 与 Agent 怎样查询当前 Team 的责任结构;真实协作又怎样逐渐沉淀为 Organization 与 Collaboration。 03 让 Agent 自己开始协作Agent Message 带来了什么变化;一个 Agent 怎样把工作直接交给另一个 Agent;为什么 Agent 沟通不是一次把一切说完。 04 Message 负责沟通,Topic 负责收口当工作跨越多个 Agent、多个 Turn 和多天以后,怎样保留唯一的当前版本;Responsible、Participant、Artifact 和 Needs You 分别解决什么问题。 05 Overview:让一支持续变化的 Agent Team 变得可治理当 Human 不再阅读每个 Agent 的全部过程,怎样从更高层观察 Team;怎样发现等待、积压和瓶颈候选;为什么治理关注的是工作流动,而不是让每个 Agent 看起来都很忙。 06 Agent Team 怎样进入真实的外部关系为什么把 Agent 接入 Slack、飞书还远远不够;Agent 对外以后,身份、角色、信任、权限和现实后果为什么必须被分别治理。 07 CodexLoom 在织什么Multiple Agents 与 Agent Team 的真正分水岭是什么;Human 在 Team 中的新位置是什么;为什么需要稳定的 Agent 和动态的 Team。
显示更多
0
45
460
91
转发到社区
What is PUMPING now?🔥🚀🚀🚀 #DroverInu# #hydrachain# #BTC# #RICH# $CKOM $FLOKI #BABYDOGE# $KIBA $DOG #KIZUNA# $NEIRO $PONKE #HMMM# #DONS# #BLUESPARROW# #AFRO# #wDOG# #TARDI# #SLACK# #VSTN# What did I miss?
显示更多
0
58
47
22
转发到社区
“The only job left is to understand what you don't like, put it into words, and tell the AI.” Here’s my new episode with @jxnlco (DevEx at OpenAI) where he showed me how he uses Codex throughout his workday, including how to: → Set up a chief of staff for Slack and email → Turn past sessions into new AI skills → Give long-running projects verifiable goals Some example Codex use cases from Jason: “I want you to read the past week of Slack messages I’ve written and make a skill to figure out how to talk like me.” “Turn this thread into a heartbeat. I want you to check my emails, my Slack, my Linear, and tell me what I need to prioritize.” “Codex can find a booking ticket and check into the flight for me and text me the boarding pass to my phone.” Jason wrote the official OpenAI handbook on how to get the most out of Codex, so don’t miss this episode. 📌 Watch now: Thanks to our sponsors: @RiversidedotFM: All-in-one AI studio for podcasts and video Google AI Studio: Build apps with Nano Banana, and more
显示更多
0
20
212
15
转发到社区
Buzz is not a slack killer. It’s much bigger. It’s the first proper multiplayer agent harness. The network effects of who wins at that layer will decide where value accrues as models commoditize. Very impressed @jack
显示更多
0
25
528
32
转发到社区
吴恩达团队推出的开源 AI 桌面应用,让 AI 不只是聊天,而是直接交付完成的工作成果,直接完成文档、日程、邮件等日常工作任务。 集成 25+ 常用工具(Slack、GitHub、Jira、Notion、Gmail 等),能从 Slack 中 OpenWorker 发起任务,也支持定时自动化。
显示更多
🚀 OpenWorker is here. An open-source AI agent that does the work—not just the chat. 🤖 📄 Draft reports 📊 Build spreadsheets 📅 Update calendars 💬 Send Slack messages Bring your own API key and use GPT-5.6, Claude, Gemini, DeepSeek, Kimi, and more. @AndrewYNg @rohitcprasad
显示更多