CodeSense docs

CodeSense is a macOS app for teams that build software with coding agents. It keeps your team’s context, plans and dashboards as plain files in a git repo, and puts them to work in every repo and worktree your agents touch.

These docs describe what the app does today. Where something is on the way, the page says so in a Coming box and doesn’t describe it as working.

Start here

• Install CodeSense: get the app running and its dependencies checked.
• Your first hour: from a fresh install to agents working on stories in your own repos.
• Key terms: org, team, context, worktree, epic, story and the rest, in one page.

The three things CodeSense does

Context that follows every agent. Write your team’s CLAUDE.md, AGENTS.md, skills and docs once, in your team context. When an agent launches in a worktree, CodeSense copies in the context its definition asks for as real files, hidden from git, and the agent can ask for more with a tool call. Reverse sync, in Beta, lets an agent bring edits made in a worktree back. Read The context repo, Teams and inheritance and Context in a worktree and reverse sync.

Plans agents can execute. Epics are folders and stories are markdown or HTML files with a few metadata fields. CodeSense tracks their status and dependencies, and gives each story its own worktree and branch. Status is a plain field: you or your agents move it, and nothing gates the move. Read The planning model and Worktrees.

Dashboards you author. HTML pages in your context repo become live dashboards over your stories and your agents’ routine results. Read Dashboards and pages.

Popular tasks

• Write a skill once for every repo
• Override a parent team’s skill
• Keep your own Claude Code hooks
• Run your own tools and scripts in a worktree
• Write your first story

The sample project

Examples across these docs come from Ledgerline, a made-up billing product with two repos, ledgerline/web and ledgerline/api, and two teams: platform, and billing, which inherits from platform.