Teams
Decided once.
Kept by every agent.
Your team’s agents share why the code is the way it is.
As it works
Every call, written down
The agent records the choices that matter while it works, without being asked.
- What was decided, why, and what was turned down, each in its own line of the turn.
- Only the choices a teammate would otherwise undo. Never a rename, never a secret.
- Its author can delete one, right from that line.
- shopSearch threads and files⌘K
make sessions expire when nobody used them
Worked for 52s 2 files edited
- [x]Kept to Ayşe’s decision Keep sessions in Redis · Oct 3
- [x]Recorded decision Sessions expire after 30 idle days · you asked
- [x]Recorded decision Last seen is written once a minute · its call
Idle sessions now end after 30 days, and the next read signs the user in again. They stay in Redis, as Ayşe decided.
Ask for a change, / for commands, @ for files
AgentOpus 5.5main · Acme
Your branch
Only what’s in your code
A decision binds once the commit that carries it is in your history. Git decides, not the agent.
In your code
Every agent on this branch follows it, and says whose call it was.
Not pulled yet
It’s on the upstream. Pull, and it binds.
On other branches
Never followed. You’re warned when your work touches the same files.
Yours, not in a commit yet
Only you see it, and your agent keeps to it on this branch until a commit carries it.
GitHub
Squash merges keep them
A squash writes a new commit. The Jinion Cloud GitHub App gives it the decisions of the pull request it came from.
- It asks for two permissions, both read-only: metadata and pull requests.
- It never reads your code, your files or your issues.
- Without it, a merge commit still carries decisions to main.
~/code/shop +- Decisions Acme / shop ----------------------------------+| In your code · your agents keep to these || > Move sessions to Postgres Mehmet · Oct 22 || Squashed into main as 7f3a91c, from #42 || Cache plans for an hour Lina · Oct 20 || Expire sessions after 30 idle days You · Oct 18 |+----------------------------------------------------------+| On other branches · agents don’t follow these || Retry payments twice feat/billing · #47 open |+----------------------------------------------------------+
jinion mcp
Whatever agent they use
A teammate who stays in Codex, Claude Code or Cursor reads the same decisions, finds what the project already has, and records a decision when asked. They sign in once, from a link.
- Codex
- Claude Code
Jinion Cloud
The team’s side of it
Members, projects and every decision your agents made, searchable on cloud.jinion.co.
Decisions
Every choice your agents recorded, across Acme’s projects.
Search decisions
- MK
Move sessions to Postgres
Mehmet Kaya · Answered · main
Merged1 day ago - LP
Retry payments twice, then email the owner
Lina Park · Asked for · feat/billing
In review2 days ago - LP
Cache plans for an hour
Lina Park · Agent’s call · main
Active3 days ago - ED
Expire sessions after 30 idle days
Emir Demir · Asked for · main
Active5 days ago - AY
Keep sessions in Redis
Ayşe Yılmaz · Answered · main
SupersededOct 3
Steer your next change
In private beta. Bring your plan and your invite.
Read the installation guide