letta-ai/Letta Code Action

Tag @letta-code in issues/PRs to get help with code review, bug fixes, and feature implementation.

View on GitHub

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit May 12, 2026
License: Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: letta-ai/letta-code-action@b50e45b91c77d5a7b8a64f4088bedcd8c442bd13 # v0.0.6

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
trigger_phrase	The trigger phrase to look for in comments or issue body	no	@letta-code
assignee_trigger	The assignee username that triggers the action (e.g. @letta-code)	no	—
label_trigger	The label that triggers the action (e.g. letta)	no	letta-code
base_branch	The branch to use as the base/source when creating new branches (defaults to repository default branch)	no	—
branch_prefix	The prefix to use for Letta branches (defaults to 'letta/', use 'letta-' for dash format)	no	letta/
allowed_bots	Comma-separated list of allowed bot usernames, or '*' to allow all bots. Empty string (default) allows no bots.	no	""
allowed_non_write_users	Comma-separated list of usernames to allow without write permissions, or '*' to allow all users. Only works when github_token input is provided. WARNING: Use with extreme caution - this bypasses security checks and should only be used for workflows with very limited permissions (e.g., issue labeling).	no	""
prompt	Instructions for Letta. Can be a direct prompt or custom template.	no	""
letta_api_key	Letta API key (get one at https://app.letta.com)	no	—
letta_base_url	Letta API base URL (defaults to https://api.letta.com)	no	""
github_token	GitHub token with repo and pull request permissions. Use GITHUB_TOKEN or a token from actions/create-github-app-token for custom bot identity.	yes	—
letta_args	Additional arguments to pass directly to Letta CLI	no	""
additional_permissions	Additional GitHub permissions to request (e.g., 'actions: read')	no	""
use_sticky_comment	Use just one comment to deliver issue/PR comments	no	false
use_commit_signing	Enable commit signing using GitHub's commit signature verification. When false, Letta uses standard git commands	no	false
bot_id	GitHub user ID to use for git operations (defaults to letta-code)	no	248085862
bot_name	GitHub username to use for git operations	no	letta-code
track_progress	Force tag mode with tracking comments for pull_request and issue events. Only applicable to pull_request (opened, synchronize, ready_for_review, reopened) and issue (opened, edited, labeled, assigned) events.	no	false
tracking_comment	Create a tracking comment on the PR/issue showing working status and results. Set to 'false' to skip the initial and final tracking comments (agent can still leave inline review comments).	no	true
path_to_letta_executable	Optional path to a custom Letta Code executable. If provided, skips automatic installation and uses this executable instead.	no	""
path_to_bun_executable	Optional path to a custom Bun executable. If provided, skips automatic Bun installation and uses this executable instead. WARNING: Using an incompatible version may cause problems if the action requires specific Bun features. This input is typically not needed unless you're debugging something specific or have unique needs in your environment.	no	""
show_full_output	Show full JSON output from Letta Code. WARNING: This outputs ALL Letta messages including tool execution results which may contain secrets. Only enable for debugging.	no	false
model	Model to use for the Letta agent (e.g., opus, sonnet-4.5, haiku, gpt-4.1)	no	opus
agent_id	Specific Letta agent ID to use. If not provided, the action will find or create an agent automatically.	no	""

Outputs

name	description
execution_file	Path to the Letta Code execution output file
agent_id	The Letta agent ID used for this execution
conversation_id	The Letta conversation ID used for this execution (enables concurrent tasks)
branch_name	The branch created by Letta Code for this execution
github_token	The GitHub token used by the action