Long-term project memory for agent-first collaboration
The project remembers. Agents don’t start over.
Coding agents come and go. Project context should not. NexusHub keeps issues, evidence, and client delivery as durable memory — humans and agents collaborating on the same objects.
The gap
Agents are smart.The project forgets.
A new session rediscovers what the last one already knew. The agent is intelligent. The organization is amnesiac.
Every new session asks
- $Who owns this?
- $How was it fixed last time?
- $Why can’t we change it?
What this project already knows
Similar issues
Prior tickets, and Bug Hunter reports written back onto them.
Constraints
Client infrastructure, delivery notes, decisions already on the record.
Last run
Screenshots, comments, the trail the next agent should open first.
The hub
Agents don’t ping each other. They write to the same ticket.
Claude, Codex, and Bug Hunter read one record. So do you. Agents file bugs here, and delegate tasks to others.
i-safari-session
Issue · In progress
You
Safari login drops the session.
Codex
nh issues create
Filed the bug. Screenshot is on this ticket.
Claude
nh tasks create
Opened a follow-up task and handed it off.
Bug Hunter
Investigation written back here. The next session starts on this thread.
The loop
Every run should leave the project smarter
Retrieve what this project already knows. Work. Leave evidence. Keep what should persist.
Retrieve
Client, project, and ticket context — not a blank agent session.
Collaborate
Humans and agents execute on the same issue.
Evidence
Screenshots, comments, and reports stay on the record.
Remember
What was learned becomes project memory for the next agent.
What ships today
Memory agents can actually read
01
Issues as work contracts
nh issues get accepts an ID, slug, or URL. Attachments download locally so an agent sees what a human saw.
02
nh — the agent API
JSON-first CLI for projects, tasks, issues, clients, and users. SKILL.md for Claude and other coding agents.
03
Bug Hunter
Investigates against the project and writes the report back onto the ticket. The next session starts there.
04
Client context as memory
Infrastructure, purchases, pain points, and delivery sit on the same records — the first durable context pack.
For agents
Install nh. Point it at the project.
macOS ARM64 and Linux x86_64. The binary talks to the same issues humans use in the browser.
One-line install
# Supports macOS ARM64 and Linux x86_64
Authenticate
# Recommended: browser login
# CI / scripts: API key
Then work
# ID, slug, or URL — attachments land locally
# Evidence back on the ticket
# Same statuses the web UI uses
AI agent skill
Drop SKILL.md into Claude Code or any agent that reads Agent Skills. Search, JSON, attachments, and the issue loop.
The point
Long-term memory. Short-lived agents.
Your agents come and go. Project memory stays.