Hacker Newsnew | past | comments | ask | show | jobs | submit | 0x008's commentslogin

Why not use something like Temporal to recover state?

OpenClaw doesn't play well with SDKs like that. It expects to be able to run on a full machine (or container), to execute commands, to write files to disk. If we wanted we could fork and run something like this but we want to stay as close to the OSS as possible.

The problem is that you are looking at the code. /s

Of course they would be possible we could just turn the rest api into a cli.

This is such an usually low signal FUD post for HN. I know I am not adding anything of value here either, but I couldn’t help myself. Please post something with more substance here.

We all notice a shift in the general perception of the SaaS industry. People are afraid, massive change is coming. But that is obvious from all the posts in news outlets, on x, on Reddit etc.

Thus far it’s just a massive hype. The technology has the potential to switch up the business, for sure, but now apart from frontier labs for everyone else it’s just eating money. No company has lost clients due to being replaced by some autonomous agent.

Don’t get me wrong, the technology has the potential, and it will improve, and we will see massive changes. Money will flow to different entities (cloud providers? New players? Who knows). But technology still needs to be shaped into a useful product. Even for coding (undoubtedly the most mature use case for AI agents) the agents still have to demonstrate they actually safe time and money in the long run. So far it looks like they mostly create more work.


Don't know where it went but there was more text to the op I cannot see now: https://web.archive.org/web/20260206225501/https://news.ycom...


The skills can be specific to a repository but the agents are global, right?


I like the lazycommit+lazygit combo.

https://github.com/m7medVision/lazycommit


care to share?


  #!ruby
  
  if ARGV.size < 1
    puts "Usage: wz path"
    exit
  end
  
  # Get current working directory
  current_dir = "#{Dir.pwd}/"
  # puts "Current directory: #{current_dir}"
  
  # Run git worktree list and capture the output
  worktree_output = `git worktree list`
  
  # Split output into lines and process
  worktrees = worktree_output.split("\n")
  
  # Extract all worktree paths
  worktree_paths = worktrees.map { |wt| "#{wt.split.first}/" }
  # puts "Worktree paths: #{worktree_paths}"
  
  # First path is always the root worktree
  root_wt_path = worktree_paths[0]
  
  # Find current worktree by comparing with pwd
  current_wt_path = worktree_paths.find do |path|
    # puts "Path: #{path}"
    current_dir.start_with?(path) 
  end
  
  if current_wt_path == root_wt_path
    zoxide_destination = `zoxide query --exclude "#{Dir.pwd}" "#{ARGV[0]}"`.strip
    puts zoxide_destination
    exit 0
  end
  
  current_dir_in_root_wt = current_dir.sub(current_wt_path, root_wt_path)
  Dir.chdir(current_dir_in_root_wt)
  current_dir = "#{Dir.pwd}/"
  # puts "Current directory: #{current_dir}"
  
  # puts "Querying zoxide for #{ARGV[0]}"
  zoxide_destination = `zoxide query --exclude "#{Dir.pwd}" "#{ARGV[0]}"`.strip
  # puts "zoxide destination: #{zoxide_destination}"
  Dir.chdir(zoxide_destination)
  current_dir = "#{Dir.pwd}/"
  
  if current_dir.start_with?(root_wt_path)
    target_dir = current_dir.sub(root_wt_path, current_wt_path)
    puts target_dir
    exit 0
  end
  
  puts Dir.pwd
  exit 0
  
  

Then put this function in your .zshrc:

  # Worktree aware form of zoxide's z command.
  function w() {
   cd $(wz $@)
  }


You can write your stories in csv (or vibe code a tool to do that) and then batch import the CSV.


This move is mostly about expected EU subsidies


Probably it’s not about gaining a competitive advantage but more about bringing down the costs to run frontier models in the EU to a level where it’s a viable enough option to bring down the risk of relying on the US and china entirely.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: