Glyph
Glyph is a vendor-agnostic Python SDK and CLI for building agent workflows with OpenAI and Anthropic models.
It is designed for flows where some steps should stay deterministic and only the parts that actually need an LLM should call one.
Glyph has two core use cases:
- A vendor-agnostic agent SDK
- A workflow builder that can act like a
SKILL.mdexecutor
Table of contents
Markdown Workflow Example
This example demonstrates how Glyph can execute workflows described entirely in Markdown.
Each step in your workflow can do one of the following:
- If it includes an
execute:key, or contains a Python or Bash code block, Glyph will run the code automatically for you. - If the step contains plain text, Glyph treats it as a prompt to the selected language model and generates a response.
This lets you blend deterministic logic and LLM-powered actions seamlessly in a single document.
---
name: writePostcard
description: if the user asks for a postcard, follow these steps
options:
model: gpt-5.4-mini
reasoning_effort: medium
allowed_tools: [Read, Glob, Grep]
---
<!-- Step sections are mandatory -->
## Step: loadTripContext
<!-- This step is executed by the framework and not by an LLM.
Code steps are compatible with bash and python
-->
```python
return {
"city": "Lisbon",
"mood": "warm and nostalgic",
"memory": "the yellow tram climbing the hill at sunset",
}
```
<!-- You can also provide a file name like
execute:
file: my_file.py | my_file.sh
function: optional function to execute, otherwise will fallback to main() for python file
-->
## Step: draftPostcard
<!-- If a step contains only text, it is considered as a prompt.
Glyph will trigger an agent using the options at the top of the file.
-->
<!-- Glyph fills template variables from previous step output. -->
Write a short postcard message from {{ city }}.
The mood should feel {{ mood }}.
Mention this memory: {{ memory }}.
Keep it to 3 sentences maximum.
## Step: savePostcard
<!-- Each step receives the previous step result automatically in a variable
called step_input.
In the case of an agent step, you can access the message using step_input.message
-->
```python
from pathlib import Path
output_path = Path(__file__).with_name("postcard.txt")
output_path.write_text(step_input.message, encoding="utf-8")
return {"file_path": str(output_path)}
```
<!-- This is a hint for readibility purpose and is not required. -->
returns:
file_path: str
Run the workflow with:
glyph workflow.md
Pass first-step input from the CLI with --initial-input (or -i). The value
must be valid JSON and can be an object, array, or scalar:
glyph workflow.md --initial-input '{"topic":"foo"}'
glyph workflow.md -i '"foo"'
Prompt-only Markdown steps can also override the workflow default model with a
step-level model: key:
---
options:
model: gpt-5.4-mini
---
## Step: draftBlurb
model: gpt-4.1-mini
Write one crisp sentence about {{ topic }}.
Use a model from the same provider as the workflow default. See
examples/21_workflow_markdown_model_override/.
Install
pip install glyph-agents # install in a virtualenv if you want the SDK
pipx install glyph-agents # install only the glyph CLI
Requires Python >=3.10.
Provider API keys
Glyph reads OPENAI_API_KEY and ANTHROPIC_API_KEY the same way the vendor SDKs
do: primarily from your process environment.
To persist keys and not having to export them in every new shell, run:
glyph auth
Glyph Python SDK
Quickstart (query helper)
import asyncio
from glyph import AgentOptions, AgentQueryCompleted, AgentText, query
async def main() -> None:
options = AgentOptions(
model="gpt-4.1-mini", # or "claude-haiku-4-5"
instructions="You are concise and accurate.",
)
async for event in query(
prompt="In one sentence, explain what an API is.",
options=options,
):
if isinstance(event, AgentText):
print(event.text, end="")
elif isinstance(event, AgentQueryCompleted):
print("\n\nis_error:", event.is_error)
print("usage:", event.usage)
print("total_cost_usd:", event.total_cost_usd)
if __name__ == "__main__":
asyncio.run(main())
Streaming with GlyphClient
Use GlyphClient when you want explicit control of turn lifecycle methods:
query(...)thenreceive_response(...): send one prompt now, stream that prompt's events right after.query_streamed(...): same behavior as above, but in one call.query_and_receive_response(...): run one prompt and return all events at once (no streaming loop).receive_messages(...): use this when you queued multiple prompts withquery(...)first and want to drain them in order from a single stream.
import asyncio
from glyph import AgentOptions, AgentQueryCompleted, AgentText, AgentThinking, GlyphClient
async def main() -> None:
options = AgentOptions(model="gpt-4.1-mini")
async with GlyphClient(options) as client:
async for event in client.query_streamed("List two benefits of unit tests."):
if isinstance(event, AgentThinking):
print("[thinking]", event.text)
elif isinstance(event, AgentText):
print(event.text, end="")
elif isinstance(event, AgentQueryCompleted):
print("\n\n[done]", event.is_error, event.stop_reason, event.usage)
if __name__ == "__main__":
asyncio.run(main())
Event Types
All APIs stream normalized AgentEvent values:
AgentText: visible assistant text segmentsAgentThinking: reasoning/thinking segments when availableAgentToolCall: structured tool invocation requestsAgentToolResult: structured tool invocation resultsAgentQueryCompleted: end-of-turn status (is_error,stop_reason,usage,total_cost_usd,extra)
Backend failures are surfaced as AgentQueryCompleted(is_error=True, ...).
AgentOptions
AgentOptions is the shared configuration surface:
model(required): determines backend automaticallyinstructions: system prompt / instructionsname: OpenAI agent display name (default:"Assistant")cwd: workspace root for tool accessallowed_tools: activation allow-list using Claude-style tool names (Read,Write,Edit,Glob,Grep,Bash,WebSearch,WebFetch).- Any tool not listed is disabled.
None/empty means no built-in tools are activated.
permission:PermissionPolicy(edit_ask=True, execute_ask=True, web_ask=True)enables interactive confirmation per capability.edit_askapplies to file mutation actions (Write/Edit).execute_askapplies to command actions (Bash).web_askapplies to web actions (WebSearch/WebFetch) (WebSearchask is not supported for OpenAI models).- Flags default to
False, so capabilities are auto-allowed when the corresponding tool is active.
approval_handler_edit: custom approval callback for edit/write actionsapproval_handler_execute: custom approval callback for command execution actionsapproval_handler_web: custom approval callback for web actions (WebSearch/WebFetch)max_turns: backend turn cap overridebash_timeout_ms: OpenAI Bash tool default timeout overridereasoning_effort/reasoning_summary: OpenAI-only reasoning controls
Approval Handlers (edit vs execute)
When permissions are set to ask, Glyph can call capability-specific approval handlers:
approval_handler_edit: used forWrite/Editstyle operationsapproval_handler_execute: used forBashstyle operationsapproval_handler_web: used forWebSearch/WebFetchstyle operations
If a handler is missing, Glyph falls back to interactive TTY approval prompts. In non-interactive contexts (server/worker/CI), missing handlers will cause the action to be denied with a clear error message.
from glyph import AgentOptions, ApprovalDecision, PermissionPolicy
def approve_edit(req):
# req.capability == "edit"
return ApprovalDecision(allow=True)
def approve_execute(req):
# req.capability == "execute"
commands = (req.payload or {}).get("commands", [])
allowed = all("rm -rf" not in c for c in commands)
return ApprovalDecision(
allow=allowed,
reason=None if allowed else "Dangerous command blocked",
)
options = AgentOptions(
model="gpt-5.4",
permission=PermissionPolicy(edit_ask=True, execute_ask=True, web_ask=True),
approval_handler_edit=approve_edit,
approval_handler_execute=approve_execute,
)
Workflows
GlyphWorkflow lets you compose multi-step flows where each step receives the
previous step result. Define steps with @step, or put the workflow in Markdown
and run it with glyph workflow.md.
import asyncio
import os
from glyph import AgentOptions, AgentQueryCompleted, GlyphWorkflow, step
class MyWorkflow(GlyphWorkflow):
options = AgentOptions(model=os.getenv("GLYPH_MODEL", "gpt-4.1-mini"))
@step
async def load_topic(self) -> str:
return "sea turtles"
@step(prompt="Write one short sentence about {topic}.")
async def ask_model(self, topic: str) -> None:
self.fill_prompt(topic=topic)
result: AgentQueryCompleted = yield
print(result.message)
async def main() -> None:
await MyWorkflow.run()
if __name__ == "__main__":
asyncio.run(main())
Python workflows (@step)
@step— plain Python step.@step(prompt=..., model=..., is_streaming=...)— LLM step;modeloverrides the workflow default for that step only.- LLM steps: set up
self.promptin the method body (fill_prompt, etc.). If the method does not useyield, the query runs after it returns. If it usesyield(async generator), that starts the turn: withis_streaming=Falseyou typically getAgentQueryCompletedafter the firstyield; withis_streaming=Trueeachyieldreceives the next streamedAgentEventuntilAgentQueryCompleted(seeexamples/16_workflow_streaming.py). self.fill_prompt(...)— render prompt templates without failing on missing placeholders (they stay in the text).self.next_step(self.some_step, value)— jump to another step with an explicit input.self.stop_workflow(value)— end the workflow immediately;GlyphWorkflow.run(...)returnsvalue.GlyphWorkflow.run(options=..., initial_input=..., session_id=...)— runtime overrides and optional first-step input.
Markdown workflows (## Step:)
GlyphWorkflow.from_markdown(path)andrun_markdown_workflow(path, ...)load a linear workflow from## Step:sections.- The first
## Step:is the entrypoint. - Each step can be an LLM prompt, an inline Python block, or an
execute:mapping (file plus optional function). <!-- ... -->comments are ignored by the loader.
Examples
Run from repository root:
python examples/01_query_helper.py
python examples/02_query_streamed.py
python examples/03_query_then_receive_response.py
python examples/04_query_and_receive_response.py
python examples/05_receive_messages_multiple_turns.py
python examples/06_sessions.py
python examples/07_tools_and_permissions.py
python examples/08_openai_reasoning.py
python examples/09_resolve_backend.py
python examples/10_claude_async_prompt_iterable.py
python examples/11_websearch_tool_calls.py
python examples/12_webfetch_tool_calls.py
python examples/13_basic_workflow.py
python examples/14_workflow_context.py
python examples/15_workflow_init_override.py
python examples/16_workflow_streaming.py
glyph examples/17_workflow_markdown/workflow.md
glyph examples/18_workflow_markdown_python/workflow.md
glyph examples/19_workflow_markdown_bash/worfklow.md
python examples/21_workflow_markdown_model_override/main.py
Metadata
Release files for glyph-agents 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| glyph_agents-0.3.0.tar.gz | 46.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| glyph_agents-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 99.7 kB
Release files / glyph_agents-0.3.0.tar.gz
| Download URL | glyph_agents-0.3.0.tar.gz |
|---|---|
| Size | 46.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb0957e08ac6f3713005df62668aa21e57a875a08ea5c63d09436f6f158ed33d
|
|
BLAKE2b-256 checksum How to use checksums |
60d75920746dffab79c9af1c0be755fd1840b8d6720694cb882958741e369577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / glyph_agents-0.3.0-py3-none-any.whl
| Download URL | glyph_agents-0.3.0-py3-none-any.whl |
|---|---|
| Size | 53.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2290fc8edd99cd368c47d2e7a3d78b2a6ff70af372a600e142b244e4b2c1c297
|
|
BLAKE2b-256 checksum How to use checksums |
8fbe521fe502c11bcadd014e1b85d06851ac1abe95e995af7bbe9c217a86c084
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for glyph-agents 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.