Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.3ngram.ai/llms.txt

Use this file to discover all available pages before exploring further.

What are actions?

When your AI identifies something that needs doing in an external system (post a GitHub comment, close a Linear issue), it proposes an action. You review and approve before anything executes. Nothing happens without your sign-off.

How it works

  1. Your AI (or a trigger) proposes an action via propose_action
  2. The action enters a pending queue
  3. You review pending actions in the dashboard, then approve or reject via the authenticated pending-action approval endpoint
  4. Approved actions execute immediately via the integration adapter

Supported action types

Action TypeProviderWhat it does
github_commentGitHubPosts a comment on an issue or pull request
linear_closeLinearTransitions a Linear issue to “Done” state

Proposing an action

Ask your AI to propose an action in natural language:
“3ngram: Propose a GitHub comment on owner/repo#42 saying ‘This has been resolved in the latest deploy’”
Under the hood, this calls propose_action with these parameters:
ParameterRequiredDescription
action_typeYesgithub_comment or linear_close
target_providerYesgithub or linear
target_refYesProvider reference (e.g. owner/repo#123 for GitHub)
payload_jsonYesJSON with action data (e.g. {"body": "comment text"})
reasonYesWhy this action is being proposed
source_memory_idNoMemory ID that prompted this action

Reviewing and deciding

Pending actions are reviewed in the 3ngram dashboard at app.3ngram.ai. Each pending action shows its type, target, reason, and proposed payload. Approve an action (executes immediately) — from the dashboard, or by asking your AI:
“3ngram: Approve action
Reject an action:
“3ngram: Reject action
Both decisions go through the authenticated pending-action approval endpoint. Once executed, the action moves out of the pending queue and its result is recorded.

Triggers + Actions

Triggers can automatically propose actions when events fire — for example, proposing a GitHub comment in response to a new blocker. The trigger only proposes; nothing runs without your approval. See Triggers for the event types that can fan out into proposals.
Actions require a paid subscription and a connected integration (GitHub or Linear). The action uses your integration credentials.