Skip to content
Jensen

Your first session

Everything up to here was setup. This page is one piece of work from start to finish, so you meet the map, a session, a plan, the trace and the git guard as one thing rather than five topics.

It takes about fifteen minutes on a repository you already know.

Before you start

Section titled “Before you start”

You need a project that is open, indexed and trusted, with an assistant chosen. If any of that is missing, Turn Jensen on covers it.

Read the map first

Section titled “Read the map first”

Press Cmd 1 for Project, Alt 1 on Linux and Windows. The map opens at the top altitude, one node per service.

Drill into one service and follow an edge to something it calls. Every edge you see was read out of your source. Nothing on the map was guessed, which is what makes the next step worth doing. See Honest by design.

Start a session

Section titled “Start a session”

Press Cmd 2 for Sessions, then Open a terminal. Jensen creates a git worktree for the session and starts your assistant inside it, so this work cannot collide with anything else in the repository.

The worktree is named after the task and lives in .jensen/worktrees/. See Worktrees for parallel work.

Ask it something only the map can answer

Section titled “Ask it something only the map can answer”

Ask your assistant a question that would normally mean grepping the tree:

Which services call authenticate, and where are the routes it protects?

What good looks like: it answers from the map and cites files, without re-scanning the repository first. If it starts listing directories instead, the context server is not connected. Check Settings, System, Health.

Ask for a change

Section titled “Ask for a change”

Now ask for something small and real, a rename or a guard clause. Your assistant writes a plan to .jensen/plans/ before it edits anything, and the plan opens in its own inspector.

Read it, then Approve. Approving opens the tracking issue, links it in the plan, and assigns it to you. See Plans and objectives.

Watch the work land

Section titled “Watch the work land”

Press Cmd J to open the right panel and pick Trace. Each net file change your assistant makes becomes a point on the timeline, and it stays there for 30 days.

Put one change back

Section titled “Put one change back”

Pick a change on the trace and use Restore before this change. The file returns to its earlier state. This is not git, so nothing was committed, no refs were created, and a later push cannot undo it. See Undo and the session trace.

Meet the guard

Section titled “Meet the guard”

Put a fake credential in a file, stage it, and commit. The commit is refused, from the terminal and from the app alike, because the guard runs from the project’s own git hooks.

Open the right panel on Git, then Versioning. The commit box reads Commit blocked and lists a row per finding. If a match is a false positive, a test fixture or a documented example key, Accept clears that one finding for future commits and leaves every other rule in force.

Delete the fake credential and commit again. See The git guard.

Where to go next

Section titled “Where to go next”