Text generation
A model for the reasoning step
Use GT to explain a problem, draft a plan or review supplied material. Select an available family from the catalog and define what a useful response should contain.
Explore model familiesGALACTRE / AGENT PLATFORM
Bring model reasoning into the work your application manages. Explore how Galactre can help plan, explain and review, with context, permissions and human decisions kept in view.
Available foundation: text generation and conversation context.
Managed multi-agent runs and tool execution remain planned.
01 / A PRACTICAL FOUNDATION
A model response can be one step in a larger system. Start with the capabilities available today and give each surrounding component a clear responsibility.
Text generation
Use GT to explain a problem, draft a plan or review supplied material. Select an available family from the catalog and define what a useful response should contain.
Explore model familiesConversation context
Continue a conversation using its saved ID. The current chat includes bounded recent messages; it does not automatically read your repository, browse a website or retrieve private documents.
Understand conversation contextGuest and account sessions
Try a limited Lunar conversation as a guest. Use an IAMC account for separate account history and billing, and check the published Galactre contract before planning a server integration.
Read the access contractReview in your application
Treat generated plans, code and checklists as proposed artifacts. Your application owns validation, approval and any action taken after a response.
Design an evaluation02 / EXPLORE THE HANDOFFS
Explore three illustrative workflows. Select a stage to inspect its input, responsibility and expected artifact. These blueprints do not run agents, tools or deployments.
Use a focused diff and explicit criteria to prepare review notes. The model produces text; repository reads, test execution and merge decisions belong to your application and reviewers.
ILLUSTRATIVE STAGE / 01
Your application obtains an authorized diff, runtime information and acceptance criteria. Exclude credentials and unrelated private files.
ILLUSTRATIVE STAGE / 02
Request possible defects, assumptions and test suggestions linked to the supplied code. Require missing context to be called out explicitly.
ILLUSTRATIVE STAGE / 03
A reviewer checks the findings. Your controlled test runner executes relevant tests and records actual results separately from generated text.
ILLUSTRATIVE STAGE / 04
An authorized maintainer decides what to change and whether to merge. No model response grants itself repository write permissions.
Help me prepare a code review. I will supply a diff, runtime version and acceptance criteria. First identify missing context. Then organize your review into correctness risks, security concerns, proposed tests and questions for the author. Do not claim repository access or test execution. Wait for the diff before making findings.The link opens a draft. No model request is sent until you submit it.
Retrieve only the documents a user may access, provide relevant excerpts and review the answer against those sources. Retrieval and document permissions are responsibilities of the consuming application.
ILLUSTRATIVE STAGE / 01
Your application checks document permissions and chooses relevant passages. Source labels should resolve to material that the user can inspect.
ILLUSTRATIVE STAGE / 02
Ask GT to ground factual claims in the supplied text, distinguish inferences and identify missing information. A citation is a claim to be checked.
ILLUSTRATIVE STAGE / 03
Verify that every reference exists and supports the associated claim. Check the answer for unsupported additions and conflicting sources.
ILLUSTRATIVE STAGE / 04
Show the reviewed answer and accessible references. Escalate unresolved questions through the workflow you control rather than inventing certainty.
Help answer a question using only the source excerpts I provide. Cite the supplied source labels for factual claims. Separate supported facts, inferences and missing information. If the answer is absent from the excerpts, say so and ask for the right source. Wait for my question and excerpts.The link opens a draft. No model request is sent until you submit it.
Prepare a release brief, identify prerequisites and review rollback criteria. The model does not build artifacts, change infrastructure or deploy an application through this chat release.
ILLUSTRATIVE STAGE / 01
Collect the change summary, actual test outputs, migration requirements, monitoring signals and rollback plan from authorized systems.
ILLUSTRATIVE STAGE / 02
Ask for prerequisites, sequence, risks and go/no-go criteria. Separate confirmed evidence from assumptions and missing checks.
ILLUSTRATIVE STAGE / 03
Your deployment system enforces the actual role and environment policy. An approver verifies evidence and accepts or rejects the release.
ILLUSTRATIVE STAGE / 04
Your controlled deployment runner applies an approved release, monitors health and follows rollback policy. Record the actual operational outcome.
Help prepare a release readiness checklist for a PHP application. Ask for the change summary, test evidence, migration plan, monitoring signals and rollback procedure. Separate confirmed evidence from missing evidence. Produce a draft go/no-go checklist; do not claim that you built or deployed anything.The link opens a draft. No model request is sent until you submit it.
03 / THE SYSTEM BOUNDARIES
Keep model reasoning, workflow state and real-world execution distinct. The integration is easier to inspect when each layer owns a defined boundary.
Owns user permissions, source retrieval, task state, tools, approvals and artifact storage. It decides which context may be sent and which actions are allowed.
Provides the GT model identity, text generation and bounded chat context. Requests follow session or workload authorization and the model catalog.
Checks service access, model availability and usage policy before processing a request. Service credentials and operational configuration stay on the server.
Run tests, apply changes and deploy only under your own isolation and approval policy. A generated plan is input to that process, not permission to execute it.
04 / FOR DEVELOPERS
The current browser contract uses a same-origin session and CSRF protection. It returns a completed text response. Tool execution, output validation and subsequent actions are implemented by your application.
Read the current catalog and choose a supported family. Availability, workload permission and service health are independent checks.
The browser example uses a same-origin session and CSRF. For backend integrations, create a model-scoped server key in API Access and use the responses endpoint with an Idempotency-Key.
Provide only the relevant, authorized context and a clear output request. Keep credentials and private tool results outside a guest session.
Accept completed results, handle errors explicitly and review the content. Reconcile an uncertain outcome before retrying a sensitive downstream operation.
// Run from a page on the Galactre origin. Nothing runs until you call it.
async function prepareReview(message) {
const catalog = await fetch('/api/v1/chat/models').then(r => r.json());
if (!catalog.models?.some(m => m.family === 'Lunar' && m.available)) {
throw new Error('Lunar is not currently available.');
}
const session = await fetch('/api/v1/chat/session', {
credentials: 'same-origin'
}).then(r => r.json());
if (!session.chat_available || !session.csrf_token) {
throw new Error('Chat is temporarily unavailable.');
}
const response = await fetch('/api/v1/chat/generate', {
method: 'POST', credentials: 'same-origin',
headers: {
'Content-Type': 'application/json',
'X-CSRF-Token': session.csrf_token
},
body: JSON.stringify({ model: 'gt-lunar', message, request_key: 'example_' + crypto.randomUUID().replaceAll('-', '') })
});
const result = await response.json();
if (response.status === 429) {
throw new Error('Rate limited. Honor the Retry-After header.');
}
if (!response.ok || result.status !== 'completed') {
throw new Error('Inspect the request outcome before retrying.');
}
// Review this text. It is not a tool command or execution approval.
return { text: result.response, conversationId: result.conversation_id };
}05 / KEEP CONTROL OF THE WORK
Design access and recovery around the actions your application actually performs. Give the model only the context needed for the current task.
Guest history belongs to its browser session; signed-in history is separate. Conversation reads and deletion are scoped to the current identity. Guest access does not grant workspace permissions.
The browser uses a server session and CSRF protection. Service credentials are configured server-side, with access checked before execution.
Check current guest limits from the session endpoint and honor 429 / Retry-After. A timeout or indeterminate result requires inspection; it is not proof that downstream work never happened.
Code writes, commands, payments and deployments need permissions enforced by your application. This chat release does not expose a tool execution API or grant agents those capabilities.
Review data processing and retention before supplying sensitive material. Read the privacy policy
06 / WHAT YOU CAN USE
Capability status below describes the current product implementation. Runtime access still depends on your session, the model catalog, limits and service health.
Guest and signed-in chat, subject to model availability, quotas and execution policy.
Saved conversations scoped to the current identity, with bounded recent messages as context.
Discuss supplied code or excerpts. No automatic repository access, browsing or document retrieval.
A native planner, delegated agents, dependencies and run dashboard are not available in this release.
No public shell, file execution, deployment tool or managed sandbox endpoint is provided by GT chat.
A public MCP server, on-chain agent registry, agent wallet and autonomous settlement API have not been published.
The model catalog could not be reached. Reload before selecting a model.
gt-lunarStatus unavailableGT Stellargt-stellarStatus unavailableGT Nebulargt-nebularStatus unavailableGT Cosmicgt-cosmicStatus unavailableRoadmap items have no release date on this page. Buying credits does not activate an unavailable capability.
07 / QUESTIONS, ANSWERED
Pin an available exact release when validating a repeatable workflow. Use a family default when you deliberately want future approved promotions. Record the resolved model ID with each result; model versioning does not grant execution tools or external system permissions.
GT is the AI model family developed by Galactre, with model access and text conversation available through the Galactre service. The agent platform direction extends that foundation, but native multi-agent scheduling, hosted tools and execution sandboxes are not available in this release. The workflow examples show how an application can use the model step.
When guest chat is enabled, you can open a sample prompt as a draft and send a limited Lunar request. Guest access does not read a repository, run tools or unlock a workspace. Review the session limits before sending.
This chat release generates text. It can propose a change or a checklist from supplied information, but a consuming application must separately provide repository access, an isolated runner and the required approval policy before any real action.
Start with the published Galactre integration contract and its current access requirements. Your application owns retrieval, tools, approvals and execution. Native integrations are documented as available only after their service contract and operational deployment have been verified.
No. Recent messages provide bounded conversation context. Document ingestion, search, durable agent memory and retrieval permissions require separate systems controlled by your application. Supply only the material the current task is allowed to use.
The minimal example requests JSON. Set stream to true for real SSE events and use the request cancel endpoint to stop delivery. Signed-in browser conversations can retrieve selected private knowledge and use calculator or current-time tools. Server keys cannot delegate those private sources. Arbitrary tools and execution sandboxes are not released.
Read the developer contract, verify a supported access path, test with representative inputs and define limits, error handling and review requirements. Keep external actions behind your own permissions, audit and recovery process.
START WITH ONE USEFUL STEP
Try an available GT model, inspect the result and design the workflow around evidence.