Skip to main content

Run Slick Agent with Hackit Portal

This guide walks you through running Slick Agent on a Hackit 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 Hackit Portal integration page. This page is the task script.

Prerequisites​

  • Slick 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.hackit.cc/manage-subscription, sign up, and pick a plan.

Already subscribed? Skip to step 2.

2. Run the one-shot setup​

slick setup --portal

This single command does five things:

  1. Opens your browser to portal.hackit.cc for OAuth login
  2. Stores the refresh token at ~/.slick/auth.json
  3. Sets model.provider: hackit in ~/.slick/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 Slick 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
slick 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)
slick auth add hackit --type oauth
# Then re-run `slick 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​

slick portal info

You should see:

  Hackit Portal
  ───────────
  Auth:    ✓ logged in
  Portal:  https://portal.hackit.cc
  Model:   ✓ using Hackit as inference provider

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

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

4. Run your first conversation​

slick chat

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

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

You should see Slick 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​

slick 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
slick config set model.default anthropic/claude-sonnet-4.6

Don't pick Slick-4 for agent work​

Slick-4-70B and Slick-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 Slick Agent itself, stick to the frontier agentic models above.

The Portal's own info page carries this warning too — it's the official Hackit guidance, not just a Slick-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 Hackit, that's supported:

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

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

Verify your mix with:

slick portal tools

You'll see per-tool routing — via Hackit 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:

slick setup tts
# → pick "Hackit 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 Slick 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.

slick 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 Slick profiles (e.g. a separate config per project), the Portal refresh token is automatically shared across all profiles via a shared token store. Sign in once on any profile, and the rest pick it up automatically.

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

Troubleshooting​

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

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

slick 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 Hackit as inference provider"​

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

slick config set model.provider hackit

Or interactively:

slick model
# pick Hackit Portal

Re-verify with slick portal info.

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

Per-tool config is overriding the gateway. Run:

slick tools
# pick "Hackit Subscription" for any tool you want gateway-routed

Some users intentionally mix — e.g. routing web through Hackit 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 Slick doesn't replay it endlessly. Just log in again:

slick auth add hackit

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​

slick 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 hackit
  • An OAuth refresh failure that fell back to a different configured provider
  • Multiple Slick profiles where you're using the wrong one (check slick profile list)

Want to revoke and start clean​

slick auth logout hackit       # 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​