pash

@pashmerepat • 33,235 subscribers

codex @openai | prev @cline | @meta knowledge graph | creator of vault // @usc alum

Shorts

Over the past 6 months, we've rearchitected Cline's agentic loop into a standalone "cline core" gRPC service that runs independently of any editor. This enabled us to decouple from VS code and build - JetBrains (released in GA this week) - CLI built in Go (releasing soon) - Secret project that may be announced soon The CLI is our newest product and will ship without a TUI. Our focus is to release a true primitive. something close to the metal that pipes cleanly into RL environments, CI/CD systems, scripts, and automation workflows. Any "presentation layer" mentioned above can connect to the same running cline core - maintaining full feature parity (e.g. checkpoints, settings, api configurations), context, and conversation state. There's an SQLite-based instance and file/directory lock registry that prevents port conflicts and coordinates graceful shutdowns between paired processes - so you can start up thousands of cline instances in parallel with no conflicts or dangling processes. What's remarkable is that this cline core architecture opens Cline to any interface imaginable: mobile apps, web dashboards, custom tools - all powered by the same intelligent core that understands your codebase.

Over the past 6 months, we've rearchitected Cline's agentic loop into a standalone "cline core" gRPC service that runs independently of any editor. This enabled us to decouple from VS code and build - JetBrains (released in GA this week) - CLI built in Go (releasing soon) - Secret project that may be announced soon The CLI is our newest product and will ship without a TUI. Our focus is to release a true primitive. something close to the metal that pipes cleanly into RL environments, CI/CD systems, scripts, and automation workflows. Any "presentation layer" mentioned above can connect to the same running cline core - maintaining full feature parity (e.g. checkpoints, settings, api configurations), context, and conversation state. There's an SQLite-based instance and file/directory lock registry that prevents port conflicts and coordinates graceful shutdowns between paired processes - so you can start up thousands of cline instances in parallel with no conflicts or dangling processes. What's remarkable is that this cline core architecture opens Cline to any interface imaginable: mobile apps, web dashboards, custom tools - all powered by the same intelligent core that understands your codebase.

59,960 просмотров

Videos

Anya Rossi

sweetdream.ai

SweetDream.ai•Sponsored•Livecam

Watch Anya Live

Anya is streaming live right now! Join her private show and enjoy exclusive content.

Exclusive private shows

1.2k viewers online

Private Show

Join now for exclusive access

Free preview available • Premium content

Boris from the Claude Code team explains why they ditched RAG for agentic discovery. "It outperformed everything. By a lot"

Boris from the Claude Code team explains why they ditched RAG for agentic discovery. "It outperformed everything. By a lot"

851,352 просмотров • 1 год назад

Biggest lesson from OpenClaw is that a good teammate doesn't start from scratch everytime you check in. They remember what was decided, what's still open, and proactively help you. Today we launched heartbeats in Codex: automations that maintain context inside a single thread over time. Instead of each run starting fresh, Codex wakes up in the same conversation, with the history and context it needs already in place. You can also have it schedule its own next steps – just ask Codex. Think about the overhead that quietly accumulates every morning: scanning Slack channels, catching up on email, piecing together what moved overnight. With a heartbeat, you offload that once, and wake up to a brief already waiting in a pinned thread. If you want to try turning Codex into a chief of staff: connect Slack, Gmail, and Notion, and paste the following prompt into codex: Please check Matt Slack Gmail Notion and write me a morning brief every weekday at 9am in this thread. I want you to collapse all the chaos at work into a single note every morning over some coffee ☕️

Biggest lesson from OpenClaw is that a good teammate doesn't start from scratch everytime you check in. They remember what was decided, what's still open, and proactively help you. Today we launched heartbeats in Codex: automations that maintain context inside a single thread over time. Instead of each run starting fresh, Codex wakes up in the same conversation, with the history and context it needs already in place. You can also have it schedule its own next steps – just ask Codex. Think about the overhead that quietly accumulates every morning: scanning Slack channels, catching up on email, piecing together what moved overnight. With a heartbeat, you offload that once, and wake up to a brief already waiting in a pinned thread. If you want to try turning Codex into a chief of staff: connect Slack, Gmail, and Notion, and paste the following prompt into codex: Please check Matt Slack Gmail Notion and write me a morning brief every weekday at 9am in this thread. I want you to collapse all the chaos at work into a single note every morning over some coffee ☕️

119,059 просмотров • 2 месяцев назад

Over the past 6 months, we've rearchitected Cline's agentic loop into a standalone "cline core" gRPC service that runs independently of any editor. This enabled us to decouple from VS code and build - JetBrains (released in GA this week) - CLI built in Go (releasing soon) - Secret project that may be announced soon The CLI is our newest product and will ship without a TUI. Our focus is to release a true primitive. something close to the metal that pipes cleanly into RL environments, CI/CD systems, scripts, and automation workflows. Any "presentation layer" mentioned above can connect to the same running cline core - maintaining full feature parity (e.g. checkpoints, settings, api configurations), context, and conversation state. There's an SQLite-based instance and file/directory lock registry that prevents port conflicts and coordinates graceful shutdowns between paired processes - so you can start up thousands of cline instances in parallel with no conflicts or dangling processes. What's remarkable is that this cline core architecture opens Cline to any interface imaginable: mobile apps, web dashboards, custom tools - all powered by the same intelligent core that understands your codebase.

Over the past 6 months, we've rearchitected Cline's agentic loop into a standalone "cline core" gRPC service that runs independently of any editor. This enabled us to decouple from VS code and build - JetBrains (released in GA this week) - CLI built in Go (releasing soon) - Secret project that may be announced soon The CLI is our newest product and will ship without a TUI. Our focus is to release a true primitive. something close to the metal that pipes cleanly into RL environments, CI/CD systems, scripts, and automation workflows. Any "presentation layer" mentioned above can connect to the same running cline core - maintaining full feature parity (e.g. checkpoints, settings, api configurations), context, and conversation state. There's an SQLite-based instance and file/directory lock registry that prevents port conflicts and coordinates graceful shutdowns between paired processes - so you can start up thousands of cline instances in parallel with no conflicts or dangling processes. What's remarkable is that this cline core architecture opens Cline to any interface imaginable: mobile apps, web dashboards, custom tools - all powered by the same intelligent core that understands your codebase.

59,960 просмотров • 9 месяцев назад

Больше нет контента для загрузки