Attach source repositories

Source repositories hold the code your team works on. Your agent or Git CLI prepares and updates their checkouts.

First create or select a team in your local organization. A newly created organization starts empty and opens the existing team-creation view.

Add a repository

Open Source repositories and add a repository. Choose an existing local folder to attach its checkout. The URL option records repository identity for tracking; it does not clone the repository or establish service authentication.

If a checkout is missing, clone it with your agent or CLI first, then attach the folder. CodeSense keeps attached source folders where you put them.

Work locally

Use Changes and History to inspect local edits and commits. CodeSense can create explicit local worktrees for workspaces and hydrate them with context. An attached source checkout is not automatically moved, updated, or republished.

Ask your agent or use Git directly for fetch, pull, push, merge, conflict resolution, or replacing a checkout. Refresh the local view after external changes if necessary.

Stop tracking

Use the repository list’s local removal controls to detach or stop tracking a source. Read any deletion confirmation before removing local data. Detaching an association is distinct from deleting files; keep backups through your own tools.