Repository navigation
Conversation
… agent of its own, apart from an installed sesh
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…es a relative folder; AGENTS.md says what's still shared
… the browser install rule and the switch back removes the dev build
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For anyone working on sesh, person or coding agent, who also uses an installed sesh day to day.
scripts/sesh-devbuilds the checkout tobuild/sesh-dev(git-ignored) and runs it withSESH_DB_PATH,SESH_AUTH_SOCKandXDG_CONFIG_HOMEinSESH_DEV_DIR(default~/.local/share/sesh-dev), without a sync or backup folder inherited from the shell. Tried with a throwawaySESH_DEV_DIR: the vault, its backup and the config were all inside it, and sync was off.AGENTS.md: keeping the installed sesh and the dev one apart, and why they shouldn't share an agent; rules for coding agents (a throwaway folder per run, no clipboard, notouchid enableorbrowser installunless asked, stop what you start); what the two still share (the browser extension's helper script, the agent's log, the clipboard,~/.aws); trying a dev build as the installed one (brew unlink/brew link); building, testing and hooks; how changes and releases go.scripts/README.mdpoint to it.