bipartite

A context layer for research groups: connecting your internal world (projects, repos, coordination) to the external academic world (papers, citations, authors).

• Go CLI for querying literature, GitHub activity, and your group's projects and repos
• Claude Code skills for synthesis: narrative digests, check-ins, spawning sessions with context
• Git-backed storage — JSONL source of truth, private by default, shareable by design

Guides

• Getting Started — Installation, configuration, and first steps
• Configuration — Every config option, tokens, and environment variables
• Issue Lifecycle — Which skill to run at each step from draft issue to landed PR
• Reference Management — Search, import, cite, and collaborate on a git-backed paper library
• Projects, Repos, and Stores — Track projects and repositories, and keep custom records in generic stores
• Workflow Coordination — Check-ins, digests, boards, and Slack integration across repos
• Worktree Layout — Opt-in per-issue git worktrees for bip spawn
• Continuation Prompt — Carrying a session across a context reset with /bip-tuckin and /bip-continue
• Server Scout — Monitor remote server resources via SSH
• How It Works — The nexus, bip CLI, and Claude Code integration explained

Quick Start

1. Install bipartite

2. Create your nexus from the nexus-template (click "Use this template"), then clone it:

git clone https://github.com/YOUR_USERNAME/nexus ~/path/to/nexus

1. Point bip to your nexus:

mkdir -p ~/.config/bip
echo 'nexus_path: ~/path/to/nexus' > ~/.config/bip/config.yml

1. Build the index and try it out:

bip rebuild
bip search "phylogenetics"
bip s2 add DOI:10.1038/s41586-021-03819-2

See Getting Started for full setup instructions.

License

MIT