Skip to main content

Attaché

A personal assistant you install with one command. It runs on your own machine, keeps your to-dos and reminders, makes interactive pages on demand, and learns how you work through a folder of skills it can edit itself. The core is under 2,100 lines of Python code, the cap CI enforces; everything else is a skill.

Status: phase 3 of the roadmap: the local core, terminal and web chat; Slack and Signal with group chats, approvals and rate limits; email (Outlook, Gmail, Titan) with a morning triage; Word, Excel and PowerPoint files; share links; and starting at login. The cloud arrives in phase 4.

Documentation: https://openafterhours.github.io/attache/.

Try it

uvx attache              # first run asks your name, creates ~/.attache, then opens a chat
uv tool install attache  # keep it
attache chat             # terminal chat, plus the web page
attache run              # web page, reminders and channels, no terminal chat
attache doctor           # check your setup
attache skill mail login gmail   # a skill's own setup step, run in your terminal
attache skill service install    # start Attaché when you log in

The web page: chat on the left, the Home page with to-dos and reminders on the right

The terminal and the web page are one conversation. Attaché prints a link like http://127.0.0.1:8765/#t=... when it starts; open that link to use the web page. The token in it changes every run, so other programs on your machine can't drive your assistant.

Attaché talks to models through four adapters, chosen in ~/.attache/attache.toml:

api Use it for
claude-cli Claude Code (claude -p) on your own login. Your own chats only.
anthropic The Claude API, or any Anthropic-compatible base_url
openai-chat Ollama, LM Studio, vLLM, llama.cpp, OpenRouter, Groq, Azure
openai-responses OpenAI reasoning models with tools
[routing]
own_chats   = "claude"      # your Claude login
group_chats = "claude-api"  # an API key, per Anthropic's terms

[endpoints.claude]
api   = "claude-cli"
model = "claude-sonnet-5-5"

[endpoints.claude-api]
api     = "anthropic"
model   = "claude-sonnet-5-5"
key_env = "ANTHROPIC_API_KEY"

How it is put together

  • Skills live in ~/.attache/skills/<name>/SKILL.md (Agent Skills format). Only names and descriptions go into the prompt. The assistant edits skills when you change how you work, and ~/.attache is a git repo, so attache skills log and attache skills undo <name> show and reverse every change.
  • Artifacts are HTML pages the assistant writes into ~/.attache/artifacts/. The local web server adds a small attache bridge so a page can read and write real data with live updates. Pages run sandboxed: they can't reach the internet or anything outside the data they declare.
  • Channels. Slack and Signal are skills that ship a small program, a sidecar, which Attaché starts with uv run and talks to over JSON lines. Any chat app can be added the same way: see docs/channels.md.
  • Mail is one skill with the same commands for Outlook (Outlook classic on this PC, or Microsoft Graph), Gmail and Titan. Bodies come back marked untrusted, every action is logged, and nothing is sent until you pick Send: see docs/mail.md.
  • Share links. With [web] public_url set and Tailscale Funnel pointed at a second local port, a group's page gets a link that works on anyone's phone, for that group's shared data only: see docs/pages.md.
  • Roles. You are the owner. Group members only reach what is shared with their chat, and never files, shell or email. Your own turns inside a group get member tools too, because the group's messages are untrusted. When a member asks for something only you can do, Attaché asks you first (buttons on Slack and the web page, a reaction or a typed reply elsewhere).
  • Claude Code runs as a backend with claude -p on your own login, for your own chats only. Attaché's tools reach it through an MCP endpoint on the local web server. It runs in a working folder next to your home (~/.attache-claude), so nothing written into ~/.attache can load as Claude Code project settings.

The full design, with the research behind it, is in docs/proposal.html.

Contributing

See CONTRIBUTING.md: bug fixes and simplifications go in the core, features go in skills.

License

MIT

Metadata

Release files for attache 0.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for attache 0.0.2
File Size Uploaded Provenance Actions
attache-0.0.2.tar.gz 673.0 kB With provenance Details for attache-0.0.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for attache 0.0.2
File Interpreter ABI Platform Actions
attache-0.0.2-py3-none-any.whl Python 3 none any Details for attache-0.0.2-py3-none-any.whl

Total release size: 1.0 MB

Release files / attache-0.0.2.tar.gz

Download URL attache-0.0.2.tar.gz
Size 673.0 kB
Tags Source
SHA-256 checksum
How to use checksums
6b463c44a21c9d64c0c50bdccc3ce5b6658a3f10fcb876770a800d2d891e24e2
BLAKE2b-256 checksum
How to use checksums
46727b3852d4c5795c0bc1ad152584116d9b15fda1b400e69e83e810280a9c9e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / attache-0.0.2-py3-none-any.whl

Download URL attache-0.0.2-py3-none-any.whl
Size 357.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1b176b15477cca68f2d99c113c73b5409ae05879a1eb41f9726f95634bca085c
BLAKE2b-256 checksum
How to use checksums
25413fdc8e35a63a750c2b46e4eec8f3f7338b551304e3d029d9c4fbe78622ac
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Security for attache 0.0.2

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for attache-0.0.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page