Terminal-first engineering environment

Build Anything.Secure What You Build.

An intelligent terminal-first coding agent. Understand your project, build with confidence, investigate security risks, and verify every change — all in one connected workflow.

Privacy-first. Developer-controlled. Local by default — only request context reaches your AI provider.
QUICK INSTALLMore options ↓
LINUXcurl -fsSL https://superxcode.com/install-linux.sh | bash
WINDOWSirm https://superxcode.com/install-windows.ps1 | iex

Build Secure Verify
Scroll to explore

01 One connected workflow

From understanding
to verified change.

SuperX Code brings building, investigating, and verifying into a single terminal-first environment — not three disconnected tools.

superx~/projects/northstar
SCRIPTED WALKTHROUGH

northstar › Explore the authentication flow.

# session uses the model and permissions configured for this project

read src/auth/login.ts

search AuthStore · 4 references

inspect request → service → store

Relevant path is visible. Proceed to build or investigate.

Local sessionTool permissions applyDemo content

The terminal panel is a scripted product illustration. It does not execute commands on this page.

02 Security is not a separate product

Secure what
you build.

SuperX Code integrates security analysis naturally into your engineering workflow — not as a disconnected dashboard, but as part of the same terminal session where you build, review, and verify.

🔍

Investigate findings

Analyze potential weaknesses in the context of your actual code. Understand what the finding means, not just what it says.

🛡️

Review with evidence

Inspect the code, the diff, and the security output together. Make decisions based on evidence, not alerts alone.

✏️

Remediate in context

Apply fixes within the same session. Keep the build and the security work connected rather than switching tools.

✓

Verify improvements

Confirm that changes address the identified issue. Run the checks you choose and inspect the results.

superx~/auth-check
ILLUSTRATIVE SECURITY REVIEW

auth-check › Investigate authentication handling.

# security analysis runs under configured permissions

security scan --target src/auth/login.ts --scope dependencies

read findings / findings/auth-check.md

shell git diff -- src/auth/login.ts

Potential weakness: token expiration window exceeds safe threshold. Recommendation: reduce to 15 minutes with refresh rotation.

This is an illustrative demonstration. Actual findings depend on your code and configured analysis.

03 Privacy-first engineering

Your Code.
Your Machine.
Your Control.

SuperX Code is designed to give developers greater control over how they build software, manage project data, and connect AI models. Here is how information actually moves.

DATA FLOW EXPLORERSelect a data category to trace where it lives

Source code stays on your machine

The agent reads and edits files in the project directory you open. Source files are not uploaded to SuperX Code servers. When you send a request to a cloud model, only the context that request needs is transmitted to the provider you configured.

Boundary: your device → your AI provider

A

Collect less

The website loads no third-party analytics or advertising scripts. The feedback form stores the display name, rating, message, and authenticated account ID you submit, plus timestamps and publication status.

B

Keep it local

Project files, session history, and model credentials live in the local application and its database on your machine.

C

Give you control

Choose your model provider, decide which context a request carries, and set tool permissions to allow, ask, or deny actions.

04 Your AI provider. Your decision.

Separate systems,
separate policies.

SuperX Code gives you the freedom to connect supported AI providers with your own credentials. SuperX Code's privacy practices and your selected provider's practices are separate.

When you use a cloud model, the provider receives the information needed to process the request — prompts, code context, tool results, and other task-related content. Processing, retention, and training policies depend on that provider, your account configuration, and its terms.

A local or self-hosted OpenAI-compatible endpoint can keep model requests on infrastructure you control, provided that endpoint is configured correctly.

Read the privacy & trust overview

05 One environment, connected steps

01 / MAPUnderstandFiles · symbols · dependencies
02 / BUILDBuildGenerate · edit · review
03 / INSPECTInvestigateSecurity · dependencies · exposure
04 / VERIFYVerifyTests · output · confirmation

06 Project intelligence

See how the
pieces connect.

Explore files, packages, dependencies, and callers as relationships. This interactive sample is illustrative; SuperX's project graph works on the project you open in the product.

Nnorthstar-apiSample project graphILLUSTRATIVE DATA
routes/billing.tsauth.tsbilling servicesession.tsstore.tsdatabasebilling.test.tsschemapolicy.ts@northstar/core

Drag to orbitDrag to pan· Select a component to focus

This sample data describes a fictional project; it is not a scan of your repository or a SuperX system map.

07 Developer control

Your Models.
Your Code. Your Control.

Choose a supported provider or configure a compatible endpoint. Decide what project context to send, and set the tool permissions that shape what the agent can do.

MODEL REQUEST PATHCONFIGURED BY YOU
⌘Your projectCode · local sessionLOCAL APP
Selected context
AIYour providerEndpoint · model · keyCONFIGURED SERVICE

Prompts and context you send to a model go to its configured provider. Check that provider's data policies for its handling and retention terms.

A
Choose your model

Use a provider integration or a custom compatible endpoint.

B
Set tool boundaries

Allow routine actions, ask before sensitive ones, or deny them by policy.

C
Inspect the session

Review model usage, tool activity, and changes in the session record.

PROVIDER OPTIONS
OpenAIAnthropicGoogleDeepSeekMistralOpenRouterGroqxAIOpenAI-compatible

SuperX includes optional account and update services. The local application also stores session data. "Bring your own key" describes model-provider choice; it is not a claim that no data leaves your device.

08 Focused execution

Less Waste.
More Engineering.

Keep the work inspectable. SuperX tracks session and model usage, supports token budgets, and lets you choose the tools and checks that fit the task.

No savings or speed multiplier is implied. Provider pricing, model behavior, and task complexity vary.

SESSION CONTROLSCONFIGURABLE
ContextRelevant files
ToolsPermissioned
UsageInspectable
Budgets can bound a sessionIllustrative interface

09 Start in your terminal

Make the next
session yours.

Install SuperX Code, open a project, and begin from the command line. Configure your model provider and permissions for the way you work.

LINUX
curl -fsSL https://superxcode.com/install-linux.sh | bash
WINDOWS / POWERSHELL
irm https://superxcode.com/install-windows.ps1 | iex

THEN Open a project and run superx or superx-code.

10 Common questions

Clear by
design.

A few practical details before you bring SuperX into your workflow.

Is SuperX Code a hosted chatbot?

No. SuperX Code is a terminal-first engineering agent backed by a local application and server. Model requests go to the provider or endpoint configured for your session.

Can I choose which model provider to use?

Yes. SuperX supports provider integrations and custom compatible endpoints. Availability and model setup depend on the provider configuration you choose.

Does "bring your own key" mean all data stays local?

No. The local app stores session data, and context sent to a model is handled by your configured provider. Optional account and update services can also contact SuperX services.

Can I restrict what the agent is allowed to do?

Yes. Tool permissions can allow, ask, or deny actions according to your configured policy. Review those settings for the project and agents you use.

Where is my project data stored?

Project files stay in the directory you open. Session history and model credentials are stored in the local application database on your machine. Source files are not uploaded to SuperX Code servers.

Does the website track me?

This website loads no third-party analytics or advertising scripts. The feedback page uses Google Firebase with authenticated accounts to store the review data you submit.

Can I use a local model to keep requests on my machine?

You can configure a compatible local or self-hosted OpenAI-compatible endpoint. In that setup, model requests go to the endpoint you control rather than a third-party cloud provider.

Build with intention

Build Anything.
Secure What You Build.

One engineering environment for building, investigating security risks, and verifying results.

Get SuperX Code