Pair CLILogin/Signup

Guides

Short workflows for common coding tasks.

Start with a task below, then adapt the commands to your repository.

Choose a Workflow

// Start with the job, not the command

Choose a guide for the task you need to complete.

First Task

Install, sign in, and run a first task.

Build a Feature

Plan, implement, and verify a feature.

Debug a Failure

Diagnose a failure, then verify the fix.

Automate CI

Run tasks in CI with JSON output.

Configure the Runtime

Set project instructions and permissions.

Troubleshoot

Find fixes for common runtime issues.

Build a Feature

// Plan → implement → verify

Give LucentraCode a concrete objective and a definition of done. Keep planning, implementation, and verification as separate steps when the change affects multiple files or systems.

Engineering Loop Pipeline
1.OBJECTIVE
2.PLAN
3.IMPLEMENT
4.TEST
5.REVIEW
6.VERIFY
Plan the change
lucentracode run --agent plan "plan a user invitation flow and identify the files, tests, and risks"
Implement the plan
lucentracode run --agent build "implement the user invitation flow from the plan"
Run verification
lucentracode run "run the relevant tests, typechecks, and lint checks for the invitation flow"
Review the result
lucentracode run --agent review "review the current changes for correctness, security, and missing tests"
// NOTE:Prefer small, verifiable objectives. If the scope changes, ask LucentraCode to update the plan before continuing.

Debug a Failing Test

// Diagnose before editing

Give LucentraCode the failure output, the affected area, and the expected behavior. Ask for a root-cause analysis first when the failure could have multiple causes.

Diagnose the failure
lucentracode run --agent review "inspect the failing test output, identify the root cause, and propose the smallest fix"
Apply and verify the fix
lucentracode run "fix the root cause and run the focused tests for this failure"
Check the full suite
lucentracode run --format json "run the full test suite and report any remaining failures"
// NOTE:Keep the original failure output in the task prompt or CI log so the diagnosis can be reproduced later.

Run LucentraCode in CI

// Machine-readable repository automation

CI jobs should authenticate through secret-managed environment variables, target a known directory, request JSON output, and fail visibly when verification does not complete.

yaml
- name: Verify generated changes
  env:
    LUCENTRACODE_API_KEY: ${{ secrets.LUCENTRACODE_API_KEY }}
  run: |
    lucentracode run \
      --dir ./ \
      --format json \
      "run the relevant tests and report failures without changing unrelated files"
// NOTE:Store the API key in your CI secret manager and limit workspace access.

Add an MCP Tool

// Extend the CLI with a trusted integration

List current servers
lucentracode mcp list
Add a server
lucentracode mcp add
Authenticate the server
lucentracode mcp auth
Test the integration
lucentracode run "use the configured MCP tool to inspect the issue and report what it found"
  • •Confirm what data the server can read.
  • •Confirm which actions it can perform.
  • •Use a separate credential or account when possible.
  • •Remove stored credentials when the integration is no longer needed.
// NOTE:Third-party MCP servers operate outside Lucentra Labs’ direct security boundary. Connect only systems you trust.