Temporal Obfuscation (Jitter)

Simulate organic development pace to avoid timing-based detection.

Overview

PhantomDev's Jitter engine introduces artificial delays between operations to simulate human coding cadences. This helps avoid timing-based developer analytics that can identify AI-assisted development patterns.

How It Works

The Jitter engine uses a delayed staging buffer with configurable timing windows:

Delayed Staging

Files are staged with random delays between operations.

Configurable Windows

Set minimum and maximum delay times to match your typical workflow.

Random Distribution

Delays are randomly distributed within the configured range for natural variation.

Commit Spacing

Automatically spaces commits to avoid rapid-fire patterns.

Enabling Jitter

Configuration

Add the following to your .phantomdev/config.toml:

[jitter] enabled = true min_delay_secs = 60 max_delay_secs = 300

Using Jitter

Once enabled, jitter automatically applies to:

  • File staging operations
  • Commit creation
  • Code humanization

Timing Configuration

Choose timing windows that match your typical development pace:

Conservative (30-120s)

For developers who work in short bursts

Moderate (60-300s)

For typical development workflows (default)

Extended (120-600s)

For developers who take longer between changes

Use Cases

Open Source Contributions

Make your contributions appear more organic when working on public projects.

Team Projects

Avoid standing out with unusually rapid commit patterns.

Code Reviews

Space out changes to match typical review cycles.

Long-running Features

Simulate natural development progression over time.

Limitations

Important: Jitter only affects timing, not code content. For complete protection, combine with detection and humanization features.
  • Does not modify code content
  • Requires enabled configuration
  • May slow down your workflow
  • Not effective for single-commit changes