Skip to content
HIPS
  • Earn with your GPU
  • Pricing
  • Docs
Sign inJoin early access
⌘K

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Code with HIPS
  7. 10Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 11Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 12Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 13Billing
  11. 14Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 15Semantic routing
  13. 16Guardrails
  14. 17Knowledge

Reference

  1. 18API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 19Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 20Changelog
Sheet indexCoding-tool setup

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Migrate to HIPS

Guides

  1. 04HIPS SDK
  2. 05Import and run your model
  3. 06Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 07Batch jobs
  5. 08Prompt caching
  6. 09Code with HIPS
  7. 10Coding-tool setup
    1. AHIPS Code
    2. BClaude Code
    3. CCodex
    4. DOpenCode
    5. EKilo
    6. FPi
    7. GQwen Code
    8. HCrush
    9. ICline
    10. JPrime Agent
    11. KAider
    12. LGoose
    13. MHermes Agent
    14. NGrok Build
    15. ODeepSeek Harness
    16. POther coding tools and editor integrations
  8. 11Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 12Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 13Billing
  11. 14Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 15Semantic routing
  13. 16Guardrails
  14. 17Knowledge

Reference

  1. 18API reference
    1. AAuthentication
    2. BChat completions
    3. CResponses
    4. DMessages
    5. ECount tokens
    6. FModels
    7. GPrices API
    8. HTasks
    9. IEmbeddings and rerank
    10. JImages
    11. KJobs
    12. LUploads
    13. MFiles
    14. NBatches
    15. OWebhooks
    16. PVector stores
    17. QDeployments
    18. RRequirements and headers
    19. SErrors
    20. TUsage
    21. UVersioning
  2. 19Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 20Changelog
10
  1. Docs/
  2. Coding-tool setup/
  3. Claude Code
(Detail B)
llms.txt

Use Claude Code with HIPS

On this sheet9 sections
  1. The quickest way: hi
  2. Permissions under hi
  3. The releases hi starts
  4. The models that passed its tests
  5. Manual setup
  6. What changes in the tool's configuration
  7. How credentials are handled
  8. How to restore the previous setup
  9. The conditions of the status

hi claude starts Claude Code on HIPS models, signed in as you, with no API key to copy: hi sets HIPS up for that session only and leaves Claude Code's own settings as they are.

F
Fig. 1, sheet 10Coding-tool setup

The quickest way: hi

00000000000000000000000000000000000000001curl -fsSL https://hips.com/hi.sh | sh
Language
  • hi finds claude on your computer, checks that its release is one HIPS has tested on your system, and names its vendor's installer when it is missing.
  • The first time, it signs you in: it shows a code and a link, and you approve it in the Console.
  • It takes a model fit for coding from your workspace's catalog, or the one you name with --model, and gives Claude Code HIPS's address and your sign-in through Claude Code's own credential setting, speaking Anthropic's Messages API.
  • It turns off Claude Code's own telemetry, and whatever would send your session to its vendor, for that session.

Code with HIPS is the overview; Coding agents has every option of hi claude.

Permissions under hi

Starts in Accept edits (acceptEdits): it edits files and runs common file commands without asking, and asks before anything else. Its auto mode, in which a model reviews each action, is not supported by hi yet: hi leaves it out of Shift+Tab, and a session you start in auto mode, with --permission-mode auto or auto as permissions.defaultMode in your settings, starts in Accept edits instead. Any other mode you name is yours.

Auto mode, where a model reviews or approves an agent's actions for you, is not supported by hi yet; Coding agents has every agent's starting mode.

The releases hi starts

SystemTested releases
macOS2.1.314 to 2.1.325
Linux2.1.319 to 2.1.325
Windows2.1.322 to 2.1.325
  • System
    macOS
    Tested releases
    2.1.314 to 2.1.325
  • System
    Linux
    Tested releases
    2.1.319 to 2.1.325
  • System
    Windows
    Tested releases
    2.1.322 to 2.1.325

From the signed list of tested versions of 2026-11-14, 01:09 UTC (sequence 7), joined with the releases built into hi 0.1.3. hi reads the signed list each day, so it may start a newer tested release than this page shows; any other release is refused with the tested ones named.

The models that passed its tests

In the per-model agent tests' record of 2026-11-14, 05:25 UTC (sequence 10): Passed in the Community pool with gpt-oss-20b, granite-4.2-8b and qwen2.5-7b-instruct, on Claude Code 2.1.325. The gateway refused the pairs of two other models, and the rest found no free capacity when they ran; both run again with the next tests. The Console's Models page shows each model's result as the record holds it.

Manual setup

For people who do not use hi. Named by the source specification as a candidate where compatibility can be established. Started on HIPS by hi claude; its manual setup is unvalidated.

StatusTool and version testedValidated on
unvalidatednonenone
  • Status
    unvalidated
    Tool and version tested
    none
    Validated on
    none

What changes in the tool's configuration

Not tested. When the row is validated, this section states where the tool reads its base URL, key and model (environment, file, flag or UI), and which of those the setup helper uses for a session and for a persistent configuration.

How credentials are handled

Not tested. When validated: how the tool sends the key, that HIPS accepts it as Authorization: Bearer, and that the helper never prints a secret. The key is read as HIPS_API_KEY and kept on the machine's own secret store or environment.

How to restore the previous setup

Not tested. When validated: the backup the helper takes before a persistent change, and the selective undo that restores the previous provider, model mapping and defaults without touching unrelated providers.

The conditions of the status

  • Tool and SDK versions: none tested.
  • Configuration surface: not tested.
  • Authentication: not tested.
  • Model mapping: not tested.
  • Streaming: not tested.
  • Complete tool-call round trips: not tested.

Note

The status is unvalidated Not decided yet. A page moves past unvalidated only with a dated validation record; the record's date and test results replace the "not tested" lines above.

Related sheets

  • Code with HIPS
  • Coding agents
  • The supported-tools matrix
  • Compatibility matrix
Previous sheetHIPS Code
Next sheetCodex
Sheet
10 of 20
Detail
B
Updated
2026-11-14
Sign in to the Console

On this sheet

  1. The quickest way: hi
  2. Permissions under hi
  3. The releases hi starts
  4. The models that passed its tests
  5. Manual setup
  6. What changes in the tool's configuration
  7. How credentials are handled
  8. How to restore the previous setup
  9. The conditions of the status

Product

  • Inference
  • Models
  • Deploy your model
  • Always-on GPU capacity
  • How it works
  • Use cases
  • Pricing

Developer

  • Docs
  • Quickstart
  • Migrate to HIPS
  • HIPS SDK
  • Batch jobs
  • API reference

Provider

  • Earn with your GPU
  • Register GPU interest
  • Download for Mac
  • Download for Windows
  • Download for Linux

Resource

  • Security and Data
  • Resources
  • llms.txt

Compare

  • OpenRouter alternatives
  • Together AI alternatives
  • Groq alternatives
  • All comparisons

Company

  • About
  • Contact
  • Affiliate program
  • HIPS Payments

Legal

  • Legal
  • Consumer Health Data Privacy Policy
  • Report content
  • Cookie preferences

Support

  • Contact HIPS
  • Looking for payments support?

HIPS. AI inference for builders.

hips.com

Hyperscale Inference Processing Systems OÜ