fix: disinto init should run hire-an-agent for all configured bot users #404

New issue

Closed

opened 2026-04-08 07:22:16 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-04-08 07:22:16 +00:00

Collaborator

Problem

Disinto init creates bot users and tokens but does not create .profile repos for them. The .profile repos are needed for journal writing and lessons learned. Currently hire-an-agent must be run manually for each bot after init.

#234 was supposed to fix this but architect-bot's .profile was not created (returns 404).

Fix

Add a step to disinto init (after bot user creation) that runs the .profile creation logic from hire-an-agent for each bot user that doesn't already have a .profile repo:

for bot in dev-bot review-bot planner-bot gardener-bot vault-bot supervisor-bot predictor-bot architect-bot; do
  if ! curl -sf "${forge_url}/api/v1/repos/${bot}/.profile" >/dev/null 2>&1; then
    # Create .profile repo using admin API
    # Same logic as hire-an-agent Step 2-3
  fi
done

This is idempotent — skips bots that already have .profile repos.

Affected files

lib/forge-setup.sh or bin/disinto (add .profile creation loop after bot user setup)

Acceptance criteria

disinto init creates .profile repos for all bot users
Existing .profile repos are not recreated
architect-bot gets a .profile repo

## Problem Disinto init creates bot users and tokens but does not create .profile repos for them. The .profile repos are needed for journal writing and lessons learned. Currently hire-an-agent must be run manually for each bot after init. #234 was supposed to fix this but architect-bot's .profile was not created (returns 404). ## Fix Add a step to disinto init (after bot user creation) that runs the .profile creation logic from hire-an-agent for each bot user that doesn't already have a .profile repo: for bot in dev-bot review-bot planner-bot gardener-bot vault-bot supervisor-bot predictor-bot architect-bot; do if ! curl -sf "${forge_url}/api/v1/repos/${bot}/.profile" >/dev/null 2>&1; then # Create .profile repo using admin API # Same logic as hire-an-agent Step 2-3 fi done This is idempotent — skips bots that already have .profile repos. ## Affected files - lib/forge-setup.sh or bin/disinto (add .profile creation loop after bot user setup) ## Acceptance criteria - [ ] disinto init creates .profile repos for all bot users - [ ] Existing .profile repos are not recreated - [ ] architect-bot gets a .profile repo