joefreeman

16 時間前議論

I've been building a text editor. It uses a server-client model, with native/terminal/web clients using a shared (local) server instance. It integrates LSP/tree-sitter/ripgrep/Git/etc, and has a concept of 'workspaces' to easily switch between projects.

I spend less time in an editor now, but it's been satisfying being able to take features I've enjoyed from other editors and customise - and it's oriented a bit more towards exploring code than editing. Key-bindings are arranged such that bare letters are for motions, Shift- variants are then used to extend selections, Ctrl- bindings are for buffer mutations, and leader-prefixed bindings are application level (e.g., opening pickers).

https://github.com/joefreeman/aether

joefreeman

3 か月前議論

The workflow orchestration tools I've used over the past have been consistently unsatisfying, so I've been building my own. With Coflux (https://coflux.com), workflows are defined declaratively in plain Python with decorated functions (tasks). Workers connect to the orchestration server and get assigned work - calls to other tasks get intercepted and then re-scheduled by the server onto (potentially different) workers. Tasks are executed in pre-warmed, isolated processes, with low latency.

Beyond standard features (retries, caching, timeouts - enabled with attributes on the decorator), Coflux supports more novel features - like suspense (where a task can choose to go to sleep and get restarted when a result it depends on becomes available), memoisation (where steps within a run are aggressively cached so that you can re-run steps in a workflow without re-running upstream steps), and the ability to re-run a step in a different workspaces (with updated code, or in a different environment).

It turns out this works great for implementing agentic systems - you can provide references to tasks as tools to an LLM call and have the AI drive - tasks can be easily sandboxed. And Claude is very capable of using the CLI to interact with the orchestration server to submit workflows, investigate failed runs, make updates to workflows and re-run steps.

I'm trying to make sure it's easy to try out - there's a self-contained CLI that can be used to start the server (a single Docker container), run worker processes, and then interact with the server. The dev mode automatically restarts the workers as you make local changes. There's also a hosted UI for observing runs in real-time, where you can see the execution graph, access logs/metrics/assets/etc - it works without creating an account - the browser interacts with your orchestration server directly.

コメント