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

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-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. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API 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. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
Sheet indexSecurity

Get started

  1. 01Developer hub
  2. 02Quickstart
  3. 03Security
    1. AChoose a pool for your data
    2. BCoding agents and prompt injection
    3. CWhat a Community pool provider can see
    4. DWhat HIPS stores
    5. EKnowledge and RAG data
  4. 04Migrate to HIPS

Guides

  1. 05HIPS SDK
  2. 06Import and run your model
  3. 07Model and task guides
    1. ATask guides
    2. BLanguage (chat)
    3. CClassification
    4. DImage
    5. EVideo
    6. FAudio
    7. GDocument processing
  4. 08Batch jobs
  5. 09Prompt caching
  6. 10Code with HIPS
  7. 11Coding-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. 12Command line
    1. AInstall and update
    2. BSign in
    3. CStatus and models
    4. DCoding agents
  9. 13Console
    1. AAccount
    2. BWorkspaces
    3. CAPI keys
    4. DSettings
    5. EUsage
    6. FModels
    7. GPlayground
    8. HDeployments
  10. 14Billing
  11. 15Provider setup
    1. AWhen it works
    2. BCommands
    3. CSettings
    4. DProvider Console
    5. EEarnings
    6. FCrash reports
    7. GData centers
  12. 16Semantic routing
  13. 17Guardrails
  14. 18Knowledge

Reference

  1. 19API 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. 20Operating guidance
    1. ALimits
    2. BErrors
    3. CRetries and billing outcomes
    4. DIdempotency
    5. EStreaming
    6. FData handling
    7. GCompatibility matrix
  3. 21Changelog
03
  1. Docs/
  2. Security/
  3. Coding agents and prompt injection
(Detail B)
llms.txt

Coding agents and prompt injection

On this sheet5 sections
  1. Every coding agent runs in the Certified pool
  2. What prompt injection is
  3. What HIPS does
  4. Run your coding agent in the Certified pool
  5. What you should do

A coding agent does what the model tells it. That makes the model's answer a security boundary.

F

Every coding agent runs in the Certified pool

Because of the risk of prompt injection, every coding agent runs in the Certified pool, always. A request that declares tools, carries tool calls or tool results, or is sent with a person's sign-in token, which only hi and HIPS Code use, runs only in the Certified pool, whatever client sends it (Requests that can act).

What prompt injection is

Prompt injection is text that makes a model act against your instructions. It reaches a model in two ways:

  1. 01

    Through what the agent reads. A library, a web page, a document or a tool result can hold instructions written for the model. The agent reads them as part of its work.

  2. 02

    Through the machine that runs the model. Whoever controls that machine could change the prompt before the model reads it, or change the answer before you get it.

For a chat, the result is a wrong answer. For a coding agent, the answer holds tool calls: commands and file edits that run on your computer, next to your source code and your credentials.

What HIPS does

  • Coding agents run only in the Certified pool. Every request that can act through tool calls is placed in the Certified pool and is never sent to a GPU in the Community pool. HIPS does not offer coding-agent models in the Community pool. In the Certified pool the machines that run the model are certified by HIPS's compliance team, so the second way above is closed.
  • Guardrails detect injected instructions. A content guardrail checks what goes to the model, tool results included, for text that tries to redirect it, and can flag, remove or block it. That addresses the first way above. Read Guardrails.
  • Keys are redacted on the way to a provider's GPU. Before a request reaches a GPU a provider owns, HIPS recognizes and redacts API keys, tokens, private keys and the values of environment variables in its text.
  • Nothing is stored. HIPS does not store, log or train on your code, your prompts or the answers. Read What HIPS stores.

Run your coding agent in the Certified pool

Install hi; it signs you in on its first run (Install hi, with Homebrew and Windows). From hi 0.1.7, every request of a session hi starts runs in the Certified pool, with fallback off, whatever the workspace's tool defaults say (Coding agents). Coding agents and tool calls are on the paid plans (Requests that can act).

Shell

00000000000000000000000000000000000000001curl -fsSL https://hips.com/hi.sh | sh2hi claude
Shell sample

Your own agent, or any app that sends tool calls: name the Certified pool in the request too, so the code says what it does.

00000000000000000000000000000000000000001import os2from openai import OpenAI3 4client = OpenAI(5    api_key=os.environ["HIPS_API_KEY"],6    base_url="https://ai.hips.com/v1",7    # A request with tools runs only in the Certified pool8    default_headers={"x-hips-pool": "certified"},9)10result = client.chat.completions.create(11    model=os.environ["HIPS_MODEL"],12    messages=[{"role": "user", "content": "List the files in this folder."}],13    tools=[{"type": "function", "function": {"name": "list_files", "parameters": {"type": "object", "properties": {}}}}],14)15print(result.choices[0].message.tool_calls)
Reads from the environmentHIPS_API_KEYHIPS_MODEL

What you should do

  • Start your coding agent through hi, or use HIPS Code once it is released.
  • Keep your agent's permission prompts on, and use its sandbox where it has one.
  • Read a command before you approve it, above all one that sends data out, installs a package or changes your shell or git configuration.
  • Keep credentials out of the folder the agent works in.

Related sheets

  • Code with HIPS
  • Guardrails
Previous sheetChoose a pool for your data
Next sheetWhat a Community pool provider can see
Sheet
03 of 21
Detail
B
Updated
2026-11-17
Sign in to the Console

On this sheet

  1. Every coding agent runs in the Certified pool
  2. What prompt injection is
  3. What HIPS does
  4. Run your coding agent in the Certified pool
  5. What you should do

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Ü