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 just under 1,600 lines of Python code, the cap CI enforces; everything else is a skill.
Status: phase 1 of the roadmap: the local core, terminal and web chat. Slack and Signal arrive in phase 2, email (Outlook, Gmail, Titan) in phase 3.
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
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~/.attacheis a git repo, soattache skills logandattache skills undo <name>show and reverse every change. - Artifacts are HTML pages the assistant writes into
~/.attache/artifacts/. The local web server adds a smallattachebridge 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. - Roles. You are the owner. Group members (from phase 2) 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.
- Claude Code runs as a backend with
claude -pon 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~/.attachecan 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.1
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 | Actions |
|---|---|---|---|---|
| attache-0.0.1.tar.gz | 485.7 kB | With provenance | Details for attache-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| attache-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for attache-0.0.1-py3-none-any.whl |
Total release size: 737.0 kB
Release files / attache-0.0.1.tar.gz
| Download URL | attache-0.0.1.tar.gz |
|---|---|
| Size | 485.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
908b8097a93317de0e6cec7de6cac3fa188d62047375e590a1363cb465fa052b
|
|
BLAKE2b-256 checksum How to use checksums |
d29f52ae212c7c58a9cbd3db8241f3d068d94f936447cfcf8c8be50333c19fc7
|
| 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 20, 2026.
Transparency logRelease files / attache-0.0.1-py3-none-any.whl
| Download URL | attache-0.0.1-py3-none-any.whl |
|---|---|
| Size | 251.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c257579734d5a0fcdef942c3e9b5f151dca3c4278a3de3410abc40b163a1afa9
|
|
BLAKE2b-256 checksum How to use checksums |
03eed48c0c3ac6e26a428921067504f2a2339b6f3b9895dfb476cf9bfca67258
|
| 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 20, 2026.
Transparency logSecurity for attache 0.0.1
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.
Attestation for attache-0.0.1.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 20, 2026.
Transparency logA 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.