Project Management

Create, configure, and monitor your Bootspring projects.

Overview#

Projects are the primary organizational unit in Bootspring. Each project:

  • Has its own context (CLAUDE.md)
  • Tracks separate usage metrics
  • Can have dedicated API keys
  • Maintains independent configuration

Project List#

The Projects page shows all your projects:

┌─────────────────────────────────────────────────────────────────────┐ │ Projects [+ New Project] │ ├─────────────────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────────────────────────────────────────────────────┐ │ │ │ 🚀 My SaaS App Active Pro │ │ │ │ github.com/user/my-saas-app │ │ │ │ Last active: 2 minutes ago │ │ │ │ API Calls: 3,420 │ Agents: 156 │ Context: Synced │ │ │ └──────────────────────────────────────────────────────────────┘ │ │ │ │ ┌──────────────────────────────────────────────────────────────┐ │ │ │ 📱 Mobile App Active Pro │ │ │ │ github.com/user/mobile-app │ │ │ │ Last active: 1 hour ago │ │ │ └──────────────────────────────────────────────────────────────┘ │ │ │ │ ┌──────────────────────────────────────────────────────────────┐ │ │ │ 🔬 Experiment Inactive Free │ │ │ │ Local project │ │ │ │ Last active: 3 days ago │ │ │ └──────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────┘

Creating a Project#

From Dashboard#

  1. Click New Project
  2. Fill in project details:
    • Name - Display name
    • Repository - GitHub/GitLab URL (optional)
    • Description - Brief description
    • Stack - Tech stack selection
  3. Click Create Project

From CLI#

Loading code block...

Project Details#

Click a project to view its detail page:

Overview Tab#

  • Project status and health
  • Recent activity log
  • Quick stats (API calls, agents, skills)
  • Active devices

Configuration Tab#

  • Project settings
  • Context configuration
  • Agent preferences
  • Skill settings
  • Quality gate configuration

API Keys Tab#

  • Project-specific API keys
  • Key permissions and scopes
  • Usage per key

Usage Tab#

  • Detailed usage metrics
  • Historical trends
  • Cost attribution

Settings Tab#

  • Rename project
  • Transfer ownership
  • Archive/delete project

Project Configuration#

General Settings#

SettingDescription
NameProject display name
SlugURL-friendly identifier
DescriptionBrief description
RepositoryLinked repository URL
VisibilityPublic or private

Context Settings#

SettingDescription
Context FilePath to CLAUDE.md
Auto-regenerateRegenerate on changes
Include PatternsFiles to include in context
Exclude PatternsFiles to exclude

Agent Settings#

SettingDescription
Enabled AgentsWhich agents are available
Default AgentAgent for general queries
Custom InstructionsPer-agent customization

Quality Settings#

SettingDescription
Pre-commit ChecksEnabled checks
Pre-push ChecksEnabled checks
Minimum CoverageTest coverage threshold
Lint RulesCustom lint configuration

Project Status#

StatusDescription
ActiveRecent activity within 24 hours
InactiveNo activity in 7+ days
ArchivedManually archived, read-only
ErrorConfiguration or sync issues

Project Actions#

Archive Project#

Archiving hides a project from active views but preserves all data. When you archive a project:

  • API keys are unlinked, not deleted — your keys remain usable for other projects
  • Usage data is retained for billing and analytics history
  • Audit logs and presence history are retained
  • The project no longer counts against your project limit
  • You can restore an archived project at any time from the projects list

To confirm archiving, you must type the project name in the confirmation dialog.

Loading code block...

Transfer Ownership#

Transfer to another team member (Team/Enterprise plans):

  1. Go to Settings > Transfer Ownership
  2. Select a current team member as the new owner
  3. The transfer takes effect immediately

Only the current owner can transfer ownership. The new owner inherits all project permissions.

Team Invitations#

Invite collaborators to your project:

  1. Go to Project Settings > Team Members
  2. Click Invite Member and enter their email
  3. Choose a role: Admin, Member, or Viewer
  4. The invitee receives an email with a link valid for 7 days

Invitation behavior:

  • Duplicate invitations to the same email are rejected
  • Invitations to existing project members are rejected
  • Invitees must have a verified email to accept
  • Expired invitations can be resent from the Pending Invitations panel
  • Owners and admins can revoke pending invitations
RolePermissions
OwnerFull control, transfer, archive
AdminManage members, settings, keys
MemberView project, use linked keys
ViewerRead-only access

Project Limits#

PlanMax Projects
Free1
Pro10
Team50
EnterpriseUnlimited

CLI Commands#

Loading code block...

API Integration#

Create Project#

Loading code block...

List Projects#

Loading code block...

See Projects API for full reference.

Best Practices#

1. One Project Per Repository#

Map projects 1:1 with repositories for clean separation.

2. Use Descriptive Names#

Choose names that identify the project at a glance.

3. Configure Context Properly#

Set appropriate include/exclude patterns for accurate context.

4. Monitor Usage#

Check usage regularly to stay within plan limits.

5. Archive Unused Projects#

Archive instead of deleting to preserve history.