This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 49b183818c Unify gitgram + aitimemachine into the monorepo (de-submodule) and merge vendored engines
Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as
opaque submodule gitlinks on GitHub) into fully-tracked first-party content.

AITM now merges its 7 vendored repos as first-party engines:
- memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts
- git: vendored C git (bundled binary) + gitnexus (in-process code intelligence)
- agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess)

Includes the full session's product build: Gitgram web/mobile/backend features,
AITM website/CLI/MCP, the unified memory layer, engine build tooling
(scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md),
and extensive test suites.

Build artifacts, node_modules, external/, and gemini-cli are gitignored.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 14:14:09 +03:00
..

Junie Integration for Beads

Integration for Junie (JetBrains AI Agent) with beads issue tracking.

Prerequisites

# Install beads
curl -fsSL https://raw.githubusercontent.com/gastownhall/beads/main/scripts/install.sh | bash

# Initialize beads in your project
bd init

Installation

bd setup junie

This creates:

  • .junie/guidelines.md - Agent instructions for beads workflow
  • .junie/mcp/mcp.json - MCP server configuration

What Gets Installed

Guidelines (.junie/guidelines.md)

Junie automatically reads this file on session start. It contains:

  • Core workflow rules for using beads
  • Command reference for the bd CLI
  • Issue types and priorities
  • MCP tool documentation

MCP Config (.junie/mcp/mcp.json)

Configures the beads MCP server so Junie can use beads tools directly:

{
  "mcpServers": {
    "beads": {
      "command": "bd",
      "args": ["mcp"]
    }
  }
}

Usage

Once installed, Junie will:

  1. Read workflow instructions from .junie/guidelines.md
  2. Have access to beads MCP tools for direct issue management
  3. Be able to use bd CLI commands

MCP Tools Available

  • mcp_beads_ready - Find tasks ready for work
  • mcp_beads_list - List issues with filters
  • mcp_beads_show - Show issue details
  • mcp_beads_create - Create new issues
  • mcp_beads_update - Update issue status/priority
  • mcp_beads_close - Close completed issues
  • mcp_beads_dep - Manage dependencies
  • mcp_beads_blocked - Show blocked issues
  • mcp_beads_stats - Get issue statistics

Verification

bd setup junie --check

Removal

bd setup junie --remove
  • bd prime - Get full workflow context
  • bd ready - Find unblocked work
  • bd dolt push - Push issue changes to Dolt remote (run at session end)

License

Same as beads (see repository root).