Skip to content

looplia init

The init command sets up your Looplia workspace at ~/.looplia/ with all required plugins and workflows.

Terminal window
looplia init [options]
OptionDescription
--yes, -ySkip confirmation prompts

The init command:

  1. Creates the workspace directory at ~/.looplia/
  2. Installs plugins from the marketplace:
    • looplia-core — Infrastructure plugin with commands and executor
    • looplia-writer — Domain plugin with content analysis skills
  3. Extracts workflows to ~/.looplia/workflows/
  4. Creates configuration files for user profile and provider settings
Terminal window
# Interactive initialization
looplia init
# Non-interactive (skip prompts)
looplia init --yes

After initialization:

~/.looplia/
├── looplia-core/ # Infrastructure plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── CLAUDE.md # Plugin instructions
│ ├── commands/
│ │ ├── run.md # /looplia:run command
│ │ └── build.md # /looplia:build command
│ ├── skills/
│ │ ├── workflow-executor/
│ │ ├── workflow-validator/
│ │ └── ...
│ └── hooks/
│ └── session-logger.md
├── looplia-writer/ # Domain plugin
│ ├── .claude-plugin/
│ │ └── plugin.json
│ └── skills/
│ ├── media-reviewer/
│ ├── idea-synthesis/
│ └── writing-kit-assembler/
├── workflows/ # Workflow definitions
│ └── writing-kit.md
├── sandbox/ # Execution sandboxes (preserved)
├── user-profile.json # User preferences (preserved)
└── looplia.setting.json # Provider config (preserved)

Run init again to update plugins to the latest version:

Terminal window
# Update plugins (will overwrite existing)
looplia init --yes

Your sandboxes, user profile, and provider settings are not overwritten.

If you see permission errors:

Terminal window
# Check directory permissions
ls -la ~/.looplia/
# Fix ownership if needed
sudo chown -R $(whoami) ~/.looplia/

If plugins fail to load after init:

Terminal window
# Remove and reinitialize
rm -rf ~/.looplia/looplia-core ~/.looplia/looplia-writer
looplia init --yes