RightNow AI is a YC-backed GPU research lab and software company. Its flagship product is RightNow Agent, the fastest coding agent harness in the world. It also builds the RightNow editor and Forge.

What is RightNow Agent?

RightNow Agent is the fastest coding agent harness in the world, a Rust terminal CLI built for one thing: speed. On the measured Windows path, a warm daemon opens a session in 105 to 115 ms.

Which NVIDIA GPUs does the RightNow editor support?

The RightNow editor supports all NVIDIA GPUs with CUDA Toolkit 11.0-12.5, including GeForce RTX 40/30/20 series, GTX 16/10 series, Quadro RTX, Tesla, A100, and H100.

How much does RightNow AI cost?

RightNow AI is free to use with unlimited profiling and benchmarking. RightNow Pro costs $20 per month and adds GPU emulator access (50+ GPUs), multi-GPU comparison, and 1,000 AI credits per month.

What CUDA development workflow does the RightNow editor support?

The RightNow editor supports CUDA development workflows that combine editing, profiling, emulation, remote GPU execution, and benchmarked performance analysis.

Can I use the RightNow editor on macOS?

Yes, the RightNow editor is available on macOS (Apple Silicon and Intel). Mac users can use remote GPUs for free or our built-in GPU emulator for CUDA profiling.

Permissions and Safety

RightNow Agent separates approval policy from isolation. Permission modes and rules decide whether a tool request may run. A configured OS sandbox can add a separate process boundary on supported kernels.

Permission modes

Mode	Behavior
default (ask)	Runs read-only tools and built-in read-only shell commands without prompting, then asks for other actions.
acceptEdits	Allows file edits without a prompt while other operations still follow the permission pipeline.
plan	Accepted for Claude-compatible settings. Use RightNow plan mode for gated planning.
auto	Runs work that passes the safety check. Other calls are blocked or escalated.
dontAsk	Runs only pre-approved tools and built-in read-only handling. Other calls are denied instead of prompting.
bypassPermissions	The config name for always-approve. Tool calls generally run, but deny rules, hooks, and some shell ask rules still apply.

Always-approve is not a sandbox

--always-approve, --yolo, and --dangerously-skip-permissions auto-approve tool execution. They do not isolate the process and should not be used for untrusted work.

bash

.\rightnow.ps1 --permission-mode auto
.\rightnow.ps1 --always-approve -p "Run the test suite"
.\rightnow.ps1 --permission-mode bypassPermissions

How authorization is evaluated

PreToolUse hooks may deny or rewrite the request.
Permission rules are merged and evaluated by severity: deny, then ask, then allow.
Remembered grants may satisfy an approval for the current project.
Built-in read-only approvals cover read tools and a fixed set of read-only shell commands.
The active mode prompts, approves, or denies anything still unresolved.

Any matching deny rule wins. If no deny matches, an ask rule wins over allow. Rule order in a file does not change that result.

toml

[permission]
deny = ["Bash(rm -rf *)", "MCPTool(sales__delete_*)"]
ask = ["Edit"]
allow = ["Bash(git *)", "Read", "Grep"]

Where rules come from

Source	Scope
--allow / --deny	Repeated CLI rules for the current process.
~/.rightnow/config.toml	User rules for all projects.
.rightnow/config.toml	Rules from the repository root through the working directory.
.claude/settings*.json	Compatible global, project, and personal project rules.
managed configuration	Organization rules and requirements.

Sandbox boundaries

Sandbox mode is off unless selected with --sandbox, GROK_SANDBOX, or [sandbox] profile. Kernel enforcement exists in the Linux Landlock and macOS Seatbelt implementations. The current product evidence is measured on Windows only.

Windows boundary

On Windows, permission prompts are application decisions, not kernel-enforced filesystem or network isolation. Use an external containment boundary when stronger isolation is required.

Shell environment policy

Tool commands receive a filtered environment. By default, ordinary variables are inherited, while names matching *KEY*, *SECRET*, or *TOKEN* are removed. Matching is case-insensitive, and this filtering is separate from sandbox isolation.

toml

[shell_environment_policy]
inherit = "core"
ignore_default_excludes = false
exclude = ["ACME_*", "CI_*"]
include_only = ["PATH", "HOME"]
set = { MY_FLAG = "1" }

Treat inputs as untrusted

Repository text, command output, fetched pages, MCP output, hooks, and migrated rules can all influence an agent session.

Before approval, review commands, paths, destinations, URLs, headers, and environment values. Keep credentials in the environment or an approved secret mechanism, never in committed configuration or shared logs.