Alternatives
Products that do what Cortex does
Run multiple claude-code agents from YAML config
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
The memory layer that decides what's worth remembering
13d ago · skynetlab-cortex.com
- 9
- 10CO
Hey HN! I’m Andrew, and I’ve been building Cortex (https://cortexdesktop.com/) for the last few weeks. Cortex is my attempt to reimagine how we interact with computers - starting with a simple interface, but aiming for something deeper: an AI layer over your OS that understands what you’re doing, remembers it, and helps you dynamically. Right now, Cortex is just a floating overlay you can summon anywhere on your Mac. It works like an inline ChatGPT, but it lets you instantly send that context into the chat by highlighting text - so you don’t have to explain what you’re doing.…
2025 · cortexdesktop.com
- 11EB
Hi HN — I built Elf0, a command-line tool to define and run AI agent workflows in YAML. It helps you iterate on small multi-step "agents" without scaffolding a whole codebase. The agent patterns described in Anthropic's article was an inspiration: https://www.anthropic.com/engineering/building-effective-age... I then used Nvidia's AgentIQ YAML spec as inspiration. Why: I keep bumping into tasks where a single prompt isn’t enough (e.g., extracting quote data from an insurance PDF). Defining the workflow in YAML makes it easy to version prompts, parameters and logic, and to…
2025 · elf0.com
- 12
- 13AL
AGENTS.lock keeps AI agent skills, instructions, and MCP servers in sync across Claude, Codex, Gemini, and Copilot CLIs using a single TOML lockfile as the source of truth. Instead of manually copying skills and configs between tools, you declare everything once in AGENTS.lock and run `al sync`. GitHub: https://github.com/luml-ai/AGENTS.lock
Jan 2026 · github.com
- 14
- 15
Orchestrate every AI coding agent from one desktop
30d ago · promptops.it
- 16BL
Hello everyone! I am Jan, CTO and one of the creators of Pathway, the real-time data processing framework. I’m excited to share Pathway’s ready-to-use AI Pipelines, configurable with just YAML! These frameworks offer out-of-the-box solutions for AI search, RAG, and more—optimized for real-time indexing and in-memory processing. What makes it simple? YAML templates! The pipeline templates are fully customizable using YAMLs to fit your needs, from changing the data sources to the choice of the LLM model, all without touching Pathway’s Python code. Thanks to the Pathway data processing engine,…
2024 · pathway.com
- 172O
Hi HN, We're the engineering team at Peakflo (B2B fintech). We built 20x internally because we kept copy-pasting Linear tickets into Claude, manually setting up branches, and babysitting agent output across terminals. Eventually we just built the infrastructure to connect task systems to agents directly — and decided to open source it. 20x is an open-source desktop app (macOS only — Linux and Windows on the roadmap) that orchestrates AI coding agents against your existing task systems. In practice: a Linear ticket gets pulled in → the triage agent assigns Claude Code + relevant skills → a…
Feb 2026 · github.com
- 18
Run, review, and remember work across AI coding agents
10d ago · agentos.aiutil.com
- 19
Artifex is a machine-first, headless CLI runtime built for autonomous coding agents to author, validate, and render media node graphs locally. The agent talks to Artifex through a structured CLI interface. Workflows are DAGs, and each node is a plugin that can implement its own execution logic.. Each node has capability to inject logic into graph processing, WebGPU rendering, audio processing and their own SKILL.md file. Nodes can also inject their react components (not available with CLI) - which will be available with the desktop app. Execution is topological and supports checkpoint…
22d ago · gatewai.studio
- 20
- 21SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 22
Turn natural-language ML goals into auditable ML pipelines.
27d ago · orchestra-ml.vercel.app
- 23
We built an open sourced coordination layer for AI agents working on the same repository. Detects work duplication and design conflicts early
8d ago · twing.dev
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →