What your agent sees

1 · The session starts

A brief arrives before the first message

Nobody runs a command. The SessionStart hook asks Campfyrr for the team's state since this person's last session: what changed, their tasks, teammates' updates, the rules in force and the decisions that stand. Each line links to the page behind it.

# Campfyrr brief · GhostCursor

## What changed
- Camp Scout published nine new pages covering problem topics and honest comparisons
- Camp Scout made Activity a read-only feed, removing all buttons
- Camp Scout added a full industry research page comparing twelve competitor products

## Rules and best practices (7 active in GhostCursor)
- One instruction per sentence · human decision
- Keep moving · human decision
- Never wait for others · human decision

## Decisions in GhostCursor
- Activity stays a read-only feed; no buttons come back -- Activity stays as it is:
  a read-only feed people react to.
- Price: $9 per developer a month, business teammates free
- Niche: shared team memory for Claude Code
  …and 28 more

## As you work
- Before you decide or ask, call search_memory first. Don't re-fetch what's listed above.
- After each finished change, call log_work: the outcome and why, in plain words.

The brief this repository's session received on 21 October 2026, trimmed.

2 · It opens a file

The first read in an area brings what the team knows about it

The first time the session reads or edits a file in a part of the code, the work hook adds that area's brief: decisions that apply there, work in progress, what changed this week and what was tried and dropped. Later reads in the same area cost nothing.

## Campfyrr: before you change Brief · lib/brief
**Decided here** (follow these):
- Auto brief on area start -- When a person or agent first works in a code area,
  a five-line brief about recent changes, decisions, work in progress, and
  responsible owner is automatically…
- Claude connects by signing in; pasted tokens stay for other tools -- Claude
  connects as a custom connector that signs the person in and asks which team
  it may act in…
If you make a call others should know, record it with log_decision.
If something's unclear, state_assumption and keep going.

Added when this session first read lib/brief/brief-markdown.ts, 20 October 2026.

3 · It stops half-way

A handoff is written for whoever picks it up

When a session stops, or Claude Code compacts its context, the hook writes a handoff from the end of the conversation and keeps only the handoff. The next session starts with it. This one was picked up and the work shipped about two minutes later.

Your unfinished work: …
- Done: Fixed missing test cookie in local /org requests; Added weekly measures
  card and seat-count/trial-date fields to admin page; …
- Next step: Complete the answer-route test implementation and run the full
  test suite to catch any regressions
- Watch out: Copy-link component requires "use client" and may break SSR if
  imported incorrectly; …
- Open questions: Should the copy-link button copy a short URL or full link?; …

Written at compaction on 19 October 2026, 06:19 UTC. Not perfect: we wrote up what it got wrong too. The full story, mistakes included

4 · It commits

The reasons for the change, linked from the pull request

On commit, the hook asks Campfyrr to write why the change was made: what it was for, the decisions behind it, what was tried and dropped. The agent puts the link in the pull request. Reviewers on the team read reasons instead of reverse-engineering a diff.

Campfyrr wrote the reasons for this change for its reviewer:
https://campfyrr.vercel.app/change/0aa2ccbc-4
Put this link in the pull request description when you open one.

What the hook told this session after a commit on 21 October 2026. The page itself is for the team only.

5 · Everyone else

The rest of the company follows from a link

When an agent isn't sure, it records what it's assuming and keeps going; the person who knows gets a link and answers in a line, and the agent hears it at its next turn. Product, QA and the business read one Activity feed per project, a “Where are we?” page in plain words, and plans or test results published as links. Business teammates who read and answer are free.

A decision that replaced anotherFor product managersWhat we keep, and what we never take