Sandbox connector
Expose bounded test, build, package, or repo actions from infrastructure the customer controls.
Developer platforms
Add governed coding agents to developer platforms and internal engineering tools.
Build coding agents and developer assistants with customer-owned sandboxes, bounded tools, audit, memory, traces, and approvals.
Best for
- developer platforms adding AI assistants
- internal engineering portals and workflow tools
- products that need repo, build, test, or deployment tools behind policy
Recommended fit
General Augment fits developer platform teams that want to add an AI agent backend to an existing app. Best for developer products that need useful agent action without handing unrestricted shell or deploy access to the model. Your app keeps the user experience, auth, billing, product data, permissions, and source of truth while General Augment provides memory, governed tools, approvals, channels, usage, traces, and connector governance.
Common workflows
What teams build with this pattern.
Best for developer products that need useful agent action without handing unrestricted shell or deploy access to the model.
01
Repo-aware assistants that can propose, test, or verify changes
02
Customer-owned sandboxes that keep caches, credentials, and code local
03
Approval-gated deploy, publish, or write actions with trace evidence
What General Augment provides
Tool governance
Keep destructive or expensive actions behind explicit policy, rate limits, and approvals.
Agent-friendly docs
Use machine-readable docs, CLI checks, and support evidence to help coding agents integrate correctly.
Production shape
What this looks like in production.
Developer platforms can keep repo access, package caches, CI credentials, and deploy paths inside customer-owned or sandboxed infrastructure. General Augment handles the app-agent layer: task brief, allowed actions, approvals, usage, traces, and final result delivery.
A coding capability with product-grade governance
A user asks the product assistant to verify a failing integration. General Augment prepares the task, calls a governed sandbox capability, streams progress back to the app, reviews the output, and requires approval before publish or deploy actions.
Integration path
- 01Start with read-only repo inspection or test-run capabilities.
- 02Add bounded build, test, and package tools with time and cost limits.
- 03Require approval for write, merge, deploy, publish, or external-send actions.
- 04Return artifacts, logs, response ids, and trace ids to the app backend.
Memory, tools, approvals, channels
Memory
Remember project conventions, prior failures, approved tools, and user preferences without leaking across projects.
Tools
Expose repo, build, test, and deploy actions as bounded capabilities instead of raw shell access.
Approvals
Hold writes, merges, deploys, publishing, and billing-impacting actions until the product or operator approves.
Channels
Use app UI for task progress and optional messaging for completion, review, or approval prompts.
Operational checklist
Define allowed repo paths, commands, timeouts, package caches, and network boundaries.
Separate read, test, write, and deploy capabilities by risk.
Attach approvals to irreversible actions and external side effects.
Persist artifacts, test output, trace ids, and cost evidence for review.
Architecture
Keep the app. Add the agent backend.
Your app owns
User experience, auth, billing, product data, permissions, and source of truth.
General Augment runs
Agent turns, memory, governed tools, approvals, channels, usage, and traces.
Connectors can own
Private hosts, local machines, sandboxes, provider keys, and private network execution.
FAQ
When should teams use General Augment for developer platforms?
Best for developer products that need useful agent action without handing unrestricted shell or deploy access to the model. Use General Augment when your app should keep the product experience, auth, billing, permissions, and source of truth while the agent backend handles memory, governed tools, approvals, channels, usage, traces, and connector governance.
Does General Augment replace the app backend?
No. The app keeps user experience, auth, billing, product data, permissions, and source of truth. General Augment runs the agent backend layer.
Can private systems stay customer-owned?
Yes. Connectors can run on private hosts, local machines, sandboxes, or provider-owned capacity while General Augment governs the model-facing tool surface.
What is the first implementation step for developer platforms?
Start with read-only repo inspection or test-run capabilities.
What should teams review before launch?
Define allowed repo paths, commands, timeouts, package caches, and network boundaries. Separate read, test, write, and deploy capabilities by risk. Attach approvals to irreversible actions and external side effects. Persist artifacts, test output, trace ids, and cost evidence for review.
Related use cases
Personal productivity
A daily agent that remembers context
Morning briefings, meeting prep, reminders, inbox triage, and proactive follow-up across in-app chat, Telegram, SMS, or a local Mac connector.
Open use case
Health and care
Guided support with guardrails
Care navigation, intake summaries, follow-up tasks, escalation, and patient messaging with approval gates and auditable tool calls.
Open use case
Fintech and marketplaces
Policy-aware account actions
Support agents, dispute workflows, onboarding help, payment follow-up, and risky operations that require explicit approval before execution.
Open use case