Skip to main content

Run Nastech Agent with Nastech Portal

This guide walks you through running Nastech Agent on a Nastech Portal subscription end to end — from signing up to verifying that every tool routes correctly. If you just want the overview of what the Portal is and what's in the subscription, see the Nastech Portal integration page. This page is the task script.

Prerequisites​

  • Nastech Agent installed (Quickstart)
  • A web browser on the machine you're setting up (or SSH port forwarding — see OAuth over SSH)
  • About 5 minutes

You do not need: an OpenAI key, an Anthropic key, a Firecrawl account, a FAL account, a Browser Use account, or any other per-vendor credential. That's the whole point.

1. Get a subscription​

Open portal.nastechresearch.github.io/manage-subscription, sign up, and pick a plan.

Already subscribed? Skip to step 2.

2. Run the one-shot setup​

nastech setup --portal

This single command does five things:

  1. Opens your browser to portal.nastechresearch.github.io for OAuth login
  2. Stores the refresh token at ~/.nastech/auth.json
  3. Sets model.provider: nastech in ~/.nastech/config.yaml
  4. Picks a default agentic model (anthropic/claude-sonnet-4.6 or similar)
  5. Turns on the Tool Gateway for web search, image generation, TTS, and browser automation

When it finishes, you're back at your terminal ready to chat.

What if I'm SSH'd into a server?​

OAuth needs a browser, but the loopback callback runs on the machine where Nastech is running. Two options:

# Option A: SSH port forwarding (preferred)
ssh -N -L 8642:127.0.0.1:8642 user@remote-host    # in a local terminal
nastech setup --portal                              # on the remote, open the printed URL in your local browser

# Option B: device-code login (works from Cloud Shell, Codespaces, EC2 Instance Connect)
nastech auth add nastech --type oauth
# Then re-run `nastech setup --portal` to wire the provider + gateway

See OAuth over SSH / Remote Hosts for the full walkthrough including ProxyJump chains, mosh/tmux, and ControlMaster gotchas.

3. Verify it worked​

nastech portal info

You should see:

  Nastech Portal
  ───────────
  Auth:    ✓ logged in
  Portal:  https://portal.nastechresearch.github.io
  Model:   ✓ using Nastech as inference provider

  Tool Gateway
  ────────────
  Web search & extract  via Nastech Portal
  Image generation      via Nastech Portal
  Text-to-speech        via Nastech Portal
  Browser automation    via Nastech Portal

If any line shows something other than "via Nastech Portal" or the auth line says "not logged in", jump to Troubleshooting below.

4. Run your first conversation​

nastech chat

Try something that exercises both the model and the Tool Gateway:

Hey, search the web for "Nastech Agent release notes" and summarize the top 3 hits.

You should see Nastech call web_search (Firecrawl-backed, through the gateway) and respond with a summary. If the search runs and the response makes sense, you're done — the Portal is wired up end to end.

5. Pick the model you actually want​

nastech setup --portal lets you pick a model during setup, but the whole point of the subscription is access to the full catalog — switch any time with /model mid-session:

/model anthropic/claude-sonnet-4.6     # best general-purpose agentic
/model openai/gpt-5.4                  # strong reasoning + tool calling
/model google/gemini-2.5-pro           # huge context window
/model deepseek/deepseek-v3.2          # cost-effective coder
/model anthropic/claude-opus-4.6       # heavyweight for hard problems

Or pop the picker to browse:

/model

Pick a different default permanently:

# in your terminal, outside any session
nastech config set model.default anthropic/claude-sonnet-4.6

Don't pick Nastech-4 for agent work​

Nastech-4-70B and Nastech-4-405B are available on the Portal at deep discounts, but they're chat/reasoning models, not tool-call-tuned. They will struggle with multi-step agent loops. Use them for conversation/research work through the subscription proxy from non-agent tools. For Nastech Agent itself, stick to the frontier agentic models above.

The Portal's own info page carries this warning too — it's the official Nastech guidance, not just a Nastech-side opinion.

6. (Optional) Customize Tool Gateway routing​

The gateway is opt-in per tool, not all-or-nothing. If you already have a Browserbase account and want to keep using it while routing web search and image generation through Nastech, that's supported:

nastech tools
# → Web search       → "Nastech Subscription"     (recommended)
# → Image generation → "Nastech Subscription"     (recommended)
# → Browser          → "Browserbase"           (your existing key)
# → TTS              → "Nastech Subscription"     (recommended)

