Takos Docs

テーマ切替

File Handlers ​

File handlers let installed apps open or edit selected file types from a Workspace. Takos discovers them through Capsule output projection, not through a Takos-specific manifest.

Current Flow ​

  1. Install an app Capsule from Git.
  2. Review and apply the Takosumi plan.
  3. The app exposes non-secret service metadata with a capability such as interface.file.handler.
  4. Takos reads the bound export and shows the handler for matching files in the Workspace.
  5. Runtime authority, when needed, comes from the deployed runtime/account-plane boundary rather than OpenTofu output values.

Takos Boundary ​

Takos owns the user-facing workspace experience: chat, agents, memory, Workspaces, and app launcher. Git, storage, agent runtime, file handlers, UI surfaces, and MCP are exposed through the Capsule Outputs and Takos runtime contracts. Takosumi records the run ledger (Capsule / Run / StateVersion / Output) for the applied OpenTofu Capsule, while Connections hold credential references, ProviderBindings resolve each provider (+ optional alias) to an explicit provider connection (an explicit ProviderConnection), and policy resolves provider allowlists and state handling. The Takosumi Accounts plane owns account-plane policy (OIDC / billing / dashboard).

Install Shape ​

json
{
  "spaceId": "space_1",
  "module": {
    "source": "github.com/example/takos//deploy/opentofu/cloudflare",
    "ref": "main"
  }
}

Selecting an adapter runs a plan type Run and then an apply type Run, which records StateVersion and non-sensitive endpoints as Output. Takos product routes rely on the Takosumi deploy-control ledger and Capsule output projection instead of exposing a separate product-local deployment surface.

References ​