sheremetyev
Joined 15 years ago
Karma
135
Submissions
42
Member since
Jun 24
Recent submissions
Comment · 4 months ago
I'm running Codex/Claude in native macOS sandbox with access just to the project folder (plus read-only access to Git repo), and expand to other folders if necessary - https://github.com/sheremetyev/sandfence
Comment · 4 months ago
Linux VM doesn't run native macOS toolchain and requires copying files back and forth
Comment · 4 months ago
> I don't want to give it "dangerous" access to my entire mac
I'm running Claude/Codex inside native macOS sandbox, configured with a simple script - https://github.com/sheremetyev/sandfence
always in "bypass permissions" mode - it works until task is solved, sometime 1 hour or more (which includes running tests etc)
Comment · 6 months ago
I've built multi-agent workflow on JJ workspaces - independent from specific agent. You can run Codex, Claude or anything else - https://www.visualjj.com/learn/parallel-ai-agents
Comment · 11 months ago
You can use VisualJJ to rebase via drag & drop, split interactively etc.
https://www.visualjj.com - I'm building it and would appreciate any feedback!
Comment · 1 year ago
JJ is great - we actually build on it! Branching uses JJ for commit-graph storage, then layers live-sync and automatic conflict resolution on top. It started life as the VisualJJ extension for VS Code and Cursor and is now available as a standalone app as well, so any editor can benefit.
Comment · 1 year ago
Branching continuously synchronises your Git repository with GitHub and automatically resolves conflicts on rebase - removing manual pull/push, management of branches, and conflict resolution. The exact merge strategy is evolving - we are starting with deterministic "take incoming" and testing structural and AI-assisted options. The guiding principle: automate the routine merges, leave full control in developer's hands when it matters.
You are right that some situations do require careful inspection of changes to avoid "garbage". In others cases you might not care about internals if behaviour looks correct, e.g. for a prototype.
Our "progressive depth" approach in Branching aims to serve both cases - default automatic behaviour, and the option to do Git operations manually when you need to - including editing conflicts manually or with tools like Mergiraf. That way the busy path stays fast, and the careful path is still just plain Git.
Comment · 2 years ago
by default snapshotting happens on each jj command
additionally you can enable automatic snapshots when files in the working copy are updated: https://martinvonz.github.io/jj/latest/config/#watchman
Comment · 2 years ago
for me important argument in favour of JJ over Sapling was "first-class conflicts" - JJ stores conflicts in the history and allows you to resolve them later, while Sapling forces you to resolve conflicts at the point when they happen
Comment · 2 years ago
You are not alone :) For Microsoft Word you might find Writage plugin useful (https://www.writage.com) - supports all basic Markdown syntax, tables etc. and recently added support for math formulas.