These rows appear in nastech tools even before you've logged into Nastech Portal — if you pick "Nastech Subscription" without an active session, Nastech runs the Portal login inline (without changing your inference provider or your other tools).

Verify your mix with:

nastech portal tools

You'll see per-tool routing — via Nastech Portal for the ones routed through the subscription, and the partner name (browserbase, firecrawl, etc.) for the ones using your own keys.

7. (Optional) Enable voice mode​

Because the Tool Gateway includes OpenAI TTS, voice mode works without a separate OpenAI key:

nastech setup tts
# → pick "Nastech Subscription" for TTS
# → pick a speech-to-text backend (local faster-whisper is free, no setup)

Then in any messaging-platform session (Telegram, Discord, Signal, etc.), send a voice message and Nastech will transcribe it, respond, and reply with synthesized voice — all on your Portal subscription.

8. (Optional) Cron + always-on workflows​

The Portal subscription works for cron jobs and batch processing the same way it works for interactive chat — the OAuth refresh token is reused automatically. No additional setup; just schedule cron jobs and they'll bill against your subscription.

nastech cron create "0 9 * * *" \
  "Search the web for top AI news and summarize the 5 most important stories" \
  --name "Daily AI news"

The cron job runs unattended, calls the model + web search + summarization all through your Portal subscription.

Profiles and multi-user setups​

If you use Nastech profiles (e.g. a separate config per project), each profile is an independent credential island: a profile that has never signed in to the Portal fails closed instead of adopting another profile's session. Sign in once per profile with nastech -p <name> portal — when a shared Portal session already exists on the machine it offers to import it without a browser round-trip, and from then on the shared token store keeps that profile's token current. See Profile setup.

For team setups where multiple humans share a machine, each human has their own Portal account → each home directory holds its own ~/.nastech/auth.json → no token sharing across users. This is the right boundary.

Troubleshooting​

nastech portal info shows "not logged in" after nastech setup --portal​

The OAuth flow didn't complete. Re-run it:

nastech portal

If your browser doesn't open or the callback fails, you're likely on a remote/headless host — see OAuth over SSH for the port-forwarding workarounds.

"Model: currently openrouter" (or some other provider) instead of "using Nastech as inference provider"​

Your local config drifted. The OAuth worked but model.provider is still pointing at a different provider. Fix:

nastech config set model.provider nastech

Or interactively:

nastech model
# pick Nastech Portal

Re-verify with nastech portal info.

Tool Gateway tools showing partner names instead of "via Nastech Portal"​

Per-tool config is overriding the gateway. Run:

nastech tools
# pick "Nastech Subscription" for any tool you want gateway-routed

Some users intentionally mix — e.g. routing web through Nastech but using their own Browserbase key for browser. If that's intentional, leave it alone. If not, this command fixes it.

"Re-authentication required" mid-session​

Your Portal refresh token was invalidated (password change, manual revoke, session expiry). The token is now quarantined locally so Nastech doesn't replay it endlessly. Just log in again:

nastech auth add nastech

The quarantine clears automatically on successful re-login.

Model I want isn't in the /model picker​

The Portal catalog draws on OpenRouter's model list (300+) plus models served through proprietary or secondary providers. If a model is missing, try typing the OpenRouter-style slug directly:

/model anthropic/claude-opus-4.6
/model openai/o1-2025-12-17

If a model is genuinely unavailable, open an issue — most gaps are routing config we can update.

Billing not appearing on my Portal account​

nastech portal info will tell you whether you're actually routing through the Portal or some other provider. Common causes:

  • model.provider set to openrouter/anthropic/etc. instead of nastech
  • An OAuth refresh failure that fell back to a different configured provider
  • Multiple Nastech profiles where you're using the wrong one (check nastech profile list)

Want to revoke and start clean​

nastech auth logout nastech       # wipes the local refresh token
# Then re-run setup or remove the subscription from the Portal web UI

What this gets you, in plain numbers​

Without PortalWith Portal
1× OpenRouter / Anthropic / OpenAI key in .env1× OAuth refresh token, no .env keys
1× Firecrawl key for webWeb routed through gateway
1× FAL key for image genImage gen routed through gateway
1× Browser Use / Browserbase key for browserBrowser routed through gateway
1× OpenAI key for TTS / voice modeTTS routed through gateway
5 separate dashboards, top-ups, invoices1 subscription, 1 invoice
Cross-machine: replicate all 5 keysCross-machine: re-OAuth once

That's the deal. If you're using more than two of those backends anyway, the subscription pays for itself.

See also​