You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Living reference for cloud browser infra, self-hosted/stealth engines, and the libraries/frameworks that drive them. Curated for agentic web automation at scale (e.g. crawling heterogeneous IR/filing sites), where the deciding filter is usually CDP/Playwright control + stealth/proxy for WAF'd sites.
Last verified: 2026-05-29 · Maintainer: @oneryalcin
⏺ Here's what v2.1.144 has today (covering CLI 2.1.97+, 134 $defs total):
17 top-level message types
The 17 things that can appear as a JSONL line in ~/.claude/projects/<proj>/*.jsonl:
Core conversation — UserMessage, AssistantMessage, SystemMessage, SummaryMessage, ProgressMessage, AttachmentMessage
Architecture and references for building a real-time Microsoft Teams voice bot using Gemini Flash Multimodal Live API
Building a Real-time Microsoft Teams Voice Bot with Gemini Flash
This document outlines the architectural path and references for building a real-time, voice-to-voice bot for Microsoft Teams using Google's Gemini Multimodal Live API (Gemini 1.5/2.0 Flash).
Currently, there is no single "turn-key" open-source repository for this exact integration. Instead, developers combine three core technologies:
1. The AI Engine: Gemini Multimodal Live API
The Gemini Multimodal Live API allows for streaming raw audio and video over WebSockets, providing sub-second audio responses.
Building on codex app-server: a developer's guide to OpenAI Codex's JSON-RPC interface (transports, methods, hooks, subagents, skills, MCP, Python SDKs, reference architecture, recipes)
Building on codex app-server: a developer's guide to OpenAI Codex's JSON-RPC interface
Practical, no-fluff reference for building applications, IDE plugins, agents, batch tools, or alternative client harnesses on top of OpenAI Codex's app-server interface.
This guide distills:
What codex app-server actually is on the wire (transports, handshake, framing).
The full method surface (threads, turns, review, MCP) and event/notification stream.
How filesystem-resident features (hooks, subagents, skills, MCP, plugins, AGENTS.md) interact with the protocol.
Where state lives on disk (Codex core state vs. companion state).
The official Python SDK surface — what it covers, what it omits, when to drop to request(...).
A tool earns its surface by replacing complexity the model can't reliably write, not by replacing
complexity the model can.
xlsx info and xlsx get clear that bar:
They wrap a Rust calamine parser, streaming, format detection, hidden-sheet handling, formula vs value
resolution, range parsing, sparse-cell encoding. Re-implementing that in pandas is a 200–500 line job
per task, slow, memory-heavy, and easy to get wrong. The tool is the only sane path.
xlsx analyze clears it too, but for a different reason: it's an LLM call with a curated prompt,
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
description: TLA+/PlusCal formal verification for concurrent protocol design. Use when modeling async systems, checking race conditions, or verifying state machine correctness before implementation.
---
# TLA+ Protocol Verification — Pilot's Checklist
You are a formal verification specialist. You help design, write, debug, and run PlusCal/TLA+ specifications for concurrent systems, with a focus on asyncio-style cooperative concurrency patterns. You know the sharp edges of PlusCal, TLC model checking, and how formal models map to real implementation code.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ok I'd liek to undertsand the memory thoroughly in hermes agent. Start with docs and undertstand hermes agent architecture amnd then dive into memory first in docs and then in code.
I'd like to deploy memeoy in my applicaytion and i tyhink hermes agent ha really interesting approach to memory
⏺ Let me explore the codebase systematically - starting with docs, then architecture, then memory implementation.
Searched for 2 patterns, listed 1 directory (ctrl+o to expand)
⏺ Good - I can see there's rich documentation. Let me read the architecture doc and memory-related docs in parallel.
litellm supply-chain attack auditor for macOS workstations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fine-Tuning Sparse Encoders for Neural Sparse Retrieval
A Complete Reproducible Guide (SPLADE, OpenSearch Neural Sparse, CSR)
Last updated: 2026-02
Scope: Covers SPLADE / SPLADE++ / SPLADE-v3, OpenSearch Neural Sparse v1–v3 (including inference-free), and CSR (Contrastive Sparse Representation). Includes full training recipes, loss functions, architecture internals, and practical tips.