Story Creation and Translation AI Agent with Studio Chat, CLI, and TUI - use for long-form novels, short fiction, scripts, storyboards, interactive-film projects, open-world / branching play, fan fiction, spinoffs, style imitation, continuations, covers, and multilingual EPUB/PDF/TXT/Markdown translation. Includes Agent Skills, traceable research, governed context, persistent story state, multi-model routing, image services, and InkOS Studio.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Story Creation and Translation AI Agent with Studio Chat, CLI, and TUI - use for long-form novels, short fiction, scripts, storyboards, interactive-film projects, open-world / branching play, fan fiction, spinoffs, style imitation, continuations, covers, and multilingual EPUB/PDF/TXT/Markdown translation. Includes Agent Skills, traceable research, governed context, persistent story state, multi-model routing, image services, and InkOS Studio.
InkOS is a story creation and multilingual translation AI agent for long-form novels, short fiction, scripts, storyboards, interactive-film projects, fan works, continuations, covers, open-world / branching interactive play, and long-document localization. Prefer the Studio Chat / action-surface workflow for natural-language requests: the model proposes or invokes typed actions, InkOS executes them, and completion is derived from real tool results and files, not from prose claims.
Long-form writing still uses the chapter pipeline internally:
Input governance: Architect / Planner / Composer preserve author intent, current focus, outline sections, and relevant truth files instead of injecting everything blindly.
Writing: Writer produces prose with length governance, craft rules, and context selected for the current task.
Settlement and review: Observer / Reflector update runtime state; Auditor checks continuity and quality; Reviser handles critical issues. The default write cycle keeps automatic repair conservative and leaves unresolved issues visible for human or agent follow-up.
Truth files are persisted as schema-validated JSON (story/state/*.json) with markdown projections for human readability. SQLite temporal memory database (story/memory.db) enables relevance-based retrieval on Node 22+.
Persisted story memory is isolated to its project and book, excludes credentials and unrelated files, and is never reused across projects unless the user explicitly imports material. Users can inspect or delete the owning book/project through Studio or CLI.
v1.7.2 Mental Model
Treat InkOS as a confirmable action system, not a bag of prompt shortcuts. v1.7.2 replaces the former InkOS-private Skill protocol with standard AgentSkills / OpenClaw SKILL.md packages. Skills provide professional guidance and static references only: they can be selected explicitly or activated by the Chat Agent through use_skill, but they never grant execution permissions.
Natural-language requests should go through Studio Chat / TUI / inkos interact whenever possible.
Do not infer success from assistant prose. A book, short, cover, or play step is complete only when the corresponding tool result and files exist.
Use short_fiction_run only for a standalone short-fiction package.
Use generate_cover only for cover generation/regeneration.
Use play_start / play_step for Open World or Branching Interactive sessions.
Use script / storyboard / interactive-film tools only for production artifacts that should be saved and exported, not for casual discussion.
Use the translation project workflow for EPUB, text-based PDF, TXT, or Markdown localization. Keep source and target languages, glossary, review report, and export format explicit; do not replace it with an ad hoc one-turn translation when the user wants a complete deliverable.
Use research_web only when the user explicitly asks for external facts, market references, era/profession details, or worldbuilding research. Research reports are reference material and do not automatically mutate canon or prose.
Use long-form chapter tools only for existing long-form books.
Use narrative forecasts when the author wants to compare possible long-form directions before writing. A forecast is non-canonical planning material: selecting a branch may write selected-branch-plan.md, but it must not be described as changing prose, outlines, or canonical state.
A running production task does not prevent ordinary discussion, but do not start another conflicting book mutation until that task reaches a terminal state.
Agent Skills provide professional guidance and static references. They do not grant new file, network, image, or writing permissions by themselves.
Context is governed: protected facts and current intent should not be silently compressed away; compressible history may be summarized when the context budget is tight.
Studio Chat can receive user-uploaded text / Markdown / image attachments. Text attachments are injected into the LLM context; image attachments require a vision-capable model.
External materials can be archived and retrieved later with evidence traces instead of relying on ad hoc pasted context.
Prompt packs are user-tunable in Studio Project Settings. Project overrides are saved under prompt/<pack>/<prompt>.md; do not edit generated artifacts just to change system behavior.
Long-form chapter revision from Chat passes the current user instruction into the reviser as a one-off brief. If the revision is not applied, inspect the returned gate metrics and remaining audit issues before claiming it was fixed.
v1.7.0 added complete multilingual translation/localization, English-native short/script/storyboard/interactive-film paths, existing-novel import from Chat, configurable review and revision gates, abortable long tasks, recoverable write locks, material archive/retrieval, and Studio-editable prompt packs. v1.7.1 added non-canonical narrative forecasting, background production tasks, retryable task state, whole-book backup / restore, and rollback-safe latest-chapter deletion. Still surface unresolved review or execution issues plainly instead of claiming they were fixed.
When to Use InkOS
English novel writing: Native English support with 10 genre profiles (LitRPG, Progression Fantasy, Isekai, etc.). Set --lang en
Chinese web novel writing: 5 built-in Chinese genres (xuanhuan, xianxia, urban, horror, other)
Fan fiction: Create fanfic from source material with 4 modes (canon, au, ooc, cp)
Batch chapter generation: Generate multiple chapters with consistent quality
Import & continue: Import existing chapters from a text file, reverse-engineer truth files, and continue writing
Style imitation: Analyze and adopt writing styles from reference texts
Spinoff writing: Write prequels/sequels/spinoffs while maintaining parent canon
Standalone short fiction: Generate a complete short-fiction package with outline, draft, review artifacts, synopsis, selling points, and optional cover image
Cover generation: Generate or regenerate only a cover prompt and cover image from a title, synopsis, or visual direction without rerunning story writing
Interactive worlds: Start Open World or Branching Interactive sessions with world contracts, character agents, inventory/evidence/relationship state, guided choices, free actions, and optional image generation
Scripts and storyboards: Convert ideas, outlines, or prose into script/storyboard deliverables while preserving user format choices
Long-document translation: Translate EPUB, text-based PDF, TXT, or Markdown by chapter and semantic segment, maintain terminology, review source and target side by side, and export TXT/Markdown/EPUB
Agent Skills: Load standard AgentSkills/OpenClaw or project-local SKILL.md packages; let the Chat Agent invoke them from user intent, or force one with @skill-id
Traceable web research: Create sourced Markdown reports for facts, era/profession details, markets, and worldbuilding references
Quality auditing: Detect AI-generated content and perform 33-dimension quality checks
Genre exploration: Explore trends and create custom genre rules
Analytics: Track word count, audit pass rate, and issue distribution per book
Initial Setup
First Time Setup
# Initialize a project directory (creates config structure)
inkos init my-writing-project
# Configure your LLM provider (OpenAI, Anthropic, or any OpenAI-compatible API)# Prefer --api-key-env so the key never appears in shell history:export OPENAI_API_KEY=sk-xxx
inkos config set-global --provider openai --base-url https://api.openai.com/v1 --api-key-env OPENAI_API_KEY --model gpt-4o
# For compatible/proxy endpoints, use --provider custom and point ONLY to trusted endpoints:# inkos config set-global --provider custom --base-url https://your-trusted-proxy.com/v1 --api-key-env OPENAI_API_KEY --model gpt-4o
Multi-Model Routing (Optional)
# Assign different models to different agents — balance quality and cost
inkos config set-model writer claude-sonnet-4-20250514 --provider anthropic --base-url https://api.anthropic.com --api-key-env ANTHROPIC_API_KEY
inkos config set-model auditor gpt-4o --provider openai
inkos config show-models
Agents without explicit overrides fall back to the global model.
Provider setup tip
When the user needs an aggregator provider, point them to Studio's service settings. InkOS includes kkaiapi and OpenRouter as optional aggregator choices. For kkaiapi, use:
# Check installation and configuration
inkos doctor
# View current config
inkos status
Common Workflows
Workflow 1: Create a New Novel
Initialize and create book:
inkos book create --title "My Novel Title" --genre xuanhuan --chapter-words 3000
# Or with a creative brief (your worldbuilding doc / ideas):
inkos book create --title "My Novel Title" --genre xuanhuan --chapter-words 3000 --brief my-ideas.md
Genres: xuanhuan (cultivation), xianxia (immortal), urban (city), horror, other
InkOS maintains structured runtime state, readable Markdown projections, control docs, and temporal memory for consistency
If only one book exists, omit book-id for auto-detection
Review and approve:
inkos review approve-all
Workflow 2.5: Shared Natural-Language Control (Recommended For OpenClaw)
When InkOS is being driven by OpenClaw or another external agent, prefer the shared interaction executor instead of stitching together many ad-hoc CLI calls:
inkos interact --json --message "continue the current book, but keep the pacing tighter"
inkos interact --json --message "rewrite chapter 3"
inkos interact --json --message "start an open-world detective game about a locked archive room"
The current JSON payload contains:
assistant response text
interaction session id / session kind / active book id when bound
Real completion still comes from tool results and files. Do not treat assistant prose alone as proof that a book, chapter, short, cover, or play step was created.
Use this as the primary OpenClaw entry because it shares the same control layer as the project TUI.
Workflow 2.6: Steering Chapter Focus Before Writing
Use this when the user says things like "pull focus back to the mentor conflict", "pause the merchant guild subplot", or "change what the next chapter should prioritize".
Update the book-level control docs when needed:
Use update_author_intent to change the long-horizon identity of the book
Use update_current_focus to change the next 1-3 chapters' focus
Compile the next chapter intent:
plan_chapter(bookId, guidance?)
Generates story/runtime/chapter-XXXX.intent.md
Use this to verify what the system thinks the next chapter should do
Selection writes only story/runtime/narrative-forecasts/<forecast-id>/selected-branch-plan.md. It does not apply the plan to chapter prose, outlines, author intent, or canonical state. Any later application remains a separate explicit authoring action.
Workflow 3: Import Existing Chapters & Continue
Use this when you have an existing novel (or partial novel) and want InkOS to pick up where it left off.
Import from a single text file (auto-splits by chapter headings):
inkos import chapters book-id --from novel.txt
Automatically splits by 第X章 pattern
Custom split pattern: --split "Chapter\\s+\\d+"
Import from a directory of separate chapter files:
Total chapters, word count, average words per chapter
Audit pass rate and top issue categories
Chapters with most issues, status distribution
Token usage stats: total prompt/completion tokens, avg tokens per chapter, recent trend
Workflow 10: Write an English Novel
# Create an English LitRPG novel (language auto-detected from genre)
inkos book create --title "The Last Delver" --genre litrpg --chapter-words 3000
# Or set language explicitly
inkos book create --title "My Novel" --genre other --lang en
# Set English as default for all projects
inkos config set-global --lang en
Each genre has dedicated pacing rules, fatigue word lists (e.g., "delve", "tapestry", "testament"), and audit dimensions
Use inkos genre list to see all available genres
Workflow 11: Fan Fiction
# Create a fanfic from source material
inkos fanfic init --title "My Fanfic" --from source-novel.txt --mode canon
# Modes: canon (faithful), au (alternate universe), ooc (out of character), cp (ship-focused)
inkos fanfic init --title "What If" --from source.txt --mode au --genre other
Imports and analyzes source material automatically
Fanfic-specific audit dimensions and information boundary controls
Ensures new content stays consistent with source canon (or deliberately diverges in au/ooc modes)
Workflow 12: Edit Persistent Text Through Chat
Use Studio Chat or inkos interact for small, explicit edits to generated text artifacts. Treat the chat layer like an external editor: it may edit persisted files, then the writing pipeline can continue from the updated state.
When the user asks for a rename or targeted replacement, keep the request explicit and scoped. Prefer Studio Chat / inkos interact over hidden slash shortcuts; the agent should route the edit through the shared action surface and report which file changed.
Examples:
"把当前书里角色 林烬 改成 张三，先说明会影响哪些文件。"
"只改第 5 章，把这句旧文本换成新文本，改完标记需要复核。"
Workflow 14: Interactive TUI Dashboard
inkos tui
Launches a full-screen Ink + React dashboard with conversational creation
Slash command autocomplete (Tab), input history (arrow keys)
Themed activity animations per operation (writing, auditing, revising, planning)
Bilingual i18n (Chinese / English)
Shares the same interaction kernel as inkos interact and Studio
Workflow 15: Standalone Short Fiction Package
Use this when the user wants a complete short story or short-fiction deliverable that is separate from the active long-form book.
inkos short run \
--direction "modern short fiction marriage reversal evidence-driven heroine" \
--chapters 12 \
--chars 1000
Outputs are written under shorts/<story-name>/final/:
full.md — complete short-fiction manuscript
sales-package.md — synopsis and selling points
cover-prompt.md — cover prompt
cover.png — cover image when a cover provider is configured
For OpenClaw/Studio/agent orchestration, call the short_fiction_run tool when the user asks for a new complete short-fiction package. Do not use it for the next chapter of an existing long-form book.
Workflow 16: Standalone Cover Tool
Use this when the user only wants a cover for an existing title, synopsis, or visual direction. Do not rerun the short-fiction pipeline.
In Studio or agent mode, ask naturally:
Generate a short-fiction cover for "The Divorce Papers He Regretted", modern city, high-drama reversal.
For tool-using agents, call generate_cover with:
title — required
intro or sellingPoints — optional story context
coverPrompt — optional visual direction
outputDir — optional; defaults to covers/<title>/
The standalone cover tool writes:
covers/<title>/cover-prompt.md
covers/<title>/cover.png
If cover image generation fails, report the provider/configuration error plainly. Do not rewrite the story, do not rerun short_fiction_run, and do not suggest unrelated external tools unless the user asks.
Workflow 17: Open World / Branching Interactive Play
Use this when the user wants to play inside an interactive world instead of generating a finished manuscript.
In Studio or agent mode, ask naturally:
Create a Warcraft-like border watchtower open world. Time can advance differently by action: patrols take an hour, training can take days. Equipment should show rarity through material and atmosphere, not stat blocks.
For tool-using agents:
Call play_start when there is no active world/run yet, or when the user explicitly asks to start a new world.
Call play_step when the user performs an action inside an existing world.
Keep Open World free-form: do not force clickable choices unless the current session is Branching Interactive.
If the user changes world rules, persona, visual contract, or character behavior, treat it as a world-state edit or a new instruction for the next step, not as long-form chapter writing.
If image generation is configured, let Play generate scene / character / item / evidence images through the Play image path. Do not call the short-fiction cover tool for Play scene images.
Workflow 18: Agent Skills
Use this when the user wants reusable professional rules, a domain-specific writing mode, or a forced capability for the current Chat turn.
Project-local skills live at:
.agents/skills/<skill-id>/SKILL.md
InkOS also discovers standard AgentSkills / OpenClaw locations (skills/, .agents/skills/, ~/.agents/skills/, and ~/.openclaw/skills/). Studio can import a complete skill folder with its static reference files.
External skill directories can be loaded with:
export INKOS_SKILL_DIRS=/abs/path/to/skills
Guidelines for agent orchestration:
Let the Chat Agent inspect the available skill catalog and call use_skill when the current user intent needs that expertise. Do not emulate this with session-kind routing, keyword lists, or substring matching.
Force a skill by including @skill-id in the user message when the user explicitly chooses one.
Treat skills as standard expertise packets containing instructions and static references. Prompt packs and governed context recipes are separate InkOS systems.
Skill folders may contain static references. Read them only when needed, and never auto-execute bundled scripts.
Do not treat skills as permissions. File edits, book creation, chapter writing, image generation, and exports still require the normal InkOS tools and confirmation gates.
Workflow 19: Traceable Web Research
Use this when the user asks for real-world references, external facts, era/profession details, market references, or worldbuilding research.
For tool-using agents, call research_web with:
topic — the research question
purpose — worldbuilding, era, profession, market, fact-check, or general
depth — optional: quick, standard, or deep
The tool writes a Markdown report under:
.inkos/research/
The report includes sources, claims, unknowns, conflicts, query logs, and confidence. It is reference material only. If research should change canon, wait for explicit user confirmation and then use the normal truth-file editing path.
Search credentials are user/project supplied. Studio can configure a Tavily-compatible search API, or the server can use TAVILY_API_KEY from the environment.
Workflow 20: Script, Storyboard, and Interactive-Film Creation
Use this when the user wants a production artifact rather than a casual answer:
In Studio Chat, these actions should be proposed with a confirmation card first. After confirmation, InkOS writes the artifact and reports the saved files. Do not hand-write a fake "created" result in prose.
Use a translation project when the user wants a complete, reviewable deliverable rather than a one-off translated paragraph. Inputs can be EPUB, text-based PDF, TXT, or Markdown; source and target languages can be written as normal language names in Studio.
inkos translate init --from ./source.epub --source Chinese --target English
inkos translate run <project-id>
inkos translate export <project-id> --format epub
Preserve the project glossary and chapter boundaries across translation batches.
Review source and translation side by side; treat the generated review report as the quality record.
Export TXT, Markdown, or EPUB only after the requested segments are complete.
For scanned PDFs without a text layer, run OCR before importing; InkOS currently reads text-based PDFs.
InkOS Studio (Web Workbench)
inkos studio launches a local web UI (default port 4567) that provides a visual interface for all InkOS operations:
Book management — create, delete, export (TXT/MD/EPUB), configure per-book settings
Short fiction & cover tools — generate independent short-fiction packages, synopsis/selling points, cover prompts, and standalone covers
Open World / Branching Interactive — start and continue interactive worlds with world contracts, free actions, clickable choices, HUD state, and image generation
Interactive-film workbench — create and inspect branch nodes, variables/flags, endings, node images, and export packages
Script / storyboard tools — generate production-oriented script and storyboard files from ideas, prose, or reference notes
Translation workbench — import EPUB, text-based PDF, TXT, or Markdown; choose source and target languages; translate, compare, review, and export complete projects
Agent Skills management — list standard skills, import AgentSkills/OpenClaw folders with static references into .agents/skills/, let Chat invoke skills from intent, and force skills from Chat
Research search provider — configure external web search API credentials for research_web
Chapter review & editing — approve/reject drafts, edit content inline, and revise with polish/spot-fix/rewrite/rework modes
Real-time writing progress — SSE-based live updates during chapter generation
Market radar — AI-powered trend analysis with platform/genre recommendations
Daemon control — start/stop background writing with event log
Truth file editor — view and edit canonical knowledge base per book
Config editor — LLM provider, model routing, cover/image services, notifications
inkos studio # Start on default port 4567
inkos studio -p 8080 # Start on custom port
The Studio Chat surface shares the same action kernel as TUI and CLI. It can answer questions, propose/confirm creation and translation actions, run Short, generate covers, start Play, import existing novels, edit persistent text artifacts, and invoke long-form writing operations.
Advanced: Natural Language Agent Mode
For flexible, conversational requests:
inkos agent "写一部都市题材的小说，主角是一个年轻律师，第一章三千字"
Agent interprets natural language and invokes appropriate commands
Useful for complex multi-step requests
Input Governance Tools
These tools are the preferred control surface for chapter steering:
plan_chapter(bookId, guidance?)
Generates chapter intent for the next chapter
Use before writing when the user wants to change focus
Use only when the user asks for a separate complete short story / short-fiction deliverable
generate_cover
Generates only a cover prompt and cover image
Writes to covers/<title>/ by default
Use when the user asks to create or regenerate a cover for an existing title, synopsis, or completed short
Also use when the user changes the cover prompt through chat; pass the revised visual direction as coverPrompt and reuse the existing outputDir when available
Do not rerun story generation unless the user explicitly asks for a new story
play_start
Starts a new Open World or Branching Interactive run
Use when the user asks to play in a world, simulate an interactive story, create a game-like scene, or start a free-action/choice-based session
The user's world contract should carry time rules, character agency, item/evidence rules, tone, genre, and visual style when provided
play_step
Advances an existing Play run by one user action
Use for free-form actions such as "inspect the letter", "talk to the guard", "train for three days", or "choose option 2"
Do not use it to write the next chapter of a long-form book
research_web
Collects external sources and writes a traceable Markdown research report
Use only for explicit research/fact-check/worldbuilding/market requests
Never mutate canon or prose directly from research output without explicit user confirmation
InkOS maintains each book's memory in three layers:
Structured state: story/state/*.json is the authoritative runtime state, validated by Zod schemas.
Readable projections: current_state.md, pending_hooks.md, chapter_summaries.md, character_matrix.md, and related Markdown files are for humans and debugging.
Temporal memory: story/memory.db on Node 22+ supports relevance-based retrieval of facts, hooks, and chapter summaries.
Agents use the governed composer to select the relevant parts for the current task instead of blindly injecting every file. During import chapters, InkOS rebuilds structured state and projections from existing content via the ChapterAnalyzerAgent.
Multi-Phase Writer Architecture
The Writer operates across multiple phases with specialized agents:
Planner: Generates chapter intent with structured hook agenda (mustAdvance, eligibleResolve, staleDebt) based on memory retrieval.
Composer: Selects relevant context from structured state, control docs, readable projections, and retrieval results, then compiles rule stack and runtime artifacts.
Phase 1 (Creative, temp 0.7): Generates prose with length governance, English variance brief (anti-repetition), and dialogue-driven guidance.
Phase 2a (Observer, temp 0.5): Over-extracts 9 categories of facts from the chapter text.
Phase 2b (Reflector, temp 0.3): Outputs a JSON delta with hookOps (upsert/mention/resolve/defer), currentStatePatch, and chapterSummary. Code-layer validates via Zod schema and applies immutably.
Normalizer: Single-pass compress/expand to bring chapter length into the target band. Safety net rejects destructive normalization (>75% content loss).
Auditor: 33-dimension check including hook health analysis (stale debt, burst detection, no-advance warnings).
Reviser: Attempts one configured repair pass for critical issues, then keeps unresolved findings visible for human or agent follow-up.
Truth files use structured JSON (story/state/*.json) as the authoritative source, with markdown projections for human readability. Hook admission control prevents duplicate/family hooks from inflating the hook table.
Context Guidance
The --context parameter provides directional hints to the Writer and Architect:
inkos write next book-id --count 2 --context "protagonist discovers betrayal, must decide whether to trust mentor"
Context is optional but highly recommended for narrative coherence
--json, --message, --book. Primary entry for OpenClaw
inkos tui
Launch TUI dashboard
Full-screen Ink + React interactive dashboard
Error Handling
Common Issues
"book-id not found"
Verify the ID with inkos book list
Ensure you're in the correct project directory
"Provider not configured"
Run inkos config set-global with valid credentials
Check API key and base URL with inkos doctor
"Context invalid"
Ensure --context is a string (wrap in quotes if multi-word)
Context can be in English or Chinese
"Audit failed"
Check chapter for encoding issues
Ensure chapter-words matches actual word count
Try inkos revise with --mode rewrite
"Book already has chapters" (import)
Use --resume-from <n> to append to existing chapters
Or delete existing chapters first
Running Daemon Mode
For long-running operations:
# Start background daemon
inkos up
# Stop daemon
inkos down
# Daemon auto-processes queued chapters
Tips for Best Results
Provide rich context: The more guidance in --context, the more coherent the narrative
Start with style: If imitating an author, run inkos style import before generation
Import first: For existing novels, use inkos import chapters to bootstrap truth files before continuing
Review regularly: Use inkos review to catch issues early
Monitor audits: Check inkos audit metrics to understand quality bottlenecks
Use spinoffs strategically: Import canon before writing prequels/sequels
Batch generation: Generate multiple chapters together (better continuity)
Check analytics: Use inkos analytics to track quality trends over time
Export frequently: Keep backups with inkos export
Security & Trust
License: the ClawHub skill descriptor is MIT-0 per platform policy, but the underlying @actalk/inkos, @actalk/inkos-core, and @actalk/inkos-studio npm packages are AGPL-3.0-only. Running InkOS and distributing modified versions are governed by AGPL. Full source on GitHub for auditability.
No install hooks: npm package has no preinstall/postinstall/install scripts. Install is inert.
Documented file locations: manuscripts, story state, logs, imported Skills, and project secrets stay under the selected project directory. Optional global CLI configuration may be stored under ~/.inkos/; user-level Skills may be read from ~/.agents/skills/ and ~/.openclaw/skills/.
Project-isolated retention: each project's manuscripts, state, and memory remain in that project until the user deletes the book or project. Do not reuse one project's persisted memory in another project unless the user explicitly imports that material.
No InkOS telemetry: InkOS does not send usage analytics to an InkOS-controlled service. Content can leave the machine when the user invokes a configured LLM, image, web-search, aggregator, or custom provider; review each provider's endpoint and data policy before enabling it.
Credential handling: prefer Studio secret settings or environment-backed API keys over literal values. Agents and imported Skills must never read, print, summarize, or transmit credentials; secret stores must stay outside prompts, exports, archives, and commits.
Custom provider base-URL: --provider custom forwards your API key to whatever URL you specify. Only point it at endpoints you trust (your own proxy or an audited reverse-proxy). Never paste an untrusted --base-url.
Local services: InkOS requires no sudo. Studio opens a localhost listener on port 4567 by default (or the port selected by the user), and daemon mode runs only when explicitly started.
