Sharing through git

Your team’s context repo is a git repo with a remote, so sharing works the way git does: you (or an agent you ask) commit and push, teammates pull, and history records who changed what. CodeSense shows you what’s changed, what’s incoming and what happened, and pulls for you.

This applies to a shared team. A local-only team has no remote to share through. See Create or join a team.

See what you’ve changed

The Sync button in the left nav switches the tree from the pipeline to your local context changes (choose Back to Pipeline to return). Its badge counts changed files (“N changed files to sync”).

In the sync view, changes are grouped by story and epic, and docs, so you can see exactly what you’d share before you share it. Opening a changed markdown file shows a redline: prose diffs marked up the way you’d review a document, with a before/after toggle.

Get your teammates’ changes

When teammates have published, a pill next to the Sync button shows how many changes are waiting (“N incoming — pull first”).

• Auto-pull incoming changes (Settings → General, on by default) pulls them in the background when they fast-forward cleanly.
• If your copy has diverged from the team’s, pulling is left to you: resolve the merge in your context repo directly, or ask an agent to.

Once pulled, the new context is in your team’s content/. Worktrees get it the next time an agent launches there, or when a running agent calls hydrate_worktree. See Context in a worktree and reverse sync.

Look back at history

In the sync view, the right pane shows History: a timeline of sync commits by day, and the files each one changed. You can also add it from the right pane’s panel menu.

Share your changes

Your context repo is an ordinary git repo, so you share a change with git from its folder, or ask any agent to do it for you. The Sync button only switches the view; it doesn’t push.

cd ~/.codesense/users/<id>/orgs/ledgerline/codesense-context
git add billing/content/.claude/skills/write-migration
git commit -m "billing: add write-migration skill"
git push

Teammates then see it as incoming, and it reaches their worktrees once they pull.

Coming

Agents do the git, not you. An agent picks up your change and commits it, or opens it for review, as your team’s policy says, and asks you when no policy covers it. Every teammate’s CodeSense then pulls the update automatically while it’s running.

Unlocks with agent-managed sharing.

Publish mode

Settings → General → Publish mode chooses between Direct push (the default) and Open a PR. It applies when an agent publishes through CodeSense’s publish tools, not to a git push you or an agent run directly.