@longtable/setup

Researcher onboarding and setup flows for LongTable.

Recommended Usage

Researchers should use the unified CLI:

npm install -g @longtable/cli
longtable setup --provider codex

This package exists so the setup flow can also be consumed programmatically or tested in isolation during development.

By default this writes:

• setup output to ~/.longtable/setup.json
• Codex runtime config to ~/.longtable/runtime/codex/longtable.toml
• Claude runtime config to ~/.longtable/runtime/claude/longtable.json

The generated runtime config does not overwrite platform-native config files directly. It creates LongTable-managed runtime artifacts that can later be wired into provider-specific runtimes during migration.

Package Role

The setup contract stores runtime permission and intervention defaults. It should not front-load researcher-profile calibration.

Global setup should answer:

• which provider is being configured
• where LongTable may install runtime support
• which provider surfaces are approved
• how strongly LongTable may interrupt research decisions
• whether setup should show the provider-native $longtable-start launch steps

Project and session intake belongs to $longtable-start inside Codex or Claude Code, not library-level setup helpers. longtable start is a fallback for scripts and automation, not the primary research-start experience.

Included Outputs

• quick setup question flow
• provider selection resolution
• persisted setup output generator
• saved setup output helpers
• runtime config installer helpers
• numbered checkpoint helpers

See examples/ for sample Codex and Claude setup outputs